Anyone have any ideas why it takes almost 13 minutes to reboot any of my exchange 2007 servers? The servers are still pingable, yet, they haven't rebooted. I checked the event log and almost 13 minutes pass between the event log stopped and the event log started, and I see no error messages. It just sits there. Could it be that exchange is stopping services or something? Is there a correct method to reboot an exchange server such as in 2003 I stopped the system attendant which stopped the other major services, but the same is not true for 2007. This is very weird. Any ideas guys? Thanks Erik

What is the DNS suffixof your local windows-domain ? .local or .com ?

It is a childdomain with a .com

Any body got any ideas?

The idea is (was) that there is DNS-server installed on that server and this DNS-server tries to update and transfer some records in higher-level DNS-server, but the higher-level DNS-server denies to accept the notifications and there are timeouts.

disconnect the network cable while rebooting

On an Exchange Server, it is always a good idea to stop all Microsoft Exchange Services BEFORE a reboot! That will shave of minutes of the going down time!