Windows 2012 servers running Exchange 2016 VM's.
on the Exchange 2016 servers this week.
Still noticing a rather lengthy period of server unresponsiveness after each reboot.
Remember how RDP is not available for about 5 minutes.)
It turns out the server itself shows symptoms of a service or process hang when logging in directly from the console (instead of RDP).
The desktop appears, but if you try to launch an MMC, such as services, or event viewer, nothing happens.
If you wait about 5 minutes, the consoles you’d tried launching suddenly appear, RDP becomes available, and the server seems fine again.
The Microsoft Exchange Health Manager service hung on starting.
· The Microsoft Exchange Diagnostics service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
· A timeout was reached (30000 milliseconds) while waiting for the Microsoft Exchange Diagnostics service to connect.
(This service doesn’t appear to start properly on any of the 2016 VMware servers):
If I set the above services to ‘Automatic (Delayed Start)’, though, the unresponsive period drops from about 5 minutes to around 90 seconds.
Still not ideal—we have other 2012 R2 VMs that don’t experience this issue at all; you can RDP into them within 5 seconds of the CTRL-ALT-DEL screen appearing.