RE: Time service on domain client
- From: Steve Goddard <SteveGoddard@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 2 Feb 2008 00:56:00 -0800
In brief run w32tm /resync to force the client to resychronize its clock. You
could then drop the same command into a batch file and remote execute it
using psexec or use it in a group policy login script. I wouldn't bother as
clients will eventually update their time on their next polling period.
As for the reg keys and a lot of detail on how the service works you can
find out it all here;
http://technet2.microsoft.com/WindowsServer/en/library/71e76587-28f4-4272-a3d7-7f44ca50c0181033.mspx?mfr=true
Basically as I understand the service, it checks for updates several times
in a short period and if there aren't any errors it extends and randomizes
the period it checks for resync;s.
--
Steve G.
MCSA 2003 +M
"Fahad" wrote:
Dear;.
I synchronized my PDC with external H/W clock and it's successful. I noticed
some client (windows XP) didn't sync successfully.
How Can I force all client to sync with the PDC?
also what si the update interval that the client use to sync with PDC? I'm
confused when i check the registry on my client i found the following values:
under HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config
MaxPollInterval = 15
UpdateInterval = 30000
under HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProvider\NtpClient
SpecialPollInterval = 3600
which one of these valuse will be used by the client to sync with the PDC?
- Prev by Date: Re: suggeston on how to make migrations easier
- Next by Date: Re: Backup Active Directory
- Previous by thread: Re: Logon Restrictions
- Next by thread: Re: Backup Active Directory
- Index(es):
Relevant Pages
|
