<div>
Does the 2008 DC point to itself for DNS? Is it also a Global Catalog Server and hold all of the FSMO roles?<br />
<br />
Also within Exchange what DC is Exchange trying to point to? Make sure that it is pointing to the 2008 DC. <br />
<br />
Open the Exchange Management Console and do the following...<br />
- click on server configuration<br />
- in the right pane select the Exchange server, right click select properties<br />
- select the system settings tab<br />
- check and see if it is pointing to the old DC still<br />
<br />
<br />
Will.
</div>


<div>
2008 Server points at its own IP for DNS and hosts the DNS service. &nbsp;This server also holds all the FSMO roles. &nbsp;<br />
<br />
For the 2nd question, I cant open the exchange management to see what it points at since the services wont start. &nbsp;If you have a reg key or adsiedit value I can check it.
</div>


<div>
And yes the 2008 server is also aa GC, but I checked a bunch of my other single server clients and their sole DC is also a GC by default.
</div>


<div>
Does powershell work for you? If not the EMS try using a regular powershell session and add the pssnap-in for Exchange. Then run the Get-ADServerSettings | fl command and see what it is pointing to. <br />
<br />
Will.
</div>


<div>
Hang on, setting all the services to manual. &nbsp;Some are hung starting or stopping. &nbsp;Any chance you know what services need to be running for the EMS to start properly? &nbsp;I'm going to reboot and start each manually.
</div>


<div>
Cant start the EMS. &nbsp;Now what?
</div>


<div>
It is not a recommended setup to have Exchange installed on a domain controller. What you might need to do is spin up another Exchange server (own hardware) and restore your mailboxes to the new Exchange server. At that point decommission the one that is installed with the DC.<br />
<br />
Will.
</div>


<div>
its worked fine for 5 years, no other option at this point. &nbsp;Need to get it back up by 8am or I'm dead.
</div>


<div>
DCPROMO the 2003 machine back in. From there you can run EMC. It should be pretty quick and easy, and will at least buy you some time.
</div>


<div>
Paid $500 for Microsoft to fix it
</div>


<div>
<div class="content wysiwyg-content">
Here is what I have. &nbsp;<br />
2 Servers<br />
1 is 2003 running as a DC<br />
1 is 2008 running as a DC and hosts Exchange 2010<br />
I did a dcpromo and removed the 2003 server from AD as a DC. &nbsp;Now Exchange wont start on the 2008 server. &nbsp;I'm getting system errors 7031 7024 and application event ids 2114 2604 2012 5000 and 1121 &nbsp; All are related to Active Directory and services unable to start.<br />
<br />
I tried a setup /preparead and it tells me that it cant find the recipient update service.<br />
What a pain. &nbsp;A simple DC removal is now a 10 hour project. &nbsp;Any help is appreciated.
</div>
</div>


Here is what I have.  
2 Servers
1 is 2003 running as a DC
1 is 2008 running as a DC and hosts Exchange 2010
I did a dcpromo and removed the 2003 server from AD as a DC.  Now Exchange wont start on the 2008 server.  I'm getting system errors 7031 7024 and application event ids 2114 2604 2012 5000 and 1121   All are related to Active Directory and services unable to start.

I tried a setup /preparead and it tells me that it cant find the recipient update service.
What a pain.  A simple DC removal is now a 10 hour project.  Any help is appreciated.

Removal of 2003 DC Stops Exchange 2010 Services from Starting

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.