Another important note: in a domain where there are multiple domain controllers, this process should only be done on the PDC emulator for the entire forest.
Any other domain controllers should use the command "w32tm /config /syncfromflags:domhier /update" instead which will tell the DC to check with the PDC. If you or anyone else has changed the time settings on a server using group policy or registry modification, making the above changes via the w32tm command doesn't work properly.
Changes you make in the same active directory site should replicate quickly.
If you are making changes across AD sites then you will have to wait as long as you have set in your site to site replication settings.
)) and run the following: C:\net stop w32time C:\That prompts the local computer to sync to it's configured time source.
Beginning with Windows 2000, Microsoft includes the Windows Time Service with all versions of Windows.
Initially, the pupose of Windows Time Service was to keep all clocks on the Windows network loosely synchronized to support Kerberos authentication, which is time-sensitive to a degree.
The following command will tell us what the time service is up to as far as where the machine is getting its time from: w32tm /query /source On any other DCs the following needs to be run: w32tm /config /syncfromflags:domhier /reliable:no; w32tm /config /update; net stop w32time; net start w32time; w32tm /resync /rediscover On any member servers: w32tm /config /syncfromflags:domhier; w32tm /config /update; net stop w32time; net start w32time; w32tm /resync /rediscover Pasted from Tech Amature, I have same windows platform with you. during the 1 month, daylight savings time forwarded the clock an hour ahead.
Domain controller server time is not telly(1 hour back) with current time. I changed it manually in date and time settings,but it only a temporary solution.
Like most MSPs we've been doing a lot of virtualization in the past couple years.