Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

We have Exchange Server and two domain controllers. The problem is that we have one of the domain controllers down due to some hardware failures, but my exchange is not working with my second domain controller. Do we need to any modifications on exchange? What steps do we need to follow in order for our farm to be happy?

Note :- DNS has been configured on Both the servers.

share|improve this question
1  
By the way - "Dear Support" is a bad idea for a salutation on this site. We're not a support desk. This site is a way for professionals to ask questions to each other. –  mfinni Oct 27 '10 at 14:38
    
@mfinni you can always edit it ;) –  l0c0b0x Oct 27 '10 at 15:38
    
@l0c0b0x - sure, and I see you did. But I'm trying to educate a new user on the norms, and an edit might be overlooked. –  mfinni Oct 27 '10 at 15:48

3 Answers 3

Are both domain controllers configured as global catalogs? I'm guessing that the one that was down was your only GC. Assuming that you have a single domain and a single site, just make them both GCs, that's going to be the easiest thing to do.

share|improve this answer
2  
I always make my DCs Global Catalogs; with very few exceptions it makes sense for most (if not all) of your DCs to have a copy of the entire catalog. –  gWaldo Oct 27 '10 at 14:11

You can check what DCs that Exchange is using by:

Manager: Server Configuration -> Client Access, right click on a CA server, go to properties. On the System Settings tab will be the list of what DC/GC servers it is using.

Powershell: get-exchangeservers $HubCAName -status |select CurrentDomainControllers |fl

If your other DC is not in that list, you'll want to check the Application event-log on your CA server. The event ID is 2080 and should occur every 15 minutes. This lists the AD discovery process Exchange follows. For decoding what these events mean KB316300 describes it. This may yield clues as to why the other DC isn't being considered.

share|improve this answer

This redundancy would be determined by examining the FSMO roles of your active directory system.

Take a look at http://blogs.technet.com/b/mempson/archive/2007/11/08/how-to-find-out-who-has-your-fsmo-roles.aspx for a complete reference guide which will be a great resource.

share|improve this answer
1  
Please tell me what FSMO roles you think Exchange depends on. –  mfinni Oct 27 '10 at 15:28
    
Actions of operation and functionality. You might not be able to change passwords, create new distribution groups, add new users. If all remains the same then none. But since it ties into active directory I would most specifically count on having availability of the Infrastructure Master & PDC Emulator , 2 out of the 5 FSMO roles available. –  Nick O'Neil Oct 27 '10 at 15:42
1  
Nick - provide documentation that loss of the FSMO roles would stop Exchange entirely, which is what the OP is asking for. Also, none of those operations are isolated to Exchange, or even depend on FSMO roles in all cases. Password changes do not depend on PDCe (instant notifications to other DCs do though, to my recall.) Infrastructure master - wrong. Nothing to do with exchange. New user and groups will depend on DCs having a local RID pool, and if that pool is exhausted and the RID master is down there could be a problem. –  mfinni Oct 27 '10 at 15:54
1  
I don't think this is helping address the question posted or concerning to open discussion, a distraction I am accepting my -1 since I have stopped reading after seeing the word OP. Good day. –  Nick O'Neil Oct 27 '10 at 16:09
    
Nick - I'm happy to be educated if I'm wrong. –  mfinni Oct 27 '10 at 16:34

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.