Windows 2012 non-PDC DC forcibly resets NTP

Yesterday the company's San Controller was hung up, directly resulting in dozens of virtual machine machines. Manager toss to midnight, finally replaced the new controller, re-mount Lun, and then seemingly return to normal, then pleasantly home.

This morning the beans to the company, the first problem is that Exchange Outlook users cannot log in! After a closer look, we found that 4, 5 DC NTP points to a DC in Brisbane, and that time is 5 minutes faster! What's going on here?

Normally, all DCs should be synchronized from the DC with the PDC role, and the client then synchronizes the time from the respective login DC. As a result of yesterday's drop-off at Melbourne site, the other city's DC invariably pointed the NTP source to the Brisbane DC. Then Brisbane the DC, it is exaggerated to point to the NTP itself, time is completely wrong ~ ~

How to fix this problem, very simple. On these non-PDC DCs, execute the following command.

First change to default settings

net stop W32Time

W32tm/unregister

W32tm/register

net start W32Time

Then look for the PDC within the domain to synchronize

W32tm/config/syncfromflags:domhier/update

net stop W32Time

net start W32Time

If this is not the case, you can force the resynchronization again by executing the following command

net stop W32Time && net start W32Time

W32tm/resync/rediscover

W32tm/config/update

Finally, you can view the status with W32tm/query/status.

This article is from the "Mapo Tofu" blog, please be sure to keep this source http://beanxyz.blog.51cto.com/5570417/1547821

Windows 2012 non-PDC DC forcibly resets NTP