Discussion:
PDC time services how to resynch?
(too old to reply)
DoleBludger
2009-12-16 15:48:01 UTC
Permalink
After successfull comands on my PDC Window server 2003:

w32tm /config /syncfromflags:manual /manualpeerlist:time.windows.com
/reliable:yes
w32tm /config /update
w32tm /stripchart /computer:time.windows.co
m /samples:10 /dataonly
Tracking time.windows.com [207.46.232.182].
Collecting 10 samples.
The current time is 12/16/2009 1:44:11 PM (local time).
13:44:11, error: 0x800705B4
13:44:14, -92.9414991s
13:44:16, -92.9493396s
13:44:18, -92.9585717s
13:44:20, error: 0x800705B4
13:44:23, -92.9586381s
13:44:26, -92.9430413s
13:44:28, -92.9430693s
13:44:30, error: 0x800705B4
13:44:33, -92.9509480s
net time /querysntp
The current SNTP value is: time.windows.com
I do not know what I have to do to get less error, than 92 sec?
Florian Frommherz [MVP]
2009-12-16 17:36:35 UTC
Permalink
Howdie!
Post by DoleBludger
w32tm /stripchart /computer:time.windows.co
m /samples:10 /dataonly
Tracking time.windows.com [207.46.232.182].
Collecting 10 samples.
The current time is 12/16/2009 1:44:11 PM (local time).
13:44:11, error: 0x800705B4
13:44:14, -92.9414991s
[...]
13:44:30, error: 0x800705B4
13:44:33, -92.9509480s
net time /querysntp
The current SNTP value is: time.windows.com
I do not know what I have to do to get less error, than 92 sec?
I would give it some time and watch it. As far as I know, the Windows
Time service doesn't actually change the time right away but tries to
slowly adjust to it. It probably won't change its clock to the accurate
time but will get nearer and nearer to the correct time.

Cheers,
Florian
--
Microsoft MVP - Group Policy
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.
ANY advice you get on the Newsgroups should be tested thoroughly in your
lab.
Ace Fekay [MCT]
2009-12-17 01:45:34 UTC
Permalink
Post by Florian Frommherz [MVP]
Howdie!
Post by DoleBludger
w32tm /stripchart /computer:time.windows.co
m /samples:10 /dataonly
Tracking time.windows.com [207.46.232.182].
Collecting 10 samples.
The current time is 12/16/2009 1:44:11 PM (local time).
13:44:11, error: 0x800705B4
13:44:14, -92.9414991s
[...]
13:44:30, error: 0x800705B4
13:44:33, -92.9509480s
net time /querysntp
The current SNTP value is: time.windows.com
I do not know what I have to do to get less error, than 92 sec?
I would give it some time and watch it. As far as I know, the Windows Time
service doesn't actually change the time right away but tries to slowly
adjust to it. It probably won't change its clock to the accurate time but
will get nearer and nearer to the correct time.
Cheers,
Florian
--
Microsoft MVP - Group Policy
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.
ANY advice you get on the Newsgroups should be tested thoroughly in your
lab.
Hi Florian,

I believe the poster, multi-posted this in another group, which I had
replied to (I can't remember which other group it was in). One thing that I
did point out in my response, is that the Windows time service is not as
accurate as one expects, and expect a 2-3 minute skew. Microsoft even says
this in two KB articles (listed in my blog). If something tighter is needed,
such as down to the second transaction logging, such as for a bank solution,
a third party time service solution will be required.

Configuring the Windows Time Service for Windows Server
http://msmvps.com/blogs/acefekay/archive/2009/09/18/configuring-the-windows-time-service-for-windows-server.aspx
--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.
Loading...