Back to Blog

Finding Why SYSVOL on FRS Blocks a New Domain Controller

Christopher 6 min read
windowsactive-directorytroubleshooting

A new Windows Server 2019 or later server can't be promoted to a domain controller in a domain that still replicates SYSVOL with the File Replication Service (FRS). Promotion stops at the prerequisite check with "The specified domain contoso.com is still using the File Replication Service (FRS) to replicate the SYSVOL share." The message also says "You MUST migrate the specified domain to use DFS Replication using the DFSRMIG command before continuing." This post covers how to confirm which service replicates SYSVOL, check replication health, move the domain through the dfsrmig states, and clear the two blockers Microsoft documents for the migration.

A recent r/sysadmin thread describes a plan to replace Windows Server 2016 domain controllers with new Windows Server 2022 VMs. Microsoft's documentation says a domain at a functional level older than Windows Server 2008 uses FRS for SYSVOL. A domain that started at that level keeps FRS until someone runs the migration.

Check which service replicates SYSVOL

Find the PDC emulator and the domain functional level from an elevated PowerShell window on any domain controller.

Get-ADDomain | Select-Object PDCEmulator,DomainMode

The migration needs a DomainMode of Windows2008Domain or higher. Microsoft says to run dfsrmig /getglobalstate only on the PDC emulator.

dfsrmig /getglobalstate

A domain that never started the migration returns "DFSR migration has not yet initialized". A domain that finished it returns "Current DFSR global state: 'Eliminated'". A "Prepared" or "Redirected" state means a migration is in progress or was left partway.

Check the share on each domain controller as well.

net share SYSVOL

The "Path" line reads C:\Windows\SYSVOL\sysvol while FRS serves the share. It reads C:\Windows\SYSVOL_DFSR\sysvol once DFS Replication serves it.

Check replication before you change anything

Microsoft's migration guide asks for a healthy SYSVOL, a backup of the SYSVOL folder, and the DFS Replication service running with a "Start Type" of "Automatic" on the PDC emulator. I'd check Active Directory replication on every domain controller first.

repadmin /replsummary
dcdiag /q
Get-Service DFSR | Select-Object Status,StartType

Fix every failure repadmin or dcdiag reports before you set the first state. Back up the SYSVOL folder on the PDC emulator.

Move the domain through the states

The dfsrmig tool has four global states. They are Start (0), Prepared (1), Redirected (2), and Eliminated (3). In Prepared, DFS Replication replicates a copy of the SYSVOL folder while FRS keeps replicating the original. In Redirected, the DFS Replication copy serves SYSVOL requests. In Eliminated, Windows deletes the original SYSVOL folder and FRS stops replicating SYSVOL. Microsoft documents that the migration can be rolled back any time before Eliminated. Eliminated can't be rolled back.

Set each state on the PDC emulator and wait for every domain controller to reach it before you set the next one.

dfsrmig /setglobalstate 1
dfsrmig /getmigrationstate

Run dfsrmig /getmigrationstate until it returns "Migration has reached a consistent state on all Domain Controllers." Any domain controller listed under "The following Domain Controllers are not in sync with Global state" hasn't reached the state yet. Microsoft says the wait depends on Active Directory replication latency and the amount of data in SYSVOL.

dfsrmig /setglobalstate 2
dfsrmig /getmigrationstate

Once every domain controller reports Redirected, run gpupdate /force on a client in each site and confirm Group Policy applies without errors. Set Eliminated only after Group Policy applies without errors in every site.

dfsrmig /setglobalstate 3
dfsrmig /getmigrationstate

After every domain controller reports Eliminated, run net share on each one and confirm the SYSVOL path is under C:\Windows\SYSVOL_DFSR. Stop and disable FRS on each domain controller unless FRS replicates something other than SYSVOL.

sc.exe \\<servername> stop ntfrs
sc.exe \\<servername> config ntfrs start= disabled

When a domain controller never reaches the new state

Read the DFS Replication log on each domain controller that hasn't reached the state.

Get-WinEvent -FilterHashtable @{LogName='DFS Replication';Id=8013,8028} -MaxEvents 20 | Select-Object TimeCreated,Id,Message

Event 8028 says "DFSR Migration was unable to transition to the 'PREPARED' state" for that domain controller. Event 8013 says DFSR "was unable to copy the contents of the SYSVOL share" to the SYSVOL_DFSR folder. Both events include an error code.

When both events show error 367 ("The process creation has been blocked."), the domain controller matches a case Microsoft documents for domain controllers upgraded in place to Windows Server 2019 while the domain used FRS. Those domain controllers stay in the Start state and stop sharing SYSVOL and NETLOGON. Microsoft's workaround is to set the global state back to 0 and confirm SYSVOL is shared again on those domain controllers. It then has you demote the upgraded domain controllers to member servers, finish the migration on the remaining older domain controllers, and promote the upgraded servers again. The article gives a separate procedure for domain controllers that already reached Eliminated.

A domain that uses Microsoft Entra Kerberos for passwordless sign-in has a computer object named AzureADKerberos in the Domain Controllers OU. The output of dfsrmig /getmigrationstate then includes "AzureADKerberos ('Start') - Writable DC". The migration never reaches Eliminated because the object doesn't replicate SYSVOL. Microsoft's storage team documents the fix. Open ADSI Edit on a domain controller, create an object of class msDFSR-LocalSettings named DFSR-LocalSettings under the AzureADKerberos object, and set its msDFSR-Flags attribute to 48. Wait for Active Directory replication and run dfsrmig /getmigrationstate again.

Retry the promotion

Promote the new server again once every domain controller reports Eliminated. Run dcdiag /q on the new domain controller after the reboot, and run net share to confirm it shares SYSVOL and NETLOGON.

Where ET Ducky shows it

I build ET Ducky. You can open a Live Session shell to each domain controller from the browser without the need for a VPN and run dfsrmig /getmigrationstate, net share, and the Get-WinEvent query there. Its Windows agent reads process creation and file events from the kernel through ETW. File activity in the SYSVOL and SYSVOL_DFSR folders shows up in the ETW event stream with the process that made it.

You'd start a Multi-Agent Session across a domain controller that reached the new state and one that didn't. It compares the kernel events from both to find the outlier. The raw events stay on the hosts.

Try it on one server

One Windows or Linux server costs $5 a month with no query subscription.

See pricing