B
BambuPH
Guest
In our environment we have 5 DC's (1 PDC - Windows Server 2012, 1 DC - Windows Server 2012, 1 DC - Windows Server 2008R2, 2 DCs - Windows Server 2012R2) and ~200 Clients (Win 7, Win 8, Win 10). The PDC and one DC in our headquarter are virtualized (VMWare). The other DCs are in our branch offices. The domain-functional-level and the forest-functional level is Server 2008R2.
Because of some time-service-entries in Eventlogs I checked the time-status of our PDC. Unfortunately it shows Local CMOS Clock or Free-running System Clock. That is definitely a new problem. I don't know since when this problem exists. This has always worked and was configured correctly.
Normally the PDC sync his time with an external NTP-Server (three entries for redundancy) and the other DCs sync their time with the PDC. On all DCs or clients the time-source is the PDC or one DC. There seems to be no problem. The configuration is AD-Integrated (NT5DS). Our second DC shows the Type NT5DS in the registry and NtpServer "time.windows.com, 0x9".
Unfortunately it is not possible to change the NTP-Server on the PDC. If I run the command (w32tm /config /manualpeerlist:"NTP-Server1, NTP-Server2, NTP-Server3" /syncfromflags:manual /reliable:yes /update), the command completed successfully. The registry (HKLM\System\CurrentControlSet\Services\w32tm) shows at NTP-Server the three NTP-Server-Entries, the TYPE is NTP and the AnnounceFlags is 5.
But after that command, the source is again Local CMOS Clock or Free-running System Clock.
How can I configure the PDC to use external NTP-Server again? Don't know what happened. I didn't find a misconfiguration.
Have anybody out there a solution for my problem or an idea?
Continue reading...
Because of some time-service-entries in Eventlogs I checked the time-status of our PDC. Unfortunately it shows Local CMOS Clock or Free-running System Clock. That is definitely a new problem. I don't know since when this problem exists. This has always worked and was configured correctly.
Normally the PDC sync his time with an external NTP-Server (three entries for redundancy) and the other DCs sync their time with the PDC. On all DCs or clients the time-source is the PDC or one DC. There seems to be no problem. The configuration is AD-Integrated (NT5DS). Our second DC shows the Type NT5DS in the registry and NtpServer "time.windows.com, 0x9".
Unfortunately it is not possible to change the NTP-Server on the PDC. If I run the command (w32tm /config /manualpeerlist:"NTP-Server1, NTP-Server2, NTP-Server3" /syncfromflags:manual /reliable:yes /update), the command completed successfully. The registry (HKLM\System\CurrentControlSet\Services\w32tm) shows at NTP-Server the three NTP-Server-Entries, the TYPE is NTP and the AnnounceFlags is 5.
But after that command, the source is again Local CMOS Clock or Free-running System Clock.
How can I configure the PDC to use external NTP-Server again? Don't know what happened. I didn't find a misconfiguration.
Have anybody out there a solution for my problem or an idea?
Continue reading...