[jrexa]

anneb2, on Sep 15 2009, 08:26 PM, said:

All the above solutions still did not work for me. The policies were all set to "not configured". I tried to set them to "disabled", rebooted the machine, reset them to "not configured", rebooted, but to no avail.

Finally I found that policies get stored in the registry as well.

After renaming the following keys in :
\HKEY_LOCAL_MACHINE\SOFTWARE\POLICIES\MICROSOFT\W32TIME\

CONFIG to _CONFIG
PARAMETERS to _PARAMETERS
TIMEPROVIDERS to _TIMEPROVIDERS

and restarting w32time,

at last w32tm started reading the normal - documented - registry settings and this solved the problem for me as well.

( 8 hours wasted thanks to policy settings that do not appear in the policy editor or did I look in the wrong place?)

This was EXACTLY my problem. I have used a couple of days to solve this problem.

My PDC Emulator is running 2003 x64
I ran the "Group Policy Results Wizard" on our x86 DC and found out, that the settings came from the "Local Group Policy"

On the "Group Policy Challenged DC" I then ran MMC
Add/Remove Snapin
Select "Group Policy Object Editor"
Select "Local Computer" as the "Group Policy Object" (This is the default value)

Go to "Local Computer Policy", "Computer Configuration", "Administrative Templates", "System", "Windows Time Service"
Make sure that the settings are "not configured", also under "Time Providers"

My settings was configured under "Time Providers" and after setting to "Not Configured" the settings imidiately dissapeared from the Registry key in the Quote, and did NOT come back.

This post has been edited by jrexa: 19 January 2010 - 09:46 AM

[erobinson]

I know this is an older thread, but you guys are amazing. This problem has been driving me crazy for weeks.

Sure enough it was because of some group policy settings.

Thanks! You guys are lifesavers!

This post has been edited by erobinson: 15 April 2010 - 09:11 AM

[erobinson]

Thank you all for your time!

I just cant say thanks enough!

This post has been edited by erobinson: 15 April 2010 - 09:12 AM

[ZaidSenall]

anneb2, on 15 September 2009 - 05:26 PM, said:

All the above solutions still did not work for me. The policies were all set to "not configured". I tried to set them to "disabled", rebooted the machine, reset them to "not configured", rebooted, but to no avail.

Finally I found that policies get stored in the registry as well.

After renaming the following keys in :
\HKEY_LOCAL_MACHINE\SOFTWARE\POLICIES\MICROSOFT\W32TIME\

CONFIG to _CONFIG
PARAMETERS to _PARAMETERS
TIMEPROVIDERS to _TIMEPROVIDERS

and restarting w32time,

at last w32tm started reading the normal - documented - registry settings and this solved the problem for me as well.

( 8 hours wasted thanks to policy settings that do not appear in the policy editor or did I look in the wrong place?)

GENIUS! PURE GENIUS!

I have had this problem for god knows how long! none of the replied to none of the other forums helped just like the fist post, but this one, this was the answer to all my problems!

I had to update group policy on all my machines and resync them to the DC after I was finally able to sync the DC with the external time source, but now all my machines are running on time!!!

Thank you so much, anneb2!!!

[m1a9r8k3]

It works!!

GP was the problem.. like many others i had tried for for too long to get this right.. rechecked all setting and configurations.. nothing worked until I tried to disable the time service in Group Policies that aparently affected even our DC..

Thanks a lot!!

[pstraight]

I've been having this same issue and hope it is related to the GPO settings like everyone else is saying. I am administering a Windows 2003 32bit SP2 machine. I only got hired a week ago and aparently the clocks here have always been about 12 minutes ahead of the real time.

Anyway, the network administrators before me set the default domain policy to configure the "Configure the Windows NTP Client" and the "Enable WIndows NTP client" to be enabled. Obviously since our domain controllers were in the domain that this policy was being issued to, they are getting these settings as well. I went ahead and made an OU and put the domain controllers in there and enforced the "Default domain controllers policy" GPO so that should override any settings the default domain policy issues. Of course, the default domain controllers policy has all three of the time settings discussed here set as "not configured". I went ahead and did a gpupdate /force on the domain controller with the PDC fsmo role and then logged off and logged back on. The problem was that I was getting the same error. Is this something that I will have to restart the domain controller for all the settings of the enforced "default domain controllers policy" to take effect? I really don't want to restart this domain controller seeing as it is running DHCP and DNS.

Thanks