Exchange 2003 reliance on Domain Controller
Posted on 2004-09-21
Hi, this has been bugging me as I'm trying to work out why exchange functionality stops when I restart the primary domain controller.
I have 2 win2k domain controllers and 1 Exchange 2003 on Windows 2003 member server.
GC is available on both Domain Controllers. 1 DC server has all the FSOM Roles.
Now if I reboot the primary domain controller with the FSOM Roles exchange stops working.
What exactly does Exchange 2003 need to be operational. I thought all it needed was one global catalogue server to be functional??
Is there a particular FSOM role that exchange requires access to on a server? Or do I have a problem with my second GC server? I did notice LDAP errors in event viewer with exchange trying to connect to the second DC GC server after stopping the Primary Domain Controller.
Hoping someone can explain this simply.
Thanks for your time.