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

EE

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.
LVL 1
drivenitAsked:
Who is Participating?

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

x
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.

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:

http://technet.microsoft.com/en-us/library/ee692764.aspx
0
drivenitAuthor Commented:
Hmmm so is this not really the problem them. because i still have to have DC1 online in order to start exchange.
0
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
0
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!

VirastaRUC Tech Consultant Commented:
Hi,

Check this

Exchange DSAccess / ADAccess and AD site Link
http://blogs.technet.com/b/sukum/archive/2013/02/08/ds-access-ad-access-and-ad-sites-link.aspx

Hope that helps :)
0
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)      
In-site:
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      
Out-of-site:
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.
0
drivenitAuthor Commented:
Virastar,

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.
0
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
2080 looks fine please ensure that no DC\GC is hardcoded

- Rancy
0
drivenitAuthor Commented:
EE

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
0

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
drivenitAuthor Commented:
It ended up being a 2nd NIC
0
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
Windows Server 2012

From novice to tech pro — start learning today.