Discussion:
Problems setting TIME on DC
(too old to reply)
GeirOtto
2009-11-24 11:46:57 UTC
Permalink
Hi, I just wonder if there is some of you that could help me with this
problem:

I have a DC (AD) that I want to use for synchronizing the time for all the
other servers.

I uses this command on that machine:
w32tm /config /manualpeerlist:fartein.ifi.uio.no /syncfromflags:manual
/reliable:yes /update

after that I do a net stop w32time && net start w32time

But nothing happens with the time either for the AD nor the servers. I know
the other servers synch against the AD, but I am not able to sync the DC
(AD).

I get this message in the eventlog:

Warning
Source:W32Time
Category:none
Eventid: 12

Time Provider NtpClient: This machine is configured to use the domain
hierarchy to determine its time source, but it is the PDC emulator for the
domain at the root of the forest, so there is no machine above it in the
domain hierarchy to use as a time source. It is recommended that you either
configure a reliable time service in the root domain, or manually configure
the PDC to synchronize with an external time source. Otherwise, this
machine will function as the authoritative time source in the domain
hierarchy. If an external time source is not configured or used for this
computer, you may choose to disable the NtpClient.

Geir Otto
GeirOtto
2009-11-24 15:46:50 UTC
Permalink
Fixed. It was due to vmWare time sync. vmWare was set up to sync against DC
(AD) and visa versa.... me bad :-)

Geir Otto
Post by GeirOtto
Hi, I just wonder if there is some of you that could help me with this
I have a DC (AD) that I want to use for synchronizing the time for all the
other servers.
w32tm /config /manualpeerlist:fartein.ifi.uio.no /syncfromflags:manual
/reliable:yes /update
after that I do a net stop w32time && net start w32time
But nothing happens with the time either for the AD nor the servers. I
know the other servers synch against the AD, but I am not able to sync the
DC (AD).
Warning
Source:W32Time
Category:none
Eventid: 12
Time Provider NtpClient: This machine is configured to use the domain
hierarchy to determine its time source, but it is the PDC emulator for the
domain at the root of the forest, so there is no machine above it in the
domain hierarchy to use as a time source. It is recommended that you
either configure a reliable time service in the root domain, or manually
configure the PDC to synchronize with an external time source. Otherwise,
this machine will function as the authoritative time source in the domain
hierarchy. If an external time source is not configured or used for this
computer, you may choose to disable the NtpClient.
Geir Otto
Loading...