Windows 2008 R2 w32time configuration Clients off by two minutes

So, I spent a great deal of time getting my AD servers to sync to the Internet but now that they are, all my servers are still off from the AD Servers and I don't understand it.

On the AD Servers I configured them as such:

w32tm /config /manualpeerlist:"",0x8 /syncfromflags:MANUAL /reliable:YES /update

after restarting they sync just fine and I'm good to go.

On the member Servers in the domain I first did this:

w32tm /config /syncfromflags:DOMHIER /update

That didn't seem to do anything so I changed it to this below with the ips of the domain controllers:

w32tm /config /manualpeerlist:"",0x8 /syncfromflags:MANUAL /update

Well, at that point the clock shifted it's time. But it did so about 1:45 seconds different from the AD servers. previously it was almost four minutes. So it did update, but it did so within 2 minutes instead of exact. I don't understand it!

I can't seem to figure out. I did a test on the server and this is the result:

w32tm /stripchart /computer: /dataonly
Tracking [].
The current time is 3/12/2012 6:03:45 PM.
18:03:45, +155.9530574s
18:03:47, +155.9499391s

Why is it off by so much?

Oh, and I made sure I had no Group Policy governing which servers to sync time with. I have that setup on my workstation OU and those computers are off by about 24 seconds.
cmaohioSenior Systems ManagerAsked:
Who is Participating?
Darius GhassemConnect With a Mentor Commented:
The command you ran on the member servers should have sync with the DC that holds the PDC emulator role.

Read this as well very good article to read to understand how time works.
Darius GhassemCommented:
Are they running as virtual machines?
cmaohioSenior Systems ManagerAuthor Commented:
No, not virtual machines.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

cmaohioSenior Systems ManagerAuthor Commented:
Is there a command to see the status of the sync? Like a verbose /resync command? Perhaps I can see what server it's really looking at and why it's off by two minutes.
Darius GhassemCommented:
w32tm /monitor
cmaohioSenior Systems ManagerAuthor Commented:
Doesn't that simply show me the domain controllers?

Well, interestingly enough, I posted this around 6pm and now at 7:15pm, I go back to the server to try some more and the time is within 1 second. Now after going to the site you suggested (the Microsoft one) and telling it to "fix it for me" the time is within 0.86 seconds.

Good enough for me.

Is it possible the server simply needs a long time to come into sync? I have never seen this before but it seems that this is what it did.
Darius GhassemCommented:
Oh yeah it can take a bit for the clients to get fully sync with the DCs they don't want to change that much of the time at once so, if I remember right they take it down a little at a time.
Darius GhassemCommented:
When more command to run if you changed some settings

w32tm /resync /rediscover
cmaohioSenior Systems ManagerAuthor Commented:
Yeah, I was resyncing everytime.

That is it. I just ran the /stripchart.... Function on one of my servers that is off by 200+ seconds and as it ticks away I see it dropping by a few seconds with every check.

I have never seen a server do that before.
All Courses

From novice to tech pro — start learning today.