FRS to DFS Migration - Service not disabled

Tafadzwa Mukorombindo 21 Reputation points
2021-03-15T09:21:29.097+00:00

Recently we were adding 2 new Windows Server 2019 DCs to our existing pair of WS2016 DCs. However, that failed as we were still using FRS and not DFS for SYSVOL replication. We then went through the migration process as outlined in this article:

https://techcommunity.microsoft.com/t5/storage-at-microsoft/streamlined-migration-of-frs-to-dfsr-sysvol/ba-p/425405

All went well and the service was disabled at the end of it. However, the next day, we notice the FRS service startup on the servers had switched from Disabled to Automatic. The service wasn't running though. SO we decided to disable it again but the same thing happened the next day.

Would anyone out there know if this is to be expected or is there an issue somewhere? everything seems to work fine apart from this.

Thanks

Taf

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,595 questions
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2021-03-16T13:11:09.877+00:00

    The question is that after the migration, should the FRS service be ina Disabled state or does it not matter as long as it's not running and replication is ok?

    Should have been Disabled so something else may have broken.

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments No comments

3 additional answers

Sort by: Most helpful
  1. Anonymous
    2021-03-15T12:51:06.057+00:00

    You'll need to remove the two 2019 domain controllers, then do the FRS-> DFSR migration. Then check domain health / replication is 100% before adding new domain controllers. If needed you can remove the two 2019 from network then seize roles
    https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/transfer-or-seize-fsmo-roles-in-ad-ds

    and perform cleanup.
    https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup
    https://techcommunity.microsoft.com/t5/itops-talk-blog/step-by-step-manually-removing-a-domain-controller-server/ba-p/280564

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments No comments

  2. Fan Fan 15,321 Reputation points Microsoft Vendor
    2021-03-16T01:13:50.963+00:00

    Hi,
    How is the situation now?
    As DSPatrick said above, FRS-> DFSR migration should be done before the 2019 dc was added.
    You need to remove the 2019 DCs and then migrate the FRS to DFSR.
    If you can't remove the 2019 successfully, a metadata cleanup is needed.
    https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup

    Then confirm if everything is working well by command:
    Dcdiag /v >c:\dcdiag1.log
    Repadmin /showrepl >C:\repl.txt
    Repadmin /showreps * 

    Migrate FRS to DFSR.
    Confirm if everything is working well
    Add the new 2019 DC.
    Best Regards,

    0 comments No comments

  3. Tafadzwa Mukorombindo 21 Reputation points
    2021-03-16T09:19:12.577+00:00

    Hi

    Thank you both for your feedback. Just to confirm, we added the 2019 DCs after the FRS->DFSR migration (it actually doesn't;t let you add a 2019 DC when FRS is in use). The question is that after the migration, should the FRS service be ina Disabled state or does it not matter as long as it's not running and replication is ok?

    0 comments No comments