We help IT Professionals succeed at work.

Exchange 2010 Dependant on Old DC

I have Exchange 2010 installed on its own DC, which is the FSMO role holder.  Its 2008 R2 server.
I also have an old DC running 2003.  Every time it gums up and I need to reboot it, Exchange on the new server dumps and wont start.  How can I rehome Exchange to the new 2008R2 server and make it so that even if the old one dies, there are no dependencies on the old box?
Comment
Watch Question

Sr. Systems Administrator
Commented:
you would use
Set-ADServerSettings -PreferredServer <server name>

How to Use a Specific Domain Controller in Exchange 2010 Management Shell
http://exchangeserverpro.com/how-to-use-a-specific-domain-controller-in-exchange-2010-management-shell/

also, exchange is not recommended to be installed on a domain controller

Installing Exchange on a domain controller is not recommended
https://technet.microsoft.com/en-us/library/ms.exch.setupreadiness.warninginstallexchangerolesondomaincontroller%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
Will SzymkowskiSenior Solution Architect
Most Valuable Expert 2015
Top Expert 2015

Commented:
I have Exchange 2010 installed on its own DC,
This not a recommended scenario. When Exchange is installed on a DC it only references this one. Also do not demote the DC where Exchange is installed on because that will break Exchange.

You will need to do the following steps
- bring up a new server 2008R2
- install Exchange (all roles)
- configure URL's / receive connectors/send connection
- move mailboxes to the new Exchange server
- point your new CAS role to the outside for 25/443 (NAT)

The decommission the old Exchange server.

Will.
AmitIT Architect
Distinguished Expert 2017

Commented:
Normally, I create different AD site dedicated to Exchange only. In your case, I might open MS case and ask them what I can do currently to overcome this situation and then plan for major change as Will said above.