Hello there, long time since I updated my blog, you can blame all my customers that have been asking for Upgrade and all the things related to it, hehe, no please don’t. Today, I’d like to quickly explain a proper step by step process to migrate your domain SYSVOL from File Replication Service (FRS) to Distributed File System Replication (DFSR). To learn about the benefits and advantages of using DFSR, please see http://technet.microsoft.com/en-us/library/cc794837(WS.10).aspx
There are different stages of SYSVOL migration and each stage has a purpose, the whole idea behind these stages is to create a roadmap where you can decide to move forward or to return back to FRS if something unforeseeable happens. We all know how important SYSVOL is, that is, it contains your entire domain Policies (GPTs) as well as Scripts. Not going into detail of SYSVOL, let’s just look at these stages, also called Stable States, and look at what happens at each state. Remember the last stage is where you cannot reverse from.
There are 4 Stable States of SYSVOL migration to DFSR, though there are total of 9 but we will focus on these Stable States and understand each one separately. I will list the commands as well as the process that happens when you run these commands. We will also see how to check if domain controllers have successfully arrived at a particular state. Also, we will look at Active Directory objects i.e. changes in Active Directory, some DFS parameters, as well as file system changes related to SYSVOL. The 4 Stable States are (drum roll please)….
Commands we will use are:
So, first, what are the requirements before we take our first step to this beautiful replication engine, well, the requirements are:
Right then, let’s look at the 4 Stable States in a bit more detail, quickly:
State 0: START
State 1: PREPARED
State 2: REDIRECTED
State 3: ELIMINATED (irreversible step aka no going back)
As I mentioned above in State 3 that it is irreversible meaning no going back, however if you were at State 2, you could initiate command to State 1 or State 0 and the appropriate steps would be taken by every domain controller to undo what was done as part of this migration process.
Before I can say ‘we are done’, let me share some more details and the commands for each step, as well as how to speed things up (not necessarily recommended, but if you know what you are doing, then you create your own recommendations J), why you ask, well since we are making changes to DFSR in the database, the content is polled once an hour by the service but we can manually poll these updates from AD. For migration of your SYSVOL replication to DFSR, below is all you need !!!
First, let’s make sure our DFL is atleast Windows Server 2008.
Now, we can migrate (assuming AD and SYSVOL replication is healthy already). My environment is a single domain forest called Contoso.com with two domain controllers ContosoDC1 and ContosoDC2.
1. Open a Command Prompt as an Administrator and type the command ‘dfsrmig /CreateGlobalObjects’
2. Notice the creation of DFSR-GlobalSettings container in System container
3. We can now poll AD for the changes we just made on both ContosoDC1 and ContosoDC2
4. Check the migration state of all domain controllers by ‘dfsrmig /GetMigrationState’
5. Moving to the next state, by typing ‘dfsrmig /SetGlobalState 1’
6. To speed things up, we can replicate just the object where these changes are being made by using the command ‘repadmin /resplsingleobj * contosodc1 “CN=DFSR-GlobalSettings,CN=System,DC=Contoso,DC=Com”
7. Let’s verify the value for msDFSR-Flags, 16 is Prepared
8. We can again, poll AD for the changes we just made on both ContosoDC1 and ContosoDC2
9. Let’s replicate inbound from our domain controller ContosoDC1
10. Check the migration state of all domain controllers by ‘dfsrmig /GetMigrationState’
11. Notice the copy of SYSVOL folder into SYSVOL_DFSR in C:\Windows or wherever the SYSVOL is placed.
12. Check that the current shared folder still points to C:\Windows\SYSVOL\Sysvol
13. Move to Redirected state by typing ‘dfsrmig /SetGlobalState 2’
14. This time the share SYSVOL is pointing to the copied one i.e. C:\Windows\SYSVOL_DFSR\Sysvol
15. Finally, we can get to Eliminated state by typing ‘dfsrmig /SetGlobalState 3’. Notice the message.
16. Note that the previous SYSVOL is deleted.
Welcome to wonderful world of DFSR J
Mr MCM Qasim, still a great post twice I've i referred to this now...Great Job.
I read this topic twice and I am sure I will come back again while testing my DC :D
And with this I finished reading all your posts ------ GREAT!
Thanks Amarpal and to Syeda, just wrote one more :)
Great post - very easy to follow. Thanks.
AweSome ... Great one!
You make it look so easy!
What a nice write up, it is coming very handy as we prepare domain and forest functional level migration to Windows Server 2008 R2.
Keep it up bro!
Thank you so much for this tutorial! I've just completed the migration and can't wait to see all the benefits of DFS-R in my environment.
All the best!
I successfully migrated over and replication is definately running better. I have one dumb question. I originally had SYSVOL on drive G: and likewise I had a SYSVOL folder also in C:\Windows. Did DFSR migration also remove this folder from C:\windows?
I am in a situation where I need to migrate FRS sysvol to DFSR Sysvol.But My FRS Sysvol Contains _NTFRSxxxxxxxx (Morphed) folders.
let me know if FRS Sysvol contains Morphed folders and If I initiate the FRS to DFSR migration, does DFSR will automatically take care of that ?
OR do i need to remove them prior to Migration ?
Nice post, helped me a lot while doing FRS to DFSR migraiton.
Best write up on the web.
I noticed that after migrating to Server 2012 R2 on my DC's that my state was set to Eliminated, however i still have the SYSVOL folder and not the SYSVOL_DFSR....
Typo on point 6 should berepadmin /replsingleobj * contosodc1 “CN=DFSR-GlobalSettings,CN=System,DC=Contoso,DC=Com”
Beautifully Documented. Easy to understand and accordingly follow. Thank you