Slow restarts after exchange install

From: scott (scott_at_denalinet.net.nospam)
Date: 05/31/04 

Date: Mon, 31 May 2004 12:50:07 -0800

Before exchange was installed, a server reboot took about 5 minutes. After
exchange was installed the restart can take as long as twenty minutes. The
server appears to hang on the "windows is shutting down" message. Drive
activity during this period is non existent. No messages in the event
viewer.

I created a batch file to shutdown the exchange services before I restart.
This helps by about 3 minutes. Any ideas?

Windows server 2003 enterprise
Exchange 2003
Dual P4 2.8 Ghz
4 Gbyte RAM
5 72 Gbyte SCSI Drives (RAID 5)

Relevant Pages

  • Re: Exchange Disaster Recovery Server
    ... The backup server is setup also in the lab so I ... >>> The Microsoft Exchange Server computer is not available. ... >>> Microsoft Exchange Server Information Store ...
    (microsoft.public.exchange2000.admin)
  • Exchange 2003 SP1 periodicaly losses connection to active directory for about 30 minutes
    ... We have active directory in two servers but the mail server fails to ... the promotion of the server to active directory the exchange was up. ... After a Domain Controller is promoted to a Global Catalog, ...
    (microsoft.public.exchange.connectivity)
  • Exchange 2003 SP1 periodicaly losses connection to active directory for about 30 minutes
    ... We have active directory in two servers but the mail server fails to ... the promotion of the server to active directory the exchange was up. ... After a Domain Controller is promoted to a Global Catalog, ...
    (microsoft.public.exchange.misc)
  • Re: LDAP Bind Unsuccessful
    ... We have a similar problem with Exchange 2003 and two DC servers 2003. ... After a Domain Controller is promoted to a Global Catalog, ... server that is designated to be a Global Catalog Server but did ...
    (microsoft.public.exchange2000.active.directory.integration)
  • Re: Upgrading from 2000 Server w/ Exchange 5.5
    ... "I'm assuming that Exchange 2000 schema updates have not been applied to the ... your first step would be to get some hardware and install Windows Server ... test that DNS is correctly configured and is replicating ...
    (microsoft.public.windows.server.general)