js0873x
asked on
Syncing Time on Server 2012 R2
My server, running Hyper-V (it that matters) is off on its time but about 45 seconds. I decided to try to set the host to get its time from external time servers, and I followed the following under Manually Configure the Windows Time service:
https://support.microsoft. com/en-us/ help/81604 2/how-to-c onfigure-a n-authorit ative-time -server-in -windows-s erver
When I did everything there in the registry as recommended I can’t get the Windows time service to start. It’ll remain in starting status after giving me the following error:
Windows could not start the Windows Time service on Local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion.
I used the following time servers:
0.pool.ntp.org,0x1 1.pool.ntp.org,0x1 2.pool.ntp.org,0x1 3.pool.ntp.org,0x1
Any idea what I might be doing wrong? How do I successfully get the time on my server, and subsequently the guests, to be accurate?
https://support.microsoft.
When I did everything there in the registry as recommended I can’t get the Windows time service to start. It’ll remain in starting status after giving me the following error:
Windows could not start the Windows Time service on Local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion.
I used the following time servers:
0.pool.ntp.org,0x1 1.pool.ntp.org,0x1 2.pool.ntp.org,0x1 3.pool.ntp.org,0x1
Any idea what I might be doing wrong? How do I successfully get the time on my server, and subsequently the guests, to be accurate?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You can try to debug w32tm
in cmd:
w32tm /debug /enable /file:C:\windows\temp\w32t ime.log
try to restart the service and watch the log
By the way: Did you turn off Time Sync in the Integration Services for VM? (that's not the core of your problem, but when you use own NTP this service must be disabled)
in cmd:
w32tm /debug /enable /file:C:\windows\temp\w32t
try to restart the service and watch the log
By the way: Did you turn off Time Sync in the Integration Services for VM? (that's not the core of your problem, but when you use own NTP this service must be disabled)
Windows Time is not designed to be an exact time.. 45 seconds off is well within the allowable difference. Windows Time is only used for kerberos time stamps which default to within 5 minutes to be determined as synchronous
https://technet.microsoft.com/en-us/library/cc976357.aspx
https://technet.microsoft.com/en-us/library/cc976357.aspx
If your HYPER-V host is an AD joined member server, it would take the time source as the PDC role holding server. If its a non-AD joined, then you can set it up the time source as an external source or from its local Cmos.
The error :- Windows could not start the Windows Time service on Local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion .
... is because the w32tm.dll would be unregistered (you may not see the "Windows Time" service on the server, are you?) and you may need to to re-register the time service by running "w32tm /register" command. If that fails, then you can try to re-register the "w32time.dll" (regsvr32 C:\Windows\System32\w32tim e.dll) and then run "net start w32time".
Once you set the NTP configuration correctly (to pick an external time source as NTP server) on your PDC role holding server, all the domain joined computers would pick the time automatically from the PDC.
If your NTP configuration having any issues- Run the commands to verify (w32tm /query /configuration and w32tm /query /status), please share the output and happy to assist.
Thanks,
The error :- Windows could not start the Windows Time service on Local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion .
... is because the w32tm.dll would be unregistered (you may not see the "Windows Time" service on the server, are you?) and you may need to to re-register the time service by running "w32tm /register" command. If that fails, then you can try to re-register the "w32time.dll" (regsvr32 C:\Windows\System32\w32tim
Once you set the NTP configuration correctly (to pick an external time source as NTP server) on your PDC role holding server, all the domain joined computers would pick the time automatically from the PDC.
If your NTP configuration having any issues- Run the commands to verify (w32tm /query /configuration and w32tm /query /status), please share the output and happy to assist.
Thanks,
ASKER
Here's our setup, right or wrong, and most likely wrong. Our main domain controller is the PDC role holding server, and it's a Hyper-V guest machine. It has time synchronization turned on in the host's Integration Services for that guest, as do all of the other guest servers. What do you think is best at this point?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I have recommended this question be closed as follows:
Split:
-- Abhi Pappi (https:#a42402420)
-- yo_bee (https:#a42398551)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
Pber
Experts-Exchange Cleanup Volunteer
I have recommended this question be closed as follows:
Split:
-- Abhi Pappi (https:#a42402420)
-- yo_bee (https:#a42398551)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
Pber
Experts-Exchange Cleanup Volunteer
ASKER