We replicate a number of vital PROD servers to our DR site and are having a major issue. In the DR site, there is a domain controller (not the PDC) which syncs with the domain controllers in the PROD site so it is always up-to-date.
I our tests we failed over our PROD servers to the DR site and found that the domain controller in the DR site, when rebooted, takes around 90 minutes to boot up and gets stuck at the "Applying Group Policy" screen.
Looking at the logs, I can see EVENTID 3096, "The primary domain controller for this domain could not be located" and I feel that this is the reason the DR domain controller is taking so long to boot.
Is there a fix for this - where we can stop the DR domain controller from looking for the PDC??
The DR domain controller is Windows 2008 R2. Thanks.
EDIT:
I just found out that the domain controller is set to DHCP for an IP and it does not look like it found a DHCP server!.
| +-- JDMils |