<div>
Thanks for the response. &nbsp;I read through the link you gave me and I am pretty sure I will have to demote the DC (which will fail) then use metadata cleanup to remove any reference of the PDC from it, remove it from the domain and then rejoin the domain and attempt another dcpromo. &nbsp;Does this sound right?<br />
<br />
I do have a question about using metadata cleanup - Am I supposed to run this on the DC AND the PDC or just one of them. &nbsp;I assume the DC but I can't seem to wrap my mind around that.
</div>


Thanks for the response.  I read through the link you gave me and I am pretty sure I will have to demote the DC (which will fail) then use metadata cleanup to remove any reference of the PDC from it, remove it from the domain and then rejoin the domain and attempt another dcpromo.  Does this sound right?

I do have a question about using metadata cleanup - Am I supposed to run this on the DC AND the PDC or just one of them.  I assume the DC but I can't seem to wrap my mind around that.

<div>
I ended up reloading the OS and starting over.
</div>


I ended up reloading the OS and starting over.

<div>
<div class="content wysiwyg-content">
I have a DC that will not replicate from the PDC and found that the DNS Alias in the NTDS Settings Properties under AD Sites and Services is incorrect. &nbsp;This box is greyed out so I can not change it. &nbsp;I assume there is some way to refresh this value or remove and re-enter the correct one. &nbsp;<br />
<br />
This happened when the original PDC failed and had to be reloaded.<br />
<br />
Thanks in advance for you help!<br />
Craig
</div>
</div>


I have a DC that will not replicate from the PDC and found that the DNS Alias in the NTDS Settings Properties under AD Sites and Services is incorrect.  This box is greyed out so I can not change it.  I assume there is some way to refresh this value or remove and re-enter the correct one.  

This happened when the original PDC failed and had to be reloaded.

Thanks in advance for you help!
Craig

NTDS Settings Properties has wrong DNS Alias

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.