HYPER-V DC clock drifting and PDC sync with external source
two things in this rant
1/ HYPER-V VM (DC) clock drifting, integration services make VM sync time with the hyper-v host, but if the vm is a DC, this process will be going in a circle.
I temporirily used a method as
http://mikefrobbins.com/2010/05/17/active-directory-and-server-time-synchronization-problems-with-hyper-v/
basically tick off time sycn in intergration services
but other papers on the internet seemed against this approach?
anyway , some cmd quite useful
w32tm /query /status
w32tm /resync /rediscover
2/ I used w32tm cmd to sync with internet clock on the PDC
but the clock on the PDC still about 2 minutes apart, there is no error in the log
the problem is w32tm contacted the source, but the source may be too far away failed to respond,
choose a local time server, chose one you can reach easily ....
then in the log , it will say w32t getting valid data and the ip address port 123 etc
two things in this rant
1/ HYPER-V VM (DC) clock drifting, integration services make VM sync time with the hyper-v host, but if the vm is a DC, this process will be going in a circle.
I temporirily used a method as
http://mikefrobbins.com/2010/05/17/active-directory-and-server-time-synchronization-problems-with-hyper-v/
basically tick off time sycn in intergration services
but other papers on the internet seemed against this approach?
anyway , some cmd quite useful
w32tm /query /status
w32tm /resync /rediscover
2/ I used w32tm cmd to sync with internet clock on the PDC
but the clock on the PDC still about 2 minutes apart, there is no error in the log
the problem is w32tm contacted the source, but the source may be too far away failed to respond,
choose a local time server, chose one you can reach easily ....
then in the log , it will say w32t getting valid data and the ip address port 123 etc
No comments:
Post a Comment