<div>
You can try to rename it back but I don't think you'll be able to due to domain connection issues.<br />
<br />
Can you do a restore from a previous backup?<br />
<br />
If not you can try to rename it using the NETDOM command.<br />
<br />
<a href="https://technet.microsoft.com/en-us/library/cc816601(v=ws.10).aspx" rel="ugc">https://technet.microsoft.com/en-us/library/cc816601(v=ws.10).aspx</a>
</div>


<div>
No luck with renaming the server back or with netdom. &nbsp;I do not have a backup of the new server. &nbsp;That was my next step. &nbsp;Not worried about the user data. It's on both servers and backups.<br />
<br />
I have a backup of my recently demoted 2003 dc (prior to demotion).<br />
<br />
If I restore it to a dc then both servers will have the same name.<br />
<br />
Not sure where to go from there.
</div>


<div>
The only thing I can think to have you try is to take the 2012 off of the network, restore the backup of your 2003 DC, bare-metal rebuild the 2012 and see if that will get you up and running.<br />
<br />
If you don't want to take that risk, I'd put a call into Microsoft, pay the fee and let them see if they can guide you through this.<br />
<br />
I used to work for MS as an Exchange Engineer and I know they have tons of internal information for fixing things that we don't have access to on the outside.
</div>


<div>
$500 is more that I can handle. &nbsp;What is the minimum I can restore on my 2003 server to get it back as a dc? &nbsp;I already have the data on the new server.
</div>


<div>
Got another question for you. &nbsp;Th 2003 exchange server (not a dc). If I am unable to get the DC back and have to recreate from scratch, will I be able to get the exchange server to move to the new domain? If not is there a way to get the mail off of it?
</div>


<div>
Try enter the server with active directory restore mode using local administrator<br />
Hen rename it bk
</div>


<div>
I doubt you're going to be able to access the Exchange server until you get the DC issue fixed.<br />
<br />
Exchange relies very heavily on AD and if that isn't there, then Exchange isn't going to work.
</div>


<div>
That does not work because there are no other DCs available.
</div>


<div>
In regards to exchange, I was planning on upgrading to latest version of exchange anyway. &nbsp;Will I be able to import the clients outlook pst/ost files to get their emails into their new accounts if I install from scratch? I think I am just about resigned to a new domain install at this point.
</div>


<div>
Yes, you will be able to import .PST files. &nbsp;OST is just a copy of the mailbox that is on the server for offline access, you don't import them.<br />
<br />
In addition, there is no direct upgrade path from Exchange 2003 to Exchange 2013/2016 (2016 released about 2 months ago). &nbsp;If you try to install either of these in an environment and they detect Exchange 2003, the installation will halt. &nbsp;You would have to upgrade to 2010 then the latest version.<br />
<br />
You might be better off installing a new domain. That way you will know it's solid and stable from the get go.
</div>


<div>
<div class="content wysiwyg-content">
I was renaming our Windows 2012 DC the wrong way. &nbsp;I did not us netdom. Now DC cannot be found. &nbsp;I just renamed the computer. &nbsp;Can anyone help me fix this? I already demoted the second DC so I could upgrade it to 2012. Will changing the computer name back help or just make things worse? (if that's even possible).
</div>
</div>


I was renaming our Windows 2012 DC the wrong way.  I did not us netdom. Now DC cannot be found.  I just renamed the computer.  Can anyone help me fix this? I already demoted the second DC so I could upgrade it to 2012. Will changing the computer name back help or just make things worse? (if that's even possible).

Windows 2012 DC not found.

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

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.