Re: Time Synchronisation - Windows XP - 2003 Domain

Is the Windows Time service running on those client machines ??
As Lanwench indicated, you should not need to do any of this in
a healthy AD where clients will automatically be sync'ing with their
domain's PDC emulator FSMO which itself will be sync'ing with
the PDC FSMO of the forestroot domain.

That is all pre-plumbed.

That you need to be tweaking about indicates problems.
If it is not that the clients' Windows Time services is not running
then I would advise removing the policies you have implemented
and instead investigating what is wrong with the AD infrastructure.

Roger

"Chris W" <ChrisW@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F314FBDC-0E33-4277-AD72-1BC1565CE99F@xxxxxxxxxxxxxxxx
If we do it on the workstation it points to our domain controller, if we
run
it on the domain controller then it points to time.windows.com but surely
this bit does not matter as the time on the server is correct we just want
the workstations to sync with it. The time service is started on the
server.
"Lanwench [MVP - Exchange]" wrote:

In news:EB6D85CF-2477-4A9F-8327-7C27529820C9@xxxxxxxxxxxxx,
Chris W <Chris W@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Hi,

We are trying to use Group Policy to Synchronise the time on all the
workstations in the domain. The workstations are Windows XP and the
Server is 2003 STD.

Users do not have access to change the system time which is why we are
trying to synchronise with group policy. We have set the group policy
to use the domain controller as the time server but the workstations
are not synchronising.

Any Ideas?

Chris W.

This should be happening automatically - if you type

net time /querysntp

in a command prompt on the client, what do you see?

Is the Windows time service started on your server? What happens if you
type
the same thing on the server?

The users themselves do not need to do anything at all and you shouldn't
need to mess around with group policy settings for it, either. Got a
firewall or router between the clients & the server? (not the XP client
firewall).





.

Relevant Pages

  • Re: GPO error no appropriate rights
    ... Thank you for posting in the SBS newsgroup. ... Install the Windows Small Business Server 2003 Update for Windows XP ... go to Group Policy Management -> ... DomainName.local -> Small Business Server Client Computer ...
    (microsoft.public.windows.server.sbs)
  • Re: "Windows cannot access the file gpt.ini for GPO" - Events 1058 and 1030 on XP client o
    ... fails (client independent). ... I can open the gpt.ini file on both server via SYSVOL share with notepad. ... Remote Registry and TCP/IP NetBIOS Helper services aren't running but their ... failed to open the group policy object ...
    (microsoft.public.windows.group_policy)
  • RE: My documents synchronization. How to stop?
    ... a new domain on the full server2003, some of the old client machines still ... try to synchronize with the SBS server. ... 2.Restart the problematic client computer to take the group policy effect. ... 6.Make sure that folder redirection group policy have listed in applied ...
    (microsoft.public.windows.server.sbs)
  • Re: Client Synchronization errors after new install of server
    ... The clients will have to regenerate SID's, as the reloaded server is considered to be a different domain. ... The second error is with the Group Policy. ... The client workstations seems to still have some of the old policy. ... USERENV07:26:06:354 UnloadUserProfileP: Didn't unload user profile ...
    (microsoft.public.windows.server.sbs)
  • RE: GP in Terminal server
    ... If the client uses Windows XP, please run Regedit to change the permissions ... >correct DNS server address. ... >Resource Kit) to troubleshoot group policy issues. ...
    (microsoft.public.windows.group_policy)