My Exchange 2007 services do not start on the initial boot of the server. After the server boots, then I wait a few minutes I can successfully start the services manually. The first error in the event viewer is: 2103 "All global catalog servers are not responding". I also get the following errors in this order: 8359 he Recipient Update Service is slow to start because of network issues. The service will continue to retry until it successfully restarts. Until that time, not all Recipient Update Service features will be available. 2601 Process MSEXCHANGEADTOPOLOGY (PID=1652). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account <WKGUID=DC1301662F547445B9C490A52961F8FC,CN=Microsoft Exchange,CN=Services,CN=Configuration,...> - Error code=80040934. The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions. 1121 Error 0x96e connecting to the Microsoft Active Directory. 5000 Unable to initialize the Microsoft Exchange Information Store service. - Error 0x96e. 8213 The Microsoft Exchange System Attendant service failed to create session for virtual machine. The error number is 0x80040115. I am running the Exchange server on a domain controller (I know...not recommended) that is also a global catalog server. dcdiag and netdiag both pass just fine. I'm confused as to why it won't start up initially but will manually after waiting a few moments. Is it having trouble connecting to AD? The Exchange server possesses all the domain master roles. There is another DC on the network but it is not a master DC and Exchange is set to use itself as the DC. Any ideas?

Keeping Infrastructure Master& Global Catalog on the same server is not a good option. Remove GC from your Exchange server. manually replicate zones from all servers to each other by navigating in "Sites and services" . Do inter site replication if you dont have any child domain over the WAN link. Which anti virus/ anti spam system you are running on the Windows Server 2003 machine hosting Exchange 2007 ?

I moved the global catalog and that cleared up most of the problem, but MSExchangeSA would load then fail with an error about not being able to contact the local security authority. I found this doc: http://support.microsoft.com/kb/940845/en-us that addresses this problem specifically (funny...I've been searching for this info for weeks!). I tried all of their suggestions except for the BootPause solution. I tried it last and it worked! Thanks for your help. :-)

I've had this with Exchange and other services - can be caused by it not being able to contact AD, so can't logon services etc, add other DCs to allow it to contact the servers that are already up on the network or try and script / delay Exchange startup until after AD has started fully on boot. Good Luck! Adam