Why is the time on my Server 2008 R2 DC wrong? It's syncing to ntp.org, it claims

CRUMMY ANSWER, I will switch the answer to a better one when a better one shows up. This is what I did for now.

I still have no idea why the group policy didn't work, but I "fixed" it by disabling the group policy that told it to enable and configure the NTP client (NTP server part is still on).

This broke the w32tm service on the server. W32tm simply returned some permission message, and "net start w32time" said something about the service being queued to be removed.

I had to reboot the server, run w32tm /register, reboot the server again, and then the server began using its own internal clock, which is more accurate than randomly skewing the NTP time forward by 10+ minutes in three days.

I will try the command line version of w32tm syncing from NTP at some future date, but I shouldn't have to do that - that's the entire point of group policy, no? I wanted to just be able to replace this DC with another one and have the NTP server set itself up.

I'm wondering if Microsoft's Group Policy templates are broken for the NTP client.