Saturday, April 9, 2011

Migrating SYSVOL to DFS replication (Part 2)

Installing DFS Server Role
1. At the Domain Controller, log in as Domain Administrator,
2. Launch "Command Prompt", enter "ServerManagercmd -i FS-DFS"

Figure 4: Installing DFS Server role

3. Repeat step 2 for all domain controllers.

Verify initial state
1. Still in the Command Prompt of the Domain Controller, enter the following commands:

dfsrmig /get/GlobalState
dfsrmig /getMigrationState

Figure 5: verify the migration state

Starting the migration
1. Still in the Command Prompt of the Domain Controller, enter "dfsrmig /setGlobalState 1".

Figure 6: DFSR global state is changed Prepared state

2. Enter "dfsrmig /getmigrationstate"

Figure 7: All domain controllers are changed Prepared state

Remark: If one of the domain controller doesn't change Prepared state, you must not perform next step.

Remark: You can enter the following commands to force the dfs replication and AD replication:

repadmin /syncall /Aed
repadmin /syncall /AedP
dfsrdiag /pollad /member:dc1.contoso.com

Remark: "dfsrdiag /pollad" is used to triggering a sync with the global information store in Active Directory Domain Services.

3. Launch "ADSI Edit", expand "Default naming context > <Domain name> > CN=System > CN=DFSR-GlobalSettings"

Figure 8: DFSR-GlobalSettings

4. Launch "Registry Editor", navigate to the following registry key:

HKLM\SYSTEM\CurrentControlSet\Services\DFSR\Parameters\Sysvols\Migrating sysVols\Local State

Figure 9: Local State registry key

Remark: Local State 1 is Prepared State.

5. Navigate to "HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\SysVol".

Figure 10: AD is still using SYSVOL folder

6. In "Windows" folder, a new "SYSVOL_DFSR" folder is created, and contains all copied domain public files.

Figure 11: The new SYSVOL_DFSR folder

Redirection the production folder
Before migrating to the "Redirected" state, a couple of precautions are advised.
A. All domain controllers are in "Prepared" state.
B. Verify that SYSVOL share is still being shared out.

1. At the Domain Controller, log in as Domain Administrator.
2. Launch "Command Prompt", enter "dfsrmig /setGlobalState 2".

Figure 12: DFSR global state is changed Redirected state

3. Enter "dfsrmig /getmigrationstate".

Figure 13: All domain controllers are changed Redirected state

4. Back to "Registry Editor", verify the "Local State" and the "SYSVOL" location.

Figure 14: Local State 2

Figure 15: AD is using SYSVOL_DFSR folder
  
Eliminating old SYSVOL configuration
Remember that the migration process to the "Eliminated" state cannot be reverted under any circumstances.

Before migrating to the "Elminated" state, a couple of precautions are advised.
A. All domain controllers are in "Redirected" state.
B. Verify that the SYSVOL share is still being shared out.

1. Still in the Domain Controller, back to "Command Prompt".
2. Enter "dfsrmig /setGlobalState 3".

Figure 16: DFSR global state is changed Eliminated state

3. Enter "dfsrmig /getmigrationstate"

Figure 17: All domain controllers are changed Eliminated state


As a result, SYSVOL folder migrates to SYSVOL_DFSR. Now, SYSVOL folder is used DFS to replicate the contains. You can custom the replication schedule of the SYSVOL_DFSR folder.

For more information:


This posting is provided “AS IS” with no warranties, and confers no rights!

1 comment: