This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 69%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EL%3C/text%3E%3C/svg%3E)
Hello everyone,
We are using MDT for offline deployment for some time now and we've noticed a strange behaviour while deploying Windows 10 20H2.
In "CustomSettings.ini file" we've set SkipTimeZone=NO so the user can choose the preferred TimeZone.
Today our V&V group found out that although the TimeZone is being set to Jerusalem, once Windows deployment finishes it seems that the TimeZone is set to 'Pacific Standard Time". I've tried a second deployment and chose "Hawaii" TimeZone and this time everything worked ok.
We've then deployment an earlier Windows 10 build (2004, just changed the deployed OS) --> chose "Jerusalem" TimeZone and confirmed that the TimeZone is indeed Jerusalem once Windows deployment finishes.
I didn't check other TimeZone so I'm not sure if the issue we've encountered with Windows 10 20H2 Jersusalem TimeZone appears in any other TimeZones.
Any ideas will be highly appreciated.
Thanks,
Liran.
Update: It seems that replacing Jerusalem TZ from "Jerusalem Standard Time" to "Israel Standard Time" in DeployWiz_LanguageUI.xml file resolved the issue.
However, since this issue only occurred with the 20H2 release I wonder what changed in 20H2 that triggered this behavior.
Any ideas?