Having an odd problem. We have a Windows 2008 R2 Standard server running the following roles: AD, DNS, File Server, Hyper-V. The server is an HP DL360 G5.
Whenever the server reboots, DNS and Intersite Messaging will not start automatically, even though they are set to do so. This problem has started occurring within the last month. I can manually start these services just fine. Someone in another thread suggested I set them to "Automatic (Delayed)" start, and when I do they also eventually start. However, though this solves the most critical problem, it still generates errors upon boot up because AD goes a little wonky when it can't determine the namespace.
The error logs show generic errors like" The Intersite Messaging service terminated with the following error: The specified server cannot perform the requested operation." Replace Intersite Messaging with DNS and you get the same error...
The other thread suggested this might be a conflict in the startup order and to try delaying the start. If this is indeed the case, I'd rather delay other services that aren't as critical. But neither solution is a good one because you shouldn't have to do this.
Any ideas would be helpful.