Then I verified that the source time server for my old PDC was pointing to my new PDC with: I then proceeded to my previous PDC role holder and reconfigured it to fall back within the domain time hierarchy. W32tm /config /manualpeerlist:"0. 1. 2. 3." /syncfromflags:manual /reliable:yes /update On my new PDC role holder, I ran the following from an elevated command prompt:.ArticleĮdit 2: Should anyone somewhere across the interwebz ever need this, I was able to do this successfully by the following:
Will this automatically configure my new PDC holder as an NTP server and not NT5DS, or do I need to make the registry changes referenced within the Microsoft KB prior to doing any of this?Įdit: Found the following article which seems to explain this process clearly. W32tm /config /manualpeerlist: peers /syncfromflags:manual /reliable:yes /update One of my biggest questions, is that this command:
I have been able to find several articles such as the below, which include a previous Reddit post about this topic as well: While I understand the importance of the time sync within AD, my lack of knowledge comes from the configuration aspect.
Move pdc to new server update#
Since the PDC role was migrated, this obviously means I need to update the NTP settings to reflect the move. Last night I was able to successfully migrate the FSMO roles over to one of our new 2012 DC's. Finally wrapping up our AD migration from 2k8 to 2k12 DC's and I need a little advice on properly migrating the NTP service from the previous PDCe to the new one.