• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 695
  • Last Modified:

Exchange 2013 won't operate if a specific DC is offine


I have 2 windows 2012 DC's, 1 Exchange 2013 server.

One DC (I'll call it DC1) is getting shipped to a different state. it so happens to be the first DC in the domain. So originally it owned all the FSMO roles. I've moved those to DC2

I have another DC (i'll call it DC2) that will sit onsite with the exchange 2013 server.

my problem is if i turn off the DC1 the one i'm shipping to another state, exchange crashes and if i reboot exchange services won't start.

After running this command

Get-ADServerSettings | fl

I've found out that DC1 si the dfault for everything.

I've also ran these commands to change the GC and Primary DC for exchange.

Set-ADServerSettings -PreferredServer DC2.domain.local

Set-AdServerSettings -ViewEntireForest $True -PreferredGlobalCatalog DC2.domain.local

but that only works for current session and reverts back.

Here are my questions.
How can i get Exchange to look at DC2 permanetly so i can turn DC1 off and not have troulbe?
Is the default DC server in exchange the reason i can't get services to start if DC1 is off?
For this problem am i looking in the right direction?

Thanks for any help you all can offer.
1 Solution
Stelian StanNetwork AdministratorCommented:
You are right Set-ADServerSettings applies only to the current session. If you want the setting to be applied each time you open a new session you could look at using a PowerShell profile:

drivenitAuthor Commented:
Hmmm so is this not really the problem them. because i still have to have DC1 online in order to start exchange.
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Can you check event 2080 and share

Also not sure if you have hardcoded some DC\GC with the Exchange ?

- Rancy
7 new features that'll make your work life better

It’s our mission to create a product that solves the huge challenges you face at work every day. In case you missed it, here are 7 delightful things we've added recently to monday to make it even more awesome.

VirastaRUC Tech Consultant Commented:

Check this

Exchange DSAccess / ADAccess and AD site Link

Hope that helps :)
drivenitAuthor Commented:
Here is what event id 2080 states

  Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2152). Exchange Active Directory Provider has discovered the following servers with the following characteristics:      
 (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)      
DC2.domain.com      CDG 1 7 7 1 0 1 1 7 1
DC1.domain.com      --G 1 7 7 1 0 1 1 7 1      
DC2.domain.com      CDG 1 7 7 1 0 1 1 7 1
DC1.domain.com      CDG 1 7 7 1 0 1 1 0 1

looks like dc2 is listed first but not sure what that means.
drivenitAuthor Commented:

Good article explains a lot, I wonder after reading that link if my issue is straight up DNS or if i accidentally hard coded DC1 to exchange.
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
2080 looks fine please ensure that no DC\GC is hardcoded

- Rancy
drivenitAuthor Commented:

Thank you for your help in this issue. Looks like it was a problem with routing. I did not realize there was two NIC's on my DC2 server. Once i disabled the 2nd Nic and cleaned up DNS everything worked it's self out. It must of been some sort of routing issue and was not getting clean communication.

Thanks for the help
drivenitAuthor Commented:
It ended up being a 2nd NIC
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

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now