SYSVOL Migration from FRS to DFRS Replication
Hi, We are looking to upgrade our network currently running 2008 R2 Domain Controllers to 2016 DC's
When attempting to promote a 2016 server to Domain Controller status during the prerequisites check we receive the following warning.
"The File Replication Service (FRS) is deprecated. To continue replicating the SYSVOL folder, you should migrate to DFS Replication by using the DFSRMIG command. If you continue to use FRS for SYSVOL replication in this domain, you might not be able to add domain controllers running a future version of Windows Server."
I know we can go through the sysvol migration process to DFRS but what would happen if we don't. Will the contents of sysvol continue to replicate as before whilst using 2016 as our DC's? Can we expect any issues when the last of the 2008 DC's are decommissioned?
When attempting to promote a 2016 server to Domain Controller status during the prerequisites check we receive the following warning.
"The File Replication Service (FRS) is deprecated. To continue replicating the SYSVOL folder, you should migrate to DFS Replication by using the DFSRMIG command. If you continue to use FRS for SYSVOL replication in this domain, you might not be able to add domain controllers running a future version of Windows Server."
I know we can go through the sysvol migration process to DFRS but what would happen if we don't. Will the contents of sysvol continue to replicate as before whilst using 2016 as our DC's? Can we expect any issues when the last of the 2008 DC's are decommissioned?
Cliff Galiher
FRS is deprecated. The warning is exactly what it says it is. 2016, as of now, technically still has the FRS engine. But FRS no longer gets support and any update could break it at any time. That's a significant business risk to take. I *strongly* recommend moving to DFS-R. It was introduced for domain controllers in 2003 R2 so it's not exactly new, and migrating from FRS has been recommended for over a decade now.
ASKER
Thanks for getting back to me, What effect will the upgrade have on existing logon scripts stored in the sysvol folder and deployed via GPO's
We have a fairly large number of scripts being used.
We have a fairly large number of scripts being used.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Many thanks, I wanted to make sure that all scripts and reg files currently being used by GPO's in SYSVOL will continue to work after the migration. Final Question, What happens to GPO's that use a unc path pointing to Netlogon as the script location?
SYSVOL and NETLOGON paths are automatically pointed to the new location during migration. This happens after the file transfer is complete. When the copy process has been completed you can go and compare the contents of SYSVOL and SYSVOL _DFSR before proceeding to the Eliminated stage where it deletes the old SYSVOL.
ASKER
Many thanks to both of you for helping me out, Is there any merit in introducing our new 2016 DC's, Demoting the old 2008 DC's and then complete the migration. Or would you recommend we migrate first?
All recommended checks have been completed and everything seems ok for us to proceed.
All recommended checks have been completed and everything seems ok for us to proceed.
If you have a newer copy of the 2016 ISO, the binaries for FRS are no longer included. It would be best to convert now before migration. https://support.microsoft.com/en-us/help/4025991/windows-server-version-1709-no-longer-supports-frs
ASKER
Thanks, I'm going to start the process later today, Can I run in Redirected state for a couple of days to make sure all is ok?
Yes, there's no issues with that.
ASKER
Many Thanks, All went well.