New DC never shares sysvol or NTDS and gets Event 13565

[chicagotech]

I have an old 2003 DC that (as part of the migration process) is being upgraded to R2, and then I'm installing a 2008 R2 server to be our new DC and file server. I do the ADPrep on the old server, then DCPromo the 2008 server, and it creates teh sysvol folder, but it never shares it, never replicates it. I'm doing a run through before the actual move scheduled for this weekend, and I haven't been able to get aeroudn this in any of the tests. I tried disab;ling the firewall on 2008, as well as disabling ip6, I also confirmed that the old DC ahs DNS entries for the new dc (svr), checked that the old DC is stil set as the DNS serve ron the new DC. Everthing that I've seen to check, but nothing gets me past the two errors:

13565 File Replication Service is initializing the system volume with data from another domain controller. Computer NewDC cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL. AND

13508 The File Replication Service is having trouble enabling replication from oldDC.ourdomain.net to newDCfor c:\windows\sysvol\domain using the DNS name oldDC.ourdomain.net. FRS will keep retrying.

I'm supposed to do this sunday, and would REALLY like to have this resolved before we put it in place (rather than after and hope no other problems come up). Any suggestions are MUCH appreciated.

[chicagotech]

If this is the only DC in the environment take the backup of sysvol folder(both policies and script folder) and peform authorative restore(D4).

Steps:
D4 also knowas as authorative,
To complete an authoritative restore, stop the FRS service, configure the
BurFlags
registry key, and then restart the FRS service.
To do so:
1.Click Start, and then click Run.
2.In the Open box, type cmd and then press ENTER.
3.In the Command box, type net stop ntfrs.
4.Click Start, and then click Run.
5.In the Open box, type regedit and then press ENTER.
6.Locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
7.In the right pane, double click BurFlags.
8.In the Edit DWORD Value dialog box, type D4 and then click OK.
9.Quit Registry Editor, and then switch to the Command box.
10.In the Command box, type net start ntfrs.
11.Quit the Command box.
When the FRS service is restarted, the following actions occur:
•The value for the BurFlags registry key is set back to 0.
•An event 13566 is logged to signal that an authoritative restore is started.
•Files in the reinitialized FRS replicated directories remain unchanged and become authoritative on direct replication. Additionally, the files become indirect replication partners through transitive replication.
•The FRS database is rebuilt based on current file inventory.
•When the process is complete, an event 13516 is logged to signal that FRS is operational. If the event is not logged, there is a problem with the FRS configuration.

Reference KB:http://support.microsoft.com/kb/290762

Regards,
Sandesh Dubey.

[chicagotech]

Event id 13568 indicates that the server' replica set is in journal wrap state.

To resolve the issue, perform D4 (Auth) restore on on Old DC, it will recover the replica set from journal wrap and you will get 13516 on server. Once you are done with above perform D2 (Non-auth) on new DC.

Once again same KB, you will need to follow this:http://support.microsoft.com/kb/290762

Regards,
Abhijit Waikar.