M
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMNMMMMMMM
I am having a problem with time-drift running virtual domain controllers on a forest with child domains. I want to configure my root PDC in the following way:
To accomplish this, I ran the following commands on my forest root PDC:
When I run the "w32tm /resync /rediscover" command I get "The computer did not resync because no time data was available". We have the NetApp's and other Cisco devices pulling time from 192.168.0.10, but the forest root PDC can't seem to pull the time from it. I'm hoping you folks have some thoughts as to why. Thanks in advance and have a great day.
Continue reading...
- Sync my root PDC time with a bare metal device, right now we are wanting to use a Cisco router for this function.
- Allow my domain-joined servers/workstations to sync time with the root PDC.
- Allow my child domain DCs to sync time with the root PDC.
- Allow my child domain servers/workstations to sync time with the PDC in their respective domains.
To accomplish this, I ran the following commands on my forest root PDC:
- W32tm /config "/manualpeerlist:192.168.0.10" /syncfromflags:manual /reliable:yes /update --- (192.168.0.10 is the IP address of the Cisco router)
- w32tm /resync /rediscover
When I run the "w32tm /resync /rediscover" command I get "The computer did not resync because no time data was available". We have the NetApp's and other Cisco devices pulling time from 192.168.0.10, but the forest root PDC can't seem to pull the time from it. I'm hoping you folks have some thoughts as to why. Thanks in advance and have a great day.
Continue reading...