Question : Group Policy Based Windows Time Synchronization Issues.

I am trying to get a windows domain to all play happily together as far as time synchroniation goes.  It isn't going well.

Here is what I have done so far:

Default Domain Policy --> Administrative Templates --> System --> Windows Time Service --> Time Providers.

Enabled Windows NTP Client and Configured Windows NTP client to use the following settings:

NtpServer: pool.ntp.org,0x1
Type: NT5DS
CrossSiteSyncFlags: 2
ResolvePeerBackoffMaxTimes: 7
SpecialPollInterval: 3600
EventLogFlags: 0

Seems simple enough.  Synch with the given time provider every 3600 seconds.  Does NOT work.

All PCs on the domain have identical time, including comain controllers.  But they are all almost 10 minutes fast.

Even entering the following command at a command prompt shows an offset of 568+ seconds.
w32tm /monitor /computers:pool.ntp.org

So, I am checking local PC time against the time server I have configured the network to use, and still get an offset of almost 10 minutes.

So, here is what I want to eventually accomplish:

1) Get Domain Controllers to synch CORRECTLY with an external NTP server (don't care which) through the default Domain Controllers Policy in the group policy editor.
2) Get all client PCs to synch from one of the Domain Controllers through the Default domain policy.  I have a simple single windows domain (vs-us.local) with only 13 clients.  This shouldn't be a big deal.
3) Avoid running manual sntp configuration from a command line on each individual PC.

What am I doing wrong, or better yet, where should I start over.  I have played with nearly every tutorial online to no avail.  I am looking for walkthrough steps from beginning to end at this point.

Thanks so much!

Answer : Group Policy Based Windows Time Synchronization Issues.

I was working with someone on EE on what sounds like an identical issue last week, and the fix ended up being this:

http://www.jsifaq.com/SF/Tips/Tip.aspx?id=11119