Link to home
Start Free TrialLog in
Avatar of Generator
GeneratorFlag for Canada

asked on

Windows 2003 Server - Additional DC and Exchange Conflict

We have an AD domain with one DC, one Terminal Server and one Exchange server. We wanted to add another DC to the group to allow for load sharing and have some redundancy. The additional DC was programed as per the first one and allowed to replicate with the first DC. As a test we removed the first DC from the domain and discovered that the Exchange server would not function with the new DC. Upon re-instating the first DC the Exchange server worked fine. Why would the introduction of the second DC cause the Exchange server to malfunction?
Avatar of theruck
theruck
Flag of Slovakia image

its probably because of the FSMO roles holder
have a look at http://support.microsoft.com/kb/223346
i think that you should consider to add a global catalog role to the exchange server to be able to authenticate user access
ASKER CERTIFIED SOLUTION
Avatar of Nenadic
Nenadic
Flag of Serbia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of shankshank
shankshank

Yeah the global catalog. It is what exchange uses. once you promote that DC to GC you will be good to go np
oops from experience, it may be helpful to install DNS on that 2nd DC and also specify in your exchange that 2nd dns server, so that if 1st dc goes down, you will be ok
Avatar of Generator

ASKER

Sorry I didn't get back to this question - we have been completing other projects. Please leave this question open for now and I will try the recommendations as suggested as soon as possible. Thank you all for your input - much appreciated.