We have a few Sites but on the very small Sites we dont have an own DC.
On the most other sites, we have a DC and the Hyper-V Server is syncing it's Clock with the virtual DC running on itself (VMICTime disabled) and the DC correctly syncs its time with the PDC running on the Main-Site.
There are however 3 smaller Sites where we havnt seen an urge to install an local Site-DC. So these Hyper-V Servers only contain Standard-Domain-Member Servers.
THe Hyper-V itself also is an Domain-Member.
----
---
Problem:
The Hyper-V Server only uses (visible with w32tm /query /status) the "Local CMOS Clock" or "Free-running System Clock"
There is only ONE WAY to get him sync with the DC which is in a different subnet and that is with
# net stop w32time
# net time \\servername /set /y
# net start w32time
With that the Clock is "in Sync" with the PDC, but "w32tm /query /status" still gives "Local CMOS Clock"
Of Course, after a few minutes, the Clock is out of sync again because it does'nt keep synching
-
-
i Tried:
Enter Registry Keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time\Parameters
-> NTPServer (pdc.domain.local)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time\TimeProviders\VMICTimeProvider
-> Enable (0)
w32tm /config /computer:pdc.domain.local /syncfromflags:DOMHIER
w32tm /resync
Gives Error: "No timedata available" which is understandable because "w32tm /query /status" shows it's still using the Local CMOS Clock/Free-running System Clock.
w32tm /stripchart /computer:zwiendc /samples:1000 /dataonly
Shows me the correct, actual difference between the HyperV and the PDC (so the NTP connection IS working, nothing blocked by any Firewall)
iam a little out of Ideas here.