J
jamicon
hello,
we have 60 Domain Controllers, all 2016, all in perfect time sync. 2016 functionality.
I recently found that one of my 2016 DHCP servers was off time by 86 seconds, this cause the hot standby to fail.
The first thing I did was check the local DC time and successfully sync'd with the Domain PDC...
So then I went back to the DHCP server and ran the command to sync domain time, failed.
Its then that I noticed I can not start the Windows Time Services on ANY of my 60 DHCP servers so then I started checking other servers and their Windows Time server won't start either.
Can you help?
Note: none of my DHCP servers is on a Domain Controller.
UPDATE - only seems to be affecting 2016 servers and nothing else.
Continue reading...
we have 60 Domain Controllers, all 2016, all in perfect time sync. 2016 functionality.
I recently found that one of my 2016 DHCP servers was off time by 86 seconds, this cause the hot standby to fail.
The first thing I did was check the local DC time and successfully sync'd with the Domain PDC...
So then I went back to the DHCP server and ran the command to sync domain time, failed.
Its then that I noticed I can not start the Windows Time Services on ANY of my 60 DHCP servers so then I started checking other servers and their Windows Time server won't start either.
Can you help?
Note: none of my DHCP servers is on a Domain Controller.
UPDATE - only seems to be affecting 2016 servers and nothing else.
Continue reading...