Verifying File Replication during the Windows Server 2008 DFSR SYSVOL Migration – Down and Dirty Style

SYSVOL migration from File Replication Services (FRS) to Distributed File System Replication (DFSR)

Group Policy Team Blog — Fri, 15 May 2009 00:55:01 GMT

It’s come to my attention (in a blunt object kind of way) that you’ve been waiting to migrate from Windows

SYSVOL migration from FRS to DFSR - Whitepaper Released

Ask the Directory Services Team — Fri, 01 May 2009 19:54:53 GMT

Ned here. It's done, it's out, come get it, stop yelling at me! :-) SYSVOL Replication Migration Guide:

DFSR SYSVOL Migration FAQ: Useful trivia that may save your follicles

Ask the Directory Services Team — Fri, 01 May 2009 19:51:24 GMT

Hi, Ned here again. Today I'm going to go through some well-hidden information on DFSR SYSVOL migration;

re: Verifying File Replication during the Windows Server 2008 DFSR SYSVOL Migration – Down and Dirty Style

NedPyle [MSFT] — Wed, 17 Dec 2008 05:47:05 GMT

Hi,

We've seen one circumstance where some of the FRS AD objects might not get cleaned up (the details escape me and I'm not in the office to check - I seem to recall it had to do with RODC's). That was not the error I remember though (in fact, there were no errors - we just dangled behind some AD FRS data that never got used by the service).

If you look in ADSIEDIT.MSC under the DC objects CN=NTFRS Subscriptions,CN=ARRENC1,OU=Domain Controllers,DC=a,DC=com do you still see the NTFRS objects for SYSVOL? And in the CN=File Replication Service,CN=System,DC=A,DC=COM path?

Is there anything you can tell me about how you reproduced this scenario? Do your test machines also host custom FRS/DFSN replica sets?

re: Verifying File Replication during the Windows Server 2008 DFSR SYSVOL Migration – Down and Dirty Style

jeffery.d.jorgenson@wellsfargo.com — Wed, 17 Dec 2008 03:21:32 GMT

After running dfsrmig /setglobalstate 3 on my test domain, it ran fine. However, I am getting residual errors in the FRS log saying:

"The File Replication Service cannot replicate c:\system volume\sysvol\domain because the pathname of the replicated directory is not the fully qualified pathname of an existing, accessible local directory."

FRS still wants to replicate the old sysvol path.

The DFSRMIG \GETGLOBALSTATE and \GETMIRATIONSTATE all say succeded.

Any idea why these errors are showing?

What are the Schema Extension Requirements for running Windows Server 2008 DFSR?

Ask the Directory Services Team — Wed, 02 Jul 2008 21:03:57 GMT

Ned here again. With the release of Windows Server 2008, a number of customers have asked us whether

Verifying File Replication in 2008 DFS | Binaryfactory Blog

Verifying File Replication in 2008 DFS | Binaryfactory Blog — Fri, 23 May 2008 07:37:39 GMT

PingBack from http://blog.binaryfactory.ca/2008/05/verifying-file-replication-in-2008-dfs/