<div>
<div class="content wysiwyg-content">
Hi guys<br />
<br />
I have assigned the PDC Emulator role to a new DC. I have then configured the NTP external source on such new PDCE server.<br />
I now noticed that I did not change this setting on the other DC (Windows Server 2003) , which is still a DC but no longer a FSMO role holder.<br />
<br />
What's the best practice here ? Should I avoid that the former PDCE uses the external NTP time source ? I believe it should get the time from the new PDCE, right ? Any problems in leaving this DC it as is ?<br />
<br />
Thanks.
</div>
</div>


Hi guys

I have assigned the PDC Emulator role to a new DC. I have then configured the NTP external source on such new PDCE server.
I now noticed that I did not change this setting on the other DC (Windows Server 2003) , which is still a DC but no longer a FSMO role holder.

What's the best practice here ? Should I avoid that the former PDCE uses the external NTP time source ? I believe it should get the time from the new PDCE, right ? Any problems in leaving this DC it as is ?

Thanks.

NTP Source for previous PDC Emulator DC server

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.