Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 123
  • Last Modified:

DC on Exchange Server

One DC was crashed and we have already recreate the DC and granted to the domain again.

Under Exchange, it had removed the crashed DC but it doesn't add it back even though the DC is up and running now. This DC is a global catalog and DNS has been binded to this DC.

Is it possible to analysis on Exchange why it doesn't take up this DC in Exchange ? Tks
0
AXISHK
Asked:
AXISHK
  • 8
  • 7
  • 2
  • +2
1 Solution
 
Tony GiangrecoCommented:
It's not recommended to add the DC role to an exchange server unless it's a SBS server.
0
 
Thomas GrassiSystems AdministratorCommented:
What OS are the Servers? Windows 2003 Window 2008 ?
How many DC's do you have?
0
 
Seth SimmonsSr. Systems AdministratorCommented:
what version of windows and what version of exchange?
have you restarted the exchange server?  it should find the domain controller automatically - assuming the domain controller is in the same AD site
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Gareth GudgerCommented:
Assuming you have Ex2010, restart the Exchange Active Directory Topology Service on the Exchange Server.
0
 
AXISHKAuthor Commented:
Restart already but doesn't fix the problem. Any idea ??

Tks
0
 
Gareth GudgerCommented:
Are you sure the DC is back up and running correctly?

How did you recover the DC? Or did you just rebuild a new DC and gave it the same name and IP?

Are NETLOGON / SYSVOL shares available on the recovered DC? What happens if you run IPCONFIG /REGISTERDNS from the DC and wait a good 15 minutes?

Also, try running DCDIAG from command line on the DC. Anything happen?
0
 
Thomas GrassiSystems AdministratorCommented:
Question

How many DC's you running?

What OS are the servers?

What version of Exchange?
0
 
AXISHKAuthor Commented:
2 x Exchange 2010 running in DAG on Window 2008R2.

2 x Window 2008R2 DC + 1 x Window 2003 DC.

One DC is crashed and rebuilt with same name and IP address. Also check the netlogon and sysvol is not on the new created DC...

Is that the problem ? How to fix it ?

Tks
0
 
Gareth GudgerCommented:
Yea if SYSVOL and NETLOGON are missing then the DC is not functioning correctly. Was this a fresh install to rebuild this server? If so, before you gave it the same name and IP, did you do a proper cleanup of the old DC out of Active Directory? Metadata cleanup etc.

Safest option may be to demote, give it a new name and IP and them promote back.
0
 
AXISHKAuthor Commented:
We haven't done Meata cleanup. Simply depromote the old DC. Reinstall a fresh copy on another computer and promot it again.

We also install another new DC and we encounter the same problem, sysvol and netlogon not appears...

Tks
0
 
Gareth GudgerCommented:
Can you run DCDIAG from a command prompt on the problem DCs. Post your results here.
0
 
AXISHKAuthor Commented:
Fix the issue follow the link http://support.microsoft.com/kb/315457/en-us

Thanks for all comments
0
 
Gareth GudgerCommented:
Awesome. So as soon as you did this, the DC showed up on the Exchange server right?
0
 
AXISHKAuthor Commented:
Correct. Tks
0
 
Gareth GudgerCommented:
I disagree with the moderation here. ID: 40016580 prompted the original poster to look if SYSVOL was present or not. At that point it was determined it was not present. Which led to the solution.
0
 
AXISHKAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for AXISHK's comment #a40017756

for the following reason:

Tks for all comments. I have rebuilt the sysvol.
0
 
Gareth GudgerCommented:
I disagree with the moderation here. ID: 40016580 prompted the original poster to look if SYSVOL was present or not. At that point it was determined it was not present. Which led to the solution.
0
 
AXISHKAuthor Commented:
Tks
0
 
Gareth GudgerCommented:
Thanks all!
0
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.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 8
  • 7
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now