Ive tried, followed guides but failed!! To simply set the clock!!!!

[burgemaster]

We have always used a .bat script to set the clock from one of the Domain Controllers.

Reading about this is apparently not recommended and was used in W2000

time.bat - "Set time \\dc1 /set /yes"

Can anyone please talk me through the correct way to set the clock with Group Policy.?

 

Thanks in advance !!

 

Latest failed effort:

System/Windows Time Service/Time Providers

Policy Setting

Configure Windows NTP Client Enabled

NtpServer DC1.{school}.local

Type NTP

CrossSiteSyncFlags 2

ResolvePeerBackoffMinutes 15

ResolvePeerBackoffMaxTimes 7

SpecialPollInterval 3600

EventLogFlags 0

Edited March 19, 2019 by ZeroHour

[sted]

the workstations should all pick up time from the pdc without any intervention

[box_l]

Not using Group policy, but

 

One of the schools I picked up recently had the server referencing itself and the clients working from micrsofts' time server.

 

To fix this I did the following.

 

On the FSMO role holder

 

w32tm /configure /manualpeerlist:your.ntp.time.server.here,0x1 /syncfromflags:MANUAL
net stop w32time
net start w32time
w32tm /resync

 

where your.ntp.time.server.here is the one provided by LEA/county or a trusted one from the web, pool.ntp.org etc

 

On the clients

 

W32tm /config /syncfromflags:domhier /update
net stop w32time
net start w32time
W32tm /resync /rediscover

 

Check clients with

w32tm /monitor

 

BoX

[sukh]

Hi

 

See this Windows Time Service and Internet Communication

 

Sukh

[chrisbrown]

time.bat should read "net time" and it will still work.

[chrisbrown]

Is it just me or was a post deleted from here?

[burgemaster]

Right...

I now have all desktops syncing perfectly to our PDC... I have also manually set the servers to correct their time.

Thanks for all the help!!