Issue:
Domain Controller A is sitting in a different time zone and Domain Controller B that holds the PDC Emulator FSMO role is sitting in another time-zone.

DC A is on WS2019  – does not use Daylight saving settings
DC B is on WS2012R2 – uses Daylight saving

Ideally DC A should run 1 hour behind as they are not using the daylight saving option, but DC A’s time is the same as DC B’s time.

Things checked:
Changed the Day light savings option from windows time but no change.

Tried running the below commands, no errors
w32tm /query /status
w32tm /resync – No errors and taking the PDC time

Changed the DC A’s time manually by using the Time command in CMD, but when I executed the w32tm /resync, it syncs with the DC B’s time.

Resolution:
Start –> timedate.cpl –> Right-click and select Run As Administrator

Change the time zone if required and un-check the option “Automatically adjust clock for Daylight Saving Time” –> Press OK

And now if you run the commands w32tm /resync and w32tm /query /status it will stay the same according to the time zone that DC A is in and also still sync with the DC B that holds the PDC emulator role.

Useful command to monitor the time
w32tm /monitor

Hope this helps if your Domain Controllers sitting in different time zones and running on 2019 Servers.

[Cover image: https://science.howstuffworks.com/environmental/earth/geophysics/time-zone.htm]