I found this KB artice: http://support.microsoft.com/kb/816042
But it involves a bunch of manual registry hacks. I was hoping to find something buried in Administrative Tools somewhere that allowed me to do this.
I'm using Windows Server 2003.
1
-
Yeah, that KB article is not very helpful, considering both the "w32time" and "net time" methods achieve the same goal.– David BullockJul 11, 2011 at 13:03
Add a comment
|
3 Answers
A Windows 2003 server which is a dc and has the pdc role will be set by default to syncronise it's time with time.microsoft.com. If you wish to use a different sntp time server you can issue this command at the command promt
net time /setsntp:FQDN
where FQDN is replaced by the time server name. It may take several minutes for this to take effect.
answered May 3, 2009 at 2:07
This needs to be done on the DC with the PDC emulator role
To configure the Windows Time service on the PDC emulator
Type the following command to configure the PDC emulator and then press ENTER:
w32tm /config /manualpeerlist:peers /syncfromflags:manual /reliable:yes /update
where peers specifies the list of DNS names and/or IP addresses of the NTP time source that the PDC emulator synchronizes from. For example, you can specify time.windows.com. When specifying multiple peers, use a space as the delimiter and enclose them in quotation marks.
-
After update you might want to restart the Windows Time service. In addition to that, you should configure Windows Time service against a large time offset. IMHO this is must. You can't possible fathom amount of problems you can have if suddenly time on all of your servers/workstations goes back/forwards by even a week. support.microsoft.com/kb/884776– KAPesJul 1, 2009 at 13:06
I would have thought configuring it via the normal method would work?
- Double click the clock
- Internet Time tab
- Enter the servers and hit update, I'm for example using 0.pool.uk.ntp.org which I've always assumed propagated to the domain clients.
answered May 3, 2009 at 1:38
