How to deal with errors when adding an AD server to an existing domain

Question

There is only one existing AD server, and the OS is WIN2016.

One AD server is planned to be added, and the OS is WIN2022.

When I tried to add the AD server scheduled to be added above to an existing domain, the following error occurred.

Verification of replica failed. The specified domain {Domain-Name} is still using the File Replication Service (FRS) to replicate the SYSVOL share. FRS is depreciated.

The server being promoted does not support FRS and cannot be promoted as a replica into the specified domain.

You MUST migrate the specified domain to use DFS Replication using the DFSRMIG command before continuing.

When I searched for the error content, I found the following document.

https://jpwinsup.github.io/blog/2023/03/27/ActiveDirectory/DFSR/migration-from-FRS-to-DFSR/

If you do not know which one is used in the current domain environment, use ADSIEdit to determine where the CN=Domain System Volume (SYSVOL share) container is stored.

I opened ADSI Editor based on the description in the article, but there was nothing in it.

How should we proceed with this in the future? Also, what information will be required at that time?

Answer 1

hi chimakida,

The error you're encountering indicates that the existing domain is still using the deprecated File Replication Service (FRS) to replicate the SYSVOL share. Since Windows Server 2016 and later versions do not support FRS for SYSVOL replication, you need to migrate the SYSVOL replication from FRS to DFS Replication (DFSR) before adding a new Windows Server 2022 as an additional domain controller.

The link you provided seems to offer guidance on the migration process. Here's a general outline of the steps you would need to take:

1. Check the Current Replication Method:
   • Verify that the domain is still using FRS for SYSVOL replication.
   • You can check the current replication method by running the following command on an existing domain controller:

     
          dfsrmig /getglobalstate
     
     

2. Prepare for Migration:
   • Before migrating, ensure that you have a good backup of your domain controllers and critical data.
   • Review Microsoft documentation and articles for any specific considerations or updates related to the migration.
3. Migrate SYSVOL to DFSR:
   • Follow the steps outlined in the provided link or Microsoft documentation to migrate SYSVOL replication from FRS to DFSR.
   • The process may involve running DFSR migration commands, monitoring the migration progress, and verifying successful migration.
4. Verify Migration:
   • After migrating to DFSR, verify the status of the migration using commands like dfsrmig /getmigrationstate and dfsrmig /getmigrationtable.
   • Ensure that there are no errors or issues reported during the migration process.
5. Promote New Windows Server 2022 Domain Controller:
   • Once SYSVOL replication is successfully migrated to DFSR, you can proceed with promoting the new Windows Server 2022 as an additional domain controller.

Remember that each environment may have unique considerations, and it's crucial to refer to the latest Microsoft documentation for the specific versions of Windows Server you are working with.

At the time of migration, you may need information such as administrative credentials, knowledge of the current domain controller configuration, and an understanding of the existing replication topology. Additionally, having a backup and a rollback plan is always a good practice in case any issues arise during the migration process.