Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. SYSVOL Migrations from FRS to DFSR may fail when migrating on Windows Server 2008 SP1

SYSVOL Migrations from FRS to DFSR may fail when migrating on Windows Server 2008 SP1

View products that this article applies to.

Summary

Please update to the latest service pack before migrating SYSVOL from FRS to DFSR on Windows Server 2008. Migrations on Windows Server 2008 SP1 may fail due to downstream servers trying to replicate the same file(s) from their upstream partners that no longer exist. 

This issue is resolved in Windows Server 2008 SP2 and also in Windows Server 2008 R2. If you have already begun your migration and suspect you have encountered this problem please contact Microsoft Support. If you have started your migration and encounter this issue, upgrading to the latest service pack will not resolve the issue. You will need to contact Microsoft Support.

↑ Back to the top

More Information

To encounter this problem the non-primary member that is stuck in initial replication must be replicating from a DC that was not the original primary member. Normally the PDC emulator is the primary member for SYSVOL migrations. DFSR replication for SYSVOL migrations follows the AD replication topology. If you have more than one AD site defined it is possible you may encounter this issue during SYSVOL migration.

Example Scenario:

DC1 and DC2 are in Site A

DC3 and DC4 are in Site B

DC1 is the PDC emulator and the bridgehead server for site A. DC3 is the bridgehead server for Site B.

Note: As DFSR replication for a SYSVOL migration uses the AD replication topology DC1 will replicate with only DC3 in Site B as they are the bridgehead servers for their respective sites.
  1. SYSVOL migration begins
  2. DC1 is the primary member for the SYSVOL and successfully replicates with DC2 and DC3
  3. DC3 incorrectly leaves some unique entries in its DB when it moves unique files to the pre-existing directory
  4. DC4 begins initial replication and uses DC3 as its source
  5. DC4 is stuck in initial replication trying to replicate the files DC3 left in its DB in step 3

↑ Back to the top

Keywords: kb

↑ Back to the top

Article Info
Article ID : 2492852
Revision : 1
Created on : 1/7/2017
Published on : 1/7/2011
Exists online : False
Views : 158