I might suggest using one of the USNO time sources as the most accurate. These are public NTP servers. http://www.usno.navy.mil/USNO/time/ntp You should only do this on your PDCe, and allow all other DCs/clients to maintain synchronization as normal. Check in rsop.msc: computer configuration|administrative templates|system|windows time service If there are GP settings reverting your source (which I agree, it does sound like), then the settings should appear in rsop and have the name of the effective group policy. Brandon Wilson - Premier Field Engineer (Platforms)

Hi, Please review the GPMC log to check if there is any Windows Time Server related enabled Group Policy causes the issue. 1. On domain controller, click Start -> Run, type GPMC.MSC, it will load the GPMC console. If the GPMC snap-in is not installed. 2. Right click on "Group Policy Result" and choose wizard to generate a report for the problematic computer and user account (please place appropriately). (Choose computer and select the proper user in the wizard) 3. Right click the resulting group policy result and click the "Save Report…" => save report and upload it to the link I provided. Please also refer to the following Microsoft KB article to modify the registries and configure the Windows Server as an authoritative time server: How to configure an authoritative time server in Windows Server http://support.microsoft.com/kb/816042 Regards, Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I have DC1 server on 2003 and it is my NTP server. I want to chnage my NTP Server to point time.windows.com I have done following commands tasks but it reverts back to old value SNTP = OLD DC1 . I ran the following commands to point to external time source: w32tm /config /manualpeerlist:time.windows.com,0x1 /syncfromflags:manual /update net stop w32time net start w32time OR : net time /setsntp:time.windows.com Stop/Start the services. But it still goes back to old NTP Value = OLD DC1 Server once I REBOOT. I double checked the Group Policy but I can't find which is forcing Server to revert the settting once I reboot/logg off.

I might suggest using one of the USNO time sources as the most accurate. These are public NTP servers. http://www.usno.navy.mil/USNO/time/ntp You should only do this on your PDCe, and allow all other DCs/clients to maintain synchronization as normal. Check in rsop.msc: computer configuration|administrative templates|system|windows time service If there are GP settings reverting your source (which I agree, it does sound like), then the settings should appear in rsop and have the name of the effective group policy. Brandon Wilson - Premier Field Engineer (Platforms)

Hi, Please review the GPMC log to check if there is any Windows Time Server related enabled Group Policy causes the issue. 1. On domain controller, click Start -> Run, type GPMC.MSC, it will load the GPMC console. If the GPMC snap-in is not installed. 2. Right click on "Group Policy Result" and choose wizard to generate a report for the problematic computer and user account (please place appropriately). (Choose computer and select the proper user in the wizard) 3. Right click the resulting group policy result and click the "Save Report…" => save report and upload it to the link I provided. Please also refer to the following Microsoft KB article to modify the registries and configure the Windows Server as an authoritative time server: How to configure an authoritative time server in Windows Server http://support.microsoft.com/kb/816042 Regards, Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.