SOLVED
Home

FRS to DFS Replication migration

%3CLINGO-SUB%20id%3D%22lingo-sub-376828%22%20slang%3D%22en-US%22%3EFRS%20to%20DFS%20Replication%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-376828%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20currently%20running%20on%20Windows%202008%20R2%20DCs%20(2%20DCs)%20and%20Domain%5CFunctional%20Level%202003.%20I%20am%20planning%20to%20move%20to%20promote%204%20Windows%202016%20(version%201607)%20DCs%20and%20Demote%20the%20Win%202008%20R2%20ones%20and%20upgrade%20the%20functional%20level%20to%20Windows%202008%20R2.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOption%20Plan%201%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1-%26nbsp%3BUpgrade%26nbsp%3Bdomain%20and%20functional%20levels%20to%202008%20R2%3C%2FP%3E%3CP%3E2-%20%26nbsp%3BInstall%20Windows%202016%20DCs%3C%2FP%3E%3CP%3E3-%20Demote%20Windows%202008%20R2%20DCs%3C%2FP%3E%3CP%3E4-%20Move%20SYSVOL%20from%20FRS%20to%20DFS%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOption%20Plan%202%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1-%26nbsp%3BUpgrade%26nbsp%3Bdomain%20and%20functional%20levels%20to%202008%20R2%3C%2FP%3E%3CP%3E2-%20Move%20SYSVOL%20from%20FRS%20to%20DFS%3C%2FP%3E%3CP%3E3-%20%26nbsp%3BInstall%20Windows%202016%20DCs%3C%2FP%3E%3CP%3E4-%20Demote%20Windows%202008%20R2%20DCs%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhich%20option%20would%20be%20most%20preferred%20and%20why%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-376828%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActive%20Directory%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-377045%22%20slang%3D%22en-US%22%3ERe%3A%20FRS%20to%20DFS%20Replication%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-377045%22%20slang%3D%22en-US%22%3E%3CP%3EYou're%20welcome%2C%20glad%20to%20help.%20Seems%20you%20may%20have%20marked%20the%20wrong%20response%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-377041%22%20slang%3D%22en-US%22%3ERe%3A%20FRS%20to%20DFS%20Replication%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-377041%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F51719%22%20target%3D%22_blank%22%3E%40Dave%20Patrick%3C%2FA%3E%26nbsp%3Bthanks%20for%20the%20update%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-376832%22%20slang%3D%22en-US%22%3ERe%3A%20FRS%20to%20DFS%20Replication%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-376832%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F303439%22%20target%3D%22_blank%22%3E%40KYoussef_Consultant%3C%2FA%3E%20You%20can%20do%20it%20either%20way.%20Server%202016%20still%20supports%20FRS%20(but%20Server%202019%20does%20not)%20Either%20case%20before%20starting%26nbsp%3B%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EI'd%20use%20dcdiag%20%2F%20repadmin%20tools%20to%20verify%20health%20is%20100%25%20before%20starting.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3ETo%20do%20the%20FRS%20to%20DFSR%20migration%20you%20can%20follow%20along%20here.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Ffilecab%2F2014%2F06%2F25%2Fstreamlined-migration-of-frs-to-dfsr-sysvol%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3Ehttps%3A%2F%2Fblogs.technet.microsoft.com%2Ffilecab%2F2014%2F06%2F25%2Fstreamlined-migration-of-frs-to-dfsr-sysvol%2F%3C%2FFONT%3E%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3ETo%20do%20the%20domain%20controller%20upgrades%26nbsp%3BI'd%20use%20dcdiag%20%2F%20repadmin%20tools%20to%20verify%20health%20%3CU%3Ecorrecting%20all%20errors%20found%3C%2FU%3E%20before%20starting.%20Then%20I'd%20stand%20up%20the%20new%202016%2C%20patch%20it%20fully%2C%20license%20it%2C%20join%20existing%20domain%2C%20add%20active%20directory%20domain%20services%2C%20promote%20it%20also%20making%20it%20a%20GC%20(recommended)%2C%20transfer%20FSMO%20roles%20over%20(optional)%2C%20transfer%20pdc%20emulator%20role%20(optional)%2C%20use%20dcdiag%20%2F%20repadmin%20tools%20to%20verify%20health%2C%20when%20all%20is%20good%20you%20can%20decommission%20%2F%20demote%20old%20one%2C%20and%20move%20on%20to%20next%20one.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

I am currently running on Windows 2008 R2 DCs (2 DCs) and Domain\Functional Level 2003. I am planning to move to promote 4 Windows 2016 (version 1607) DCs and Demote the Win 2008 R2 ones and upgrade the functional level to Windows 2008 R2.

 

Option Plan 1:

 

1- Upgrade domain and functional levels to 2008 R2

2-  Install Windows 2016 DCs

3- Demote Windows 2008 R2 DCs

4- Move SYSVOL from FRS to DFS

 

Option Plan 2:

 

1- Upgrade domain and functional levels to 2008 R2

2- Move SYSVOL from FRS to DFS

3-  Install Windows 2016 DCs

4- Demote Windows 2008 R2 DCs

 

Which option would be most preferred and why ?

 

3 Replies
Highlighted

@KYoussef_Consultant You can do it either way. Server 2016 still supports FRS (but Server 2019 does not) Either case before starting I'd use dcdiag / repadmin tools to verify health is 100% before starting.

To do the FRS to DFSR migration you can follow along here.

https://blogs.technet.microsoft.com/filecab/2014/06/25/streamlined-migration-of-frs-to-dfsr-sysvol/

 

To do the domain controller upgrades I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting. Then I'd stand up the new 2016, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to verify health, when all is good you can decommission / demote old one, and move on to next one.

 

 

Highlighted
Solution

@Dave Patrick thanks for the update

You're welcome, glad to help. Seems you may have marked the wrong response?