Exchange 2003 does not start without a DC

Hi I am looking for information on why Exchange 2003 does not start without a DC. We have a customer who recently had an outage of there FSMO DC GC box. Unfortunately there was not a 2nd DC. When this server was down no one could access Exchange.

Upon researching what requirements Exchange 2003 needs in regards to FSMO, DC GC I have been unable to find any information.

So once the issue was resolved we promoted a 2nd DC and then several days later we then took down the FSMO sever to see if we could access Exchange. But we were still unable.

Can anyone point me to information about this or even better what Exchange 2003 needs to start so that if one server goes down (FSMO) it doesn’t take the Exchange 2003 server with it.

Thanks in advance.
TEAMnetwork SystemsAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SembeeCommented:
Basically Exchange requires a domain controller, which needs to be a global catalog. It is constantly querying the AD as that is where all the information on the Exchange configuration is stored - Exchange doesn't store it itself.

If the DC/GC that Exchange is attached to goes down, then Exchange will eventually fall over. It can take 30 minutes before Exchange goes looking for another DC. What I normally do is kick all the users out and reboot.

As a bare minimum I would have two domain controllers, both of whom are global catalogs. If one of those needs to be rebooted, then that can usually be done without upsetting Exchange too much.
If the server holding the key domain roles fails (ie isn't just down for some work) then you will have seize the roles. If you are taking it down to remove it then you should DCPROMO the server out and make sure that the roles have been transferred correctly.

Bottom line is that with just a single domain controller you are exposed to a single point of failure.

Simon.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
TEAMnetwork SystemsAuthor Commented:
Thanks Simon

Is this documented anywhere?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.