Background: I have a single domain, running in 2 sites that is connected using Site-to-Site VPN.

  • Site A is running in time zone 2:00+ UTC
  • Site B is running in time zone 4:00+ UTC

DCs are correctly placed into their own corespondent subnet in the Active Directory Sites and Services. All DCs are running Windows 2012 R2, all clients are running Windows 8.1

What I am trying to achieve: sync all users in the domain with an external NTP server for login purposes with an online service, I enabled NTP on the PDC to sync with an external source using the Microsoft FixIT article http://support.microsoft.com/en-us/kb/816042.

What really happened: users in Site A are working correctly, users in Site B are syncing from the PDC too, but their time zone keeps changing from 4:00+ UTC to 2:00+ UTC, users in Site B can change the TZ back to 4:00+ UTC, but whenever their machines resync with the PDC, the TZ changes back to 2:00+ UTC.

How I tried to solve this problem: I created a group policy computer start up script that reads

Tzutil.exe /s "Arabian Standard Time"

The syntax should change the TZ to 4:00 UTC, I linked the login script to Site B, I can confirm that the script is running successfully and the time changes to 2:00+ UTC upon login, however, after awhile, the machines sync to the PDC and the TZ goes back to 2:00+ UTC.


  • The thing about this that I'm confused on, is that it appears as though you are conflating two separate issues. NTP and time zones are two separate things. In other words, NTP doesn't confer any time zone to the client. It's all UTC. So the timezones being changed is something else... – Ryan Ries Apr 7 '15 at 19:15
  • That's where my puzzlement come, my problem started right after we configured the NTP service on the PDC using the Microsoft FixIt tool, I went to read the technicalities of the the tool several times, it shows nothing regarding the time zone change, I have tired to look all over the internet how both are related and I couldn't find any, I thought of asking here hoping to find the missing piece of the puzzle. – Noor Khaldi Apr 8 '15 at 5:21
  • It is also possible to set client timezone via DHCP. Perhaps you have that option enabled on your DHCP server, which overrides other settings on the clients? – Ryan Ries Apr 9 '15 at 13:24
  • I'm using two different DHCP servers, one for each site, I have rechecked my settings on both, I have only the default scope options enabled. so I believe that DHCP got nothing to do with this. – Noor Khaldi Apr 10 '15 at 10:18

So I contacted Microsoft for this, they were very puzzled as well, we never figured out why the time zone change by it self or which process was causing this behavior, but they gave me a work around that fixed my problem, I'm going to post here for future referencing (copy/pasting from Microsoft communication with me)

Regarding the current issue, if it is possible, I suggest you define the group policy

Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Change the Time Zone

to determine which users and groups can change the time zone. Please check my test:

enter image description here

enter image description here

The users which don’t have rights will unable to change the time zone:

enter image description here

| improve this answer | |

Know this is an old issue, however, we were experiencing the same problem at our 2 sites recently so thought we'd share our experience.
There is a Scheduled Task built into Windows called SynchronizeTimeZone that runs tzsync.exe which syncs the Time Zone to the closest RWDC. In our case we disabled this task on clients & used TZUtil.exe to set the correct time zone again.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.