There seem to be many_ldap records listed as SRV records. Is there a specific branch I should be making the changes on?
_msdcs
_sites
_tcp
_domaindnszone
_forestdnszones
Main Topics
Browse All TopicsI have Active Directory running on two Windows 2003 Server Standard boxes with Exchange 2003.
Here is the process of what has happened and I am not sure quite why.
I setup my domain with my PDC on a Dell Xeon 2.8Ghz server and Exchange on another server w/ the same specs.
Later on I introduced a secondary domain controller into my network, this server running on an old Dell PIII 800mhz machine (More as a precautionary measure than anything else.)
Upon doing that my exchange server is constantly referring to the secondary domain controller for all active directory tasks. It should be using the primary as it is running on superior hardware.
All domain controllers are running W2k3 SP2 and Exchange is still running Win2k3 SP1.
Any info is greatly appreciated.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I've done a bit of reseatch and it would appear that changing the registry so that the LDAP records are actually registered with a different priority inthe forst place is the preferred option - see http://books.google.com/bo
Exchange will use the first domain controller to respond. Once it has attached itself to a domain controller it will use that one exclusively until it is rebooted. Then it looks again.
You should not consider forcing Exchange to use a specific domain controller as that can have performance issues if that DC then goes down for any length of time.
Unless you are running a very high number of users on very low spec hardware, you shouldn't see much of a performance hit with a less spec dc. Domain lookup is such a low use of resources anyway.
Simon.
--
Once your question has been answered, please remember to accept an answer and close the question.
Exchange will not fail over to another domain controller for about 35 minutes. It is not instant and that behaviour cannot be changed.
Exchange only uses global catalogs for its AD functionality. However as far as I am concerned, if you only have two domain controllers having the second one NOT set as a global catalog is a waste of time.
Simon.
--
Once your question has been answered, please remember to accept an answer and close the question.
As I stated above - Exchange will use the first server to respond. Has nothing to do with the specification of the servers.
With 30 uses, you could run DCs on PIII 500s with 256mb of RAM and not see any difference. Once the DC has booted up it will be fine.
You could run 300 users on that spec.
Simon.
--
Once your question has been answered, please remember to accept an answer and close the question.
Business Accounts
Answer for Membership
by: KCTSPosted on 2007-10-29 at 12:07:59ID: 20172308
There is no such thinh as a primary and secondary Domain controller in Active Directory, Machines will respond to the first Domain Controller in their own site that they come across - all being equal. Want you can do however is to make them unequal. Find the SRV LDAP record(s) for the second server in DNS and increase the priority. echnet/pro dtechnol/w indows2000 serv/ reski t/distrib/ dsbc_nar_s dns.mspx?m fr=true
see http://www.microsoft.com/t
for details of the SRV records