TITG
asked on
DC time and client sync time?
Not sure if my setup is good& For the clients to sync time with the domain controller I have the below line included I the logon script
REM Sync workstation time to domain controller...
net time \\dc1 /set /y
Also how do I check where is the domain controller(s) is getting the time from?
REM Sync workstation time to domain controller...
net time \\dc1 /set /y
Also how do I check where is the domain controller(s) is getting the time from?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No GPO and no manual intervention (except for the PDCe) is usually necessary; Kerberos requires that the time difference between DC and clients is (reasonably) small.
Add the ,0x8 after the IP address, it tells the time service to run in client mode when querying the ntp server.
You only need to run this on the PDC emulator.
Add the ,0x8 after the IP address, it tells the time service to run in client mode when querying the ntp server.
You only need to run this on the PDC emulator.
Along with the advice above, We also leave that net time /set command in our logon scripts for one reason... Laptops that sit on shelves for 6 months that have dead BIOS batteries. The time is reset and it too far our of whack to correct using w32time. The net time in the logon script gets them going again.
ASKER
Ran command below didn't sync?
C:\>w32tm /resync
Sending resync command to local computer...
The computer did not resync because no time data was available.
C:\>w32tm /resync
Sending resync command to local computer...
The computer did not resync because no time data was available.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Used this instead...and it worked
w32tm /config /update /manualpeerlist:129.6.15.2 8,0x8 /syncfromflags:MANUAL
w32tm /resync
w32tm /config /update /manualpeerlist:129.6.15.2
w32tm /resync
ASKER
PDC checked event ID no error
Then you should be set. Note that an occasional failure of a time sync can happen--ntp is using UDP, after all. As long as there are successful time syncs, you can ignore the errors.
ASKER
I will put the line below in a DC. The clients will sync automatically no GPO for that?
w32tm /config /update /manualpeerlist:208.184.49
w32tm /resync
I have two more DCs do I run the line in them to?