Solved

Exchange 2003 reliance on Domain Controller

Posted on 2004-09-21
6
315 Views
Last Modified: 2007-12-19
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.







0
Comment
Question by:hnad
  • 3
  • 3
6 Comments
 
LVL 104

Accepted Solution

by:
Sembee earned 500 total points
ID: 12111056
Exchange will attach itself to a certain GC domain controller. While it can find another one when the original has gone (reboot, shutdown etc) it doesn't do this immediately. It can take a little while - I have seen over 30 minutes before failover takes place.

There are two ways to resolve this problem - don't reboot the GC that it is attached to unless you need to reboot the Exchange server as well, or change the GC that it is using in ESM before the reboot.

Simon.
0
 
LVL 1

Author Comment

by:hnad
ID: 12117681
In the ESM under Server Properties/Directory Access I have both DC's listed as DC (auto) and GC (auto)

The Primary DC also has another entry: Config (auto) which points to LDAP 389. What is Config (auto)? Should I have an entry for this for the second DC?

I'm just trying to understand what will happen in case of a disaster with the Primary DC. 30 minutes seems like a long time for it to attach itself to the second GC especially if it's listed in Directory Access.

Thanks
0
 
LVL 104

Expert Comment

by:Sembee
ID: 12117747
If the primary DC went down then the quickest way to get Exchange to attach to another GC is to simply reboot it. I have had to do that in the past.
That second entry is where Recipient Update Services points. That needs LDAP access to update the user account information. That can only point at one server, but can be easily changed in ESM should it be required.

Simon.
0
Don't lose your head updating email signatures!

Do your end users still have the wrong email signature? Do email signature updates bore you or fill you with a sense of dread? You can make this a whole lot easier on yourself by trusting an Exclaimer email signature management solution. Over 50 million users do...so should you!

 
LVL 1

Author Comment

by:hnad
ID: 12117921
Ok thanks Sembee.

One last question just to be clear. FSOM roles have no effect on exchange operations? All Exchange needs is a GC server correct?

I understand about moving or forcing FSOM roles to another server. I just want to be clear that Exchange does not require access to a server with these roles to function properly.

Thanks.

0
 
LVL 104

Expert Comment

by:Sembee
ID: 12117981
The active directory will need access to a server with the FSMO roles to function, but Exhcange itself needs a GC and a domain controller - that is all. You should have no problems moving the roles as the server will find them if required.

Simon.
0
 
LVL 1

Author Comment

by:hnad
ID: 12118162
Awsome thanks for your help.
0

Featured Post

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
This video discusses moving either the default database or any database to a new volume.

863 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

25 Experts available now in Live!

Get 1:1 Help Now