Workaround for out-of-date client time and server time in AD domain

Company attendance is an OA software in the domestic attendance module, the personal computer in the specified time in the form of registration, the client is to take the form of domain user login, the computer client time display than the time of OA registration two minutes later, [Note: The OA server installed time correction software Itimesync, Ensure that the OA server time is always consistent with the standard time], and then every time the computer client slow two minutes, we are two minutes late to work, over time we found that the computer is always with the phone time is two minutes slower is not happy,

Feedback to the information center, ask the information center to adjust the time for everyone, because the domain users can not modify the time, even if you modify the computer after restarting the time and the ad synchronization.

Computer time in the domain is inconsistent, it is a good technical problem for us, and the time is not synchronized with the client is not normal domain and Lync client cannot log on. Let me tell you about my solution.

Back to the point:

1, Domain control configuration

After Windows Server 2012 is domain controlled, the time setting in the Internet time is gone, in order to resolve this problem, the following CMD command can be resolved:

W32tm/config/manualpeerlist:time.windows.com/syncfromflags:manual/reliable:yes/update

or w32tm/config/manualpeerlist:time.nist.gov/syncfromflags:manual/reliable:yes/update

Because China is always unable to synchronize with time.windows.com time, it is recommended to take and National Service Center Server [Time.nist.gov]

Stay in sync. such as

650) this.width=650; "class=" AlignCenter "title=" time is out of sync. jpg "src=" http://img0.tuicool.com/rM3IRn.jpg "alt=" Rm3irn.jpg "/>650" this.width=650; "class=" AlignCenter "title=" time synchronization. jpg "src=" http://img0.tuicool.com/7ZniMr.jpg "alt=" 7znimr.jpg "/>

Open the registry and check that your settings are successful.

650) this.width=650; "class=" AlignCenter "title=" 123.jpg "src=" http://img2.tuicool.com/Q7beai.jpg "alt=" Q7beai.jpg " />

2. Set up Group Policy to start the NTP server

650) this.width=650; "class=" AlignCenter "title=" 123.jpg "src=" http://img2.tuicool.com/Yvyqii.jpg "alt=" Yvyqii.jpg " />

3. Set the Windows Time service to start automatically in the Domain policy

650) this.width=650; "class=" AlignCenter "title=" 123.jpg "src=" http://img2.tuicool.com/YvayMn.jpg "alt=" Yvaymn.jpg " />

4, the Client

Update Domain Policy Gpupdate/force

If not restarted, first net stop w32time, and then net start W32Time

5, if there are non-domain-joined servers in the enterprise [such as Lync Edge Server], we set as follows.

Date and time/internet time/Change settings, server select Time.nist.gov, tick sync with Internet time server, OK.

650) this.width=650; "title=" 123.jpg "src=" http://img1.tuicool.com/iYRna2.jpg "alt=" Iyrna2.jpg "/>

This article from the "IT" blog, reproduced please contact the author!

Workaround for out-of-date client time and server time in AD domain