Exchange Server Forums

Exchange 2010 - not recognizing new AD DC that has been promoted...

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2010] >> General >> Exchange 2010 - not recognizing new AD DC that has been promoted...

Page: [1]

Message

<< Older Topic Newer Topic >>

Exchange 2010 - not recognizing new AD DC that has been... - 9.Jan.2012 6:16:49 PM

pichels

Posts: 2
Joined: 9.Jan.2012
Status: offline

Hi-

We would like to know what we can do when our Primary AD DC fails and our Exchange 2010 server cannot see it anymore.
Can we tell Exchange Server find or fail over to another DC w/ a GC?
Is this always manual - we had to run setup.com /preparead and change DNS settings last time.

Or can we automate in case of a DC failure?
We are worried about our Email servers having issues after a DC fails.
Make sense?
Thx.

-P

Post #: 1

Featured Links*

RE: Exchange 2010 - not recognizing new AD DC that has ... - 9.Jan.2012 6:22:39 PM

mark@mvps.org

Posts: 6812
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline

It's already automated. You should not need to do anything.
Have you done anything hinky with your subnets and/or AD sites.

Unless you have inadvertently broken something if your new DC is shut down your Exchange should it stop.

One thing though. Did you make the DC a GC as well, and bounce it for luck?

_____________________________

Mark Arnold (Exchange MVP)
List Moderator

(in reply to pichels)

Post #: 2

RE: Exchange 2010 - not recognizing new AD DC that has ... - 9.Jan.2012 7:37:36 PM

pichels

Posts: 2
Joined: 9.Jan.2012
Status: offline

Hi-

We had a DC fail - example = DC1 - the primary(GC with roles, etc.) - our Exchange servers failed to work properly after this happened.
No AD site or DNS changes that I know of.

The Exchange Servers used to point to the old DC = DC1.
We had another DC that already had the GC - but, was not primary and we seized the roles and made it primary --> DC2.

The old DC1 was still in the AD DB - it was not operational - corrupt DB and could not be restored.
It was connected to the network for users to access files but in AD restore mode(safe mode).

Later - we finally removed it from the AD DB using metadata cleanup.
But, I wonder if we should have ran metadata cleanup right after the promotion of DC2 and then restarted out DC's and Exchange Servers?

Does this make sense?
Thanks for the reply!

-P

(in reply to mark@mvps.org)

Post #: 3