Preferred Domain Controller in Exchange

The preferred domain controller parameter is being shown as blank by Exchange server. I have two domain controllers in my environment. I am running the given below command to check preferred domain controller used by Exchange server.


ConfigurationDomainController               PreferredDomainControllers     PreferredGlobalCatalog RecipientViewRoot ViewEntireForest
----------------------------- -------------------------- ---------------------- ----------------- ----------------
                                                                                   {}                                                                                         False

Q1: Exchange selects itself any one domain controller as preferred domain controller or should we have to set one domain controller as preferred domain controller for Exchange?

Guys whats your Expert thoughts on this?
Muhammad AsifSenior Solutions ArchitectAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MASEE Solution Guide - Technical Dept HeadCommented:
Mal OsborneAlpha GeekCommented:
That is normal, and fine.

Exchange will find a DC just like a client machine. Usually, if you had several DCs in different offices, you would have sites set up in AD, Exchange would use this to try to "nearest" DC first.

There may be some situations where you would prefer Exchange to pick a DC outside of the usual process, but this would be unusual.
Muhammad AsifSenior Solutions ArchitectAuthor Commented:
Hi MAS and MAL ,

Thanks for your reply. I am using Exchange 2016 on Windows server 2016.   We have four Exchange servers in primary site and two in DR site.
We want that Exchange servers located in primary site use primary domain controller located in primary site and vice versa. If primary domain controller goes down then Exchange should use secondary Domain Controller as preferred domain controller in same site.

Q1: How we can achieve this?

Q2. By default Exchange use what domain controller as preferred domain controller?

How we can achieve this?
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Muhammad AsifSenior Solutions ArchitectAuthor Commented:
Hi Mal,

Thanks for your expert opinion and its very much clear to me know. I would really appreciate if you clarify the below as well.

Q1.  By default Exchange use what domain controller as preferred domain controller (if one site have two domain controllers)?
Mal OsborneAlpha GeekCommented:
It will determine the DC to use via DNS, which will round robin responses, in accordance with the SRV record weight.

By default, each DC in the local site will be used half the time.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Muhammad AsifSenior Solutions ArchitectAuthor Commented:
So By default Exchange does not use any domain controller as preferred domain controller?

BTW, I haven't created any SRV record in DNS. So Is it fine to just keep by default settings.
Mal OsborneAlpha GeekCommented:
If you set a lower priority (higher number) on one DCs SRV record, then the Exchange server will only use that one, unless it is down. Every other machine on the LAN will do the same, so the "standby" DC will actually not do anything.
Mal OsborneAlpha GeekCommented:
When you install a DC, it populates the DNS server with a heap of records, including relevant SRV records.

Here is a screenshot of one:

Muhammad AsifSenior Solutions ArchitectAuthor Commented:

Thank you so much for your detail reply. Now I have crystal clear concept. Just want to clarify last thing. The priority of SRV record is set 0 for both my Domain Controllers. Now what will happen in this case?  You may also refer to attached screenshot.
Muhammad AsifSenior Solutions ArchitectAuthor Commented:
Moreover, what field ( kerberos or LDAP) shell we need to change to change the priority? @MAL can you please comment on this as well.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.