solved: Windows Client in domain does not sync time correctly , shows „local cmos clock“ as source

The problem: In an increasing amount of cases windows-clients (in domain environents) are failing to sync the current time. The system settings show „settings are managed by your organization“  and list „Local CMOS Clock“ as source.

Here’s a quick fix, forcing windows to use other ntp-Servers.

1. launch the command line (windows prompt) per right-mouselick -> as adminstrator
2. type the following command
   Schema:
   w32tm /config /manualpeerlist:“nptserver1 ntpserver2 ntserver3“ /syncfromflags:manual /update
   whereas nptserver1 ntpserver2 ntpserver3 are – blank delimited – are a list of hostnames / ip-adreses of ntp-servers you want to use.If your router / gateway is running a ntp-server, you can use it’s ip-adress as one of these values. Here’s is an example, using two ntp-servers.
   w32tm /config /manualpeerlist:“192.168.178.1  0.de.pool.ntp.org“ /syncfromflags:manual /update
3. now restart the computer; date and time should be set automatically after 5 to 30 minutes (just be patient and wait)

Hat Ihnen dieser Beitrag gefallen oder geholfen?
Bedanken Sie sich? Mit einer kleinen Anerkennung für die inhaltliche Arbeit?
Jeder Betrag ist willkommen. Lieben Dank!