Before you do this - you should really check out the following time article.
http://www.microsoft.com/resources/...2003/all/techref/en-us/W2K3TR_times_intro.asp
Making this change is not something to be taken lightly. Time sync is
important in the kerberos world of W2K3.
The registry setting you are looking for is as follows:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters
There should be an entry called Type (REG_SZ) with one of the following
values.
NoSync. The time service does not synchronize with other sources.
NTP. The time service synchronizes from the servers specified in the
NtpServer registry entry.
NT5DS. The time service synchronizes from the domain hierarchy.
AllSync. The time service uses all the available synchronization mechanisms.
The default value on domain members is NT5DS. The default value on
stand-alone clients and servers is NTP.
Change it to NoSync... should make your designated system no longer sync
with the time hierarchy in the forest. A word of caution - Kerberos relies
on accurate time sync for its tickets. By stopping this automated process,
you will be creating a system that will generate errors in your event logs
because of its inaccurate time.
Rick Claus [MSFT], MCSE
TechNet CDN - IT Pro Advisor
No Email Please... This alias is for newsgroup purposes only.
This posting is provided “AS IS†with no warranties and confers no rights.