How to migrate FRS to DFSR Replication Method

When join windows 2016/2019 to domain 2008/2003 you can get error like :


The specified domain %1 is still using the File Replication Service (FRS) to replicate the SYSVOL share. FRS is deprecated.

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.

For more information, see


To do that first make sure all Domain Controllers are replicated :

Repadmin /syncall /force /APed

The start migration , Migrate to Prepared State :

Dfsrmig /setglobalstate 1

Make sure the process has finished :

Dfsrmig /getmigrationstate

You should get :

Only then continue with :

Dfsrmig /setglobalstate 2

You should get

Only then continue with :

Dfsrmig /setglobalstate 3

You should get


Then stop the service :


Good Luck


  • Worked great, thanks for putting together such simple and easy to follow steps.

  • Keith says:

    Thumbs up man!

  • Rupesh says:


  • Brandioni says:

    Awesome man! well done, it worked for me to migrate SBS2011 to Server 2019. Excellently written article, keep it up!

  • Maxwell says:

    Can this be done during the day?
    Does it effect the other DCs?

  • Me says:

    Brilliant and helpful. Saved me a LOT of work. Thank you!

  • Stephen says:

    This was perfect thanks! It took about 5-10 minutes for the first migration operation “/setglobalstate 1” to complete then another 5-10 minutes before the target server saw the change after all ops were complete, but other than a little waiting period it was totally smooth.

  • Jim says:

    You the man. Worked like a charm. 2012 at functional level 2003 and adding 2019 domain controller. Also worked 2008R2 server functioning at 2003 and adding 2019 domain controller.

  • Tony says:

    Do I have to perform this on every DC or just one of them?

  • Vic says:

    Awesome! Thank you…. very simple and well explained.

  • Edmund says:

    My first domain controller crashed, its been manually removed from the forrest.

    I cannot join new 2019 to my now the only DC I have left due to the dfsr. Will this work if I only have one DC?

  • Paul says:

    Nice and simple. Do we stop and disable NTFRS service on all DCs, not just one? I assume so.

  • Kenny Gurley says:

    Thank you! Worked perfectly…

  • Andrew says:

    After a long time off the tools – needed to step up and do this one – this guide worked perfectly. Thank you!!

    FWIW – reference domain was 2 physical 2k12R2 servers. Was looking at promoting 2 virtual 2k19 servers into the environment and couldnt promote them.

  • Arsalan Zia says:


    I am trying to upgrade FRS to DFRS but everytime it stuck on globalstate1 and in logs it is showing following error:

    DFSR was unable to copy the contents of the SYSVOL share located at C:\Windows\SYSVOL\domain to the SYSVOL_DFSR folder located at C:\Windows\SYSVOL_DFSR\domain. This could be due to lack of availability of disk space or due to sharing violations.

    Additional Information:
    Sysvol NTFRS folder: C:\Windows\SYSVOL\domain
    Sysvol DFSR folder: C:\Windows\SYSVOL_DFSR\domain
    Error: 367 (The process creation has been blocked.)

    I can see SYSVOL_DFRS folder created it C drive but it is not copying any data from Sysvol folder and above log is getting generated every after 5 mins.

    I need to do globalstate0 to rollback this each time. I have searched many things related to this error but unable to find any solution.

    Any help would be appreciated.

  • Vytautas says:

    For the last step disable and stop service you can use these powershell lines. You will not need to go one by one to DC or RODC and do the same action. Please notice that remote powershell feature must be enabled on servers:

    $All_domain_c=(Get-ADDomainController -filter * | Select-Object name).name
    $s = New-PSSession -ComputerName $All_domain_c
    Invoke-Command -Session $s {Set-Service ntfrs -StartupType Disabled;Stop-Service ntfrs}

  • CpnObvious says:

    Worked like a charm, thanks!

  • J.Cota says:

    This worked… What do you want, hookers or beer?

  • Idy says:

    I currently have a 2012 and 2008 server and i want to move to 2019. What implications would it have on my current servers.

    • admin says:

      You will have to update the schema in order to upgrade to 2019, that been said, 2008 is not supported for 2019 there for you will have to demote them from being DC’s

  • Idy says:

    I currently have 2012 as my main DC and my 2008r2 as my second DC. I want to move to 2019 and make that as another DC. Eventually make the 2019 my main DC, what would be the best practice?.
    If I run the command like you mentioned above would that have any effect on my main DC?

  • Saravanakumar Mani says:

    Nice helps it’s work’s, 2003 to 2012 R2, after 2012 to 2019 error came. Your solution works thanks a lot …

  • Lodgey says:

    Worked like a charm, just be patient and occasionally run the Dfsrmig /getmigrationstate to determine each step is complete. Server 2016 (1607) – Server 2019. Thank You

  • Evertos says:

    Awsome Guide.

    Maybe update the Guide, I didn’t have to stop the services ad the end!

  • GrantAU says:

    Works great – just a note that after the “Dfsrmig /setglobalstate 3” command you have left out the need to run “Dfsrmig /getmigrationstate” until migration reaches “consistent state”

    It’s fairly obvious that you need to do this, however some people may go direct to the START/STOP FRS Service stage before ensuring migration has completed fully.

  • David Napolitabn says:

    I believe the reason I received this message is that I am at the 2008 functional level. My DCs are 2016. If my assumption is correct, then all I have to do is to move to 2016 functional level. Is this correct?

  • Thanks so much for the detailed steps. Worked well for my Win 2012 R2

  • Shawn Butt says:

    Thank you brother!
    This should be the default standard for making things easier.

  • Angel says:

    Moving from 2016 to 2019, anything that I should look at before starting this process?

Leave a Reply

Your email address will not be published. Required fields are marked *