I have a main server running Windows 2008 R2 setup as a domain controller, dhcp server and dns server, on it stupidly I have running Exchange 2010 (I did this because the budget would only let me get one server).
A year later I was able to get a second server that is also running Windows 2008 R2 setup also as a domain controller, and dns server.
This morning the main server had some error with vss shadow copy reader starting, immediately after that Exchange could no longer find the active directory, and all email services stopped working. I have found that if I stop and start the active directory service, and then manually start all of the exchange services I can get it running again, but on a reboot it is back being foobarred.
I am primarily a web developer who does server management on the side (i.e. I have a lot of holes in my knowledge) What are some things I can try to fix this problem?
Ok I found that the netlogin service isn't starting, but when I start it manually, that's when I can start all the other services mentioned above.
Best Answer
Is the DC/Exchange device configured to use the second DC as an alternate DNS server?
Sounds like AD services are having a hard time starting up, which may be due to a less-than-ideal DNS situation.