AD Replication Problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Ok, I have 2 DCs in my root domain. I was going to migrate to 2003 so on DC1
I seized all of the FSMO roles. I was unable to dcpromo DC2 out of the
domain so I could reload him, so I had to manually remove him from the AD.
After reloading the server, I tried to dcpromo him back into the domain after
doing an adprep /forestprep and adprep /domainprep. Then I found out that
DC1 never completely became a DC and has not completed replicating the SYSVOL
folder. So when I try to dcpromo back into the domain, it tells me there is
no domain controller available. Since I only have the 2 DCs in my root
domain, I'm starting to think that I am screwed. I reloaded DC2 and booted
into Directory Restore Mode and restored the System State data from the
backup of the AD I made right before I brought everything down, but whenever
I reboot after restoring the AD, the server just blue screens.

Is there anyone that can help me out in this situation? If I can somehow
get all of the information curren on DC1, then I might be on the right track.

Thanks.

John
 
Shouldn't be too hard to get that DC backup that does not have SYSVOL.

First of all check the contents of your SYSVOL folder
(C:\winnt\sysvol\domain\Policies)
Look for a policy starting with {31B and {6AC. These are the Default Domain
and Default Domain controllers policies.

If you do not have these policies, download and run recreatedefpol.exe from
www.microsoft.com/downloads

Once / If you have the 6AC and 31B policies folder you will need to
reinitialize SYSVOL by performing an authoritative restore of FRS. To do
this:
Stop the File Replication Service
Set the registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup\Burflags to d4
Start the File Replication Service.

Shortly after this SYSVOL should share out.

There may still be a bit of a mess left behind from your old domain
controller but this should get you started.

Hope this helps,

Brian Delaney
 
Thanks a ton! That seemed to fix my problem. I was initially going to try
to restore the old DC back to the state it was in prior to the reload
attempt, but I wasn't having much luck there. This seems to have fixed my
problem.

Thanks again.
John
 
Back
Top