[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Exch 2010 loses connection to AD when old DC is shut down

Posted on 2014-08-15
21
Medium Priority
?
1,059 Views
Last Modified: 2014-08-28
I have an old Server 2003 machine that has been acting as the domain controller for the network. I installed a brand new Server 2008 R2 machine, joined it to the network, ran adprep32 on the old server to prepare it so I could elevate the 2008 server to a DC. Did all of that and it was successful. I transferred all of the FSMO roles over from the 2003 to 2008 server successfully. I changed the DNS settings on each server so that it points to the new 2008 DC first then the old one second. My Exchange 2010 server (separate 2008 R2 machine) works fine as long as the old 2003 DC is up and running. But once I shut it down, mail stops working. If I try to go to OWA, it lets me log in but then I get the message "A server that contains information about your user account and mailbox can't be found." It looks like the Exchange Server is not looking at the new DC.
0
Comment
Question by:stevenstrick
  • 10
  • 6
  • 5
21 Comments
 
LVL 1

Expert Comment

by:KHSIT
ID: 40263212
Did you update your domain controller settings inside of Exchange 2010?  If you didn't, go to Organization Configuration and then on the left colum, click Modify Configuration Domain Controller and force it to point to your 2008 DC.
0
 
LVL 1

Expert Comment

by:KHSIT
ID: 40263236
Sorry, I meant right column.
0
 

Author Comment

by:stevenstrick
ID: 40263273
Found it and made the change. But, I have a question. Shouldn't Exchange automatically look at the new DC without having me hard code it?
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 1

Expert Comment

by:KHSIT
ID: 40263297
It should but I've found that most times it won't when the 2003 server is still in use. I would definately be careful when you completely remove the 2003 DC.  Make sure that after you run dcpromo to remove it that you check to make sure your Exchange is still running correctly.
0
 
LVL 1

Expert Comment

by:KHSIT
ID: 40263302
The easiest way to check before running dc promo is after making the above change, try shutting down the 2003 DC and then restart your exchange server.  After it comes back up you can verify that it still works  before removing the 2003 server completely.
0
 

Author Comment

by:stevenstrick
ID: 40263313
Thanks. I'll give that a go
0
 
LVL 1

Expert Comment

by:KHSIT
ID: 40263318
Just out of curiosity, did you migrate from Exchange 2003 to Exchange 2010?  I'm finding that most users with this issue went from 2003 directly to 2010 and skipped 2007.
0
 

Author Comment

by:stevenstrick
ID: 40263353
Yes we did. Migrated from Exchange 2003 to 2010
0
 

Author Comment

by:stevenstrick
ID: 40264604
So, after making that change, I shut down the old 2003 DC. Outlook clients in the office could no longer connect to Exchange and when I tried to use OWA, I could login but then I got the message, "A server that contains information about your user account and mailbox can't be found." I'm missing something here. Anyone have an idea?
0
 
LVL 12

Assisted Solution

by:Steven Wells
Steven Wells earned 1500 total points
ID: 40265808
It sounds like your exchange environment is still referring to your old exchange 2003 server.  The exchange server information is an active directory object, which should be updated when mailboxes are migrated from exchange 2003.  Are there any DNS entries still pointing to your old exchange server or DC?
0
 

Author Comment

by:stevenstrick
ID: 40266387
That mailbox migration occurred a while ago with no issues.I have checked the DNS settings on the Exchange, old DC and new DC and they all point to the new DC first.
0
 

Author Comment

by:stevenstrick
ID: 40266414
In the EMC on the Exchange 2010 server in Server Configuration, Mailbox Properties, under System Settings, it is pointing to the old DC under Domain Controller servers being used by Exchange and Global Catalog server being used by Exchange.
0
 
LVL 12

Expert Comment

by:Steven Wells
ID: 40266505
Confirm your new domain controller is global catalogue server?
0
 

Author Comment

by:stevenstrick
ID: 40266521
Confirmed.
0
 
LVL 12

Expert Comment

by:Steven Wells
ID: 40266528
Have you rebooted exchange since dc removal?
0
 
LVL 12

Expert Comment

by:Steven Wells
ID: 40266532
It would be useful to see if any errors are logged to event log.
0
 

Accepted Solution

by:
stevenstrick earned 0 total points
ID: 40270684
OK I checked my event manager on the Exchange 2010 box. MSExchangeDSAccess was showing both domain controllers with different result codes. My new DC had a code of 177100171 where it should be 188101171. Did some research and found that the SACL rights were not set on the new DC. On the new DC, went to Local Security Policy, expanded local policies, then user rights management. Checked Manage Auditing and Security Log and added Exchange Enterprise Servers and Exchange Servers groups. My Exchange Server now sees both DCs.
0
 
LVL 12

Expert Comment

by:Steven Wells
ID: 40271079
Sounds like you are getting close. Everything should work now.
0
 

Assisted Solution

by:stevenstrick
stevenstrick earned 0 total points
ID: 40271105
have to wait to shut down the old DC to confirm.
0
 
LVL 12

Assisted Solution

by:Steven Wells
Steven Wells earned 1500 total points
ID: 40271118
You will need to still de-dc promo the old one out. Exchange may also need rebooting to force the dc bindings to update.
0
 

Author Closing Comment

by:stevenstrick
ID: 40289853
After doing some research online, I found the solution.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

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.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Wouldn't it be nice if objects in Active Directory automatically moved into the correct Organizational Units? This is what AutoAD aims to do and as a plus, it automatically creates Sites, Subnets, and Organizational Units.
The main intent of this article is to make you aware of ‘Exchange fail to mount’ error, its effects, causes, and solution.
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …
This video shows how to use Hyena, from SystemTools Software, to update 100 user accounts from an external text file. View in 1080p for best video quality.
Suggested Courses

873 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question