Problem: Applied some updates to my Server 2008 R2 domain controller which required a reboot. Tried to login to the DC and was stuck on applying computer or user settings. (it varied between the two). Waited and waited but it just stayed there. Shut down the DC and was successful on the and try but I don’t want that to be my fix. Checked in the application logs and had the following error:
“The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.”
Solution: Turns out that I had configured my DC’s primary DNS to it’s own IP address. Microsoft recommends that you set your DC’s primary DNS to another DNS server and set the secondary to its own IP. Made the switch and much better!
How were you able to make the change if you are stuck at applying computer settings? I would like to try to make the dns setting changes as well, but I litterally cannot get logged into the server to make the changes. Curious how you made that happen. Thanks,
I had to hard restart the DC and eventually it would let me login but it was a crap shoot. Would sometimes take me 2 or 3 times. You can also try letting it sit at “applying settings” but not guaranteed to work. Neither is something I would recommend unless you are desperate. You might want to try rebooting in Directory Services Restore Mode (DSRM). You’ll then be taken offline as a DC and will only be a member server for that time. Then you might be able to login and set your DNS.
http://technet.microsoft.com/en-us/library/cc816897%28v=ws.10%29.aspx
I have had this problem for years and was looking for another solution. I have to unplug the NIC card then it comes up fast then I have to restart the NIC card then DNS, DHCP, AD… and what ever normally starts after the network is established..