Wrong time on client PCs

[edsa]

Hi

Our network client pcs are displaying the wrong time. I was wondering if there was a way in which the PCs could take their system time from the server on which the time is correct.

 

If not is there any other way that I could keep their time correct?

 

cheers

 

Ed

[mattx]

Hi

Our network client pcs are displaying the wrong time. I was wondering if there was a way in which the PCs could take their system time from the server on which the time is correct.

 

If not is there any other way that I could keep their time correct?

 

cheers

 

Ed

 

Use the net time command in your logon script.....

 

NET TIME
[\\computername | /DOMAIN[:domainname] | /RTSDOMAIN[:domainname]] [/sET]
        [\\computername] /QUERYSNTP
        [\\computername] /SETSNTP[:ntp server list]

[laserblazer]

I've put a NET TIME command into the logon script and that seems to work ok, even with W98 machines.

[ICT_GUY]

Set up a time server on the network.

 

http://support.microsoft.com/kb/816042

 

And set the correct server for your client PCs in your AD.

[DMcCoy]

Or you could just use the sensible option. the Windows Time options in group policy. You really need your DC to sync with an authoritative time source though, otherwise it doesn't like to give the time to other clients.

[cookie_monster]

What client OS are you using?

 

The PDCe (usually the first DC installed) should be your authorative time server and should keep all of your 2k + clients in sync. If they aren't keeping time then i would suggest checking for DNS issues.

[Michael]

Just place

 

net time \\SERVERNAME /set /yes

 

into a logon script. Just make sure the server time is correct

[srochford]

The net time command is good for Windows 98 and earlier clients but won't work in a login script for Windows NT and later unless you give users rights to change the system time (they don't have that right by default).

 

Just for info, "net time" is deprecated - it's replaced by w32tm and the equivalent to sync time is "w32tm /resync" - if this works and time was out of sync then you'll get a message in the system event log (doesn't log if there was no problem)

[DMcCoy]

In Group Policy Editor change your Default Domain Policy to give the group Authenticated Users the right to Change the System Time (Computer Configuration / Windows Settings / Security Settings / Local Policies / User Rights).

 

But if you are going to go into group policy why not use the time options that are there so that it stays in sync even when no one eve logs in to it?

[mattx]

In Group Policy Editor change your Default Domain Policy to give the group Authenticated Users the right to Change the System Time (Computer Configuration / Windows Settings / Security Settings / Local Policies / User Rights).

 

Your happy to edit your Default Domain Policy ? Its not a pratice I would suggest !!

[cookie_monster]

Your 2k or above PC's DO NOT need bat files to keep time if you're using Active Directory if they aren't keeping time then something is wrong, you are not required to give users the right to change the system time.

 

Configuring the Windows Time Service

 

http://www.windowsnetworking.com/articles_tutorials/Configuring-Windows-Time-Service.html

 

How Windows Time Service Works

 

http://technet2.microsoft.com/windowsserver/en/library/71e76587-28f4-4272-a3d7-7f44ca50c0181033.mspx?mfr=true

Edited March 4, 2008 by cookie_monster

[Geoff]

Also check the timezone settings on the machines. The time might be right, just the machine is set to PST or something.