we are facing to very weird situation. We used customization specifications for building of new VMs and we set there time zone according to the site locality. When the VM is booting first time, the time setting is absolutely the same as have the template from which is deployed. After that are running the custom. spec. jobs and time zone is set properly.
BUT, only for UTC timezone and UTC+ zones is time set properly (the set time is corresponding with the time zone)
Anyway for UTC- zones is set only the time zone, but time itself is the same as was in template (so absolutely wrong)
For example, I have 09 AM UTC in template. After application of custom. spec. is time 11 AM EET (for Finland, correct), but still 09 AM CST (for USA, wrong)
I tested many time zones and commonly I can say, working are only UTC+ zones
Any idea, how is it possible? We used vmware 6.7 U3
Yes, the ESXi hosts are in domain and all have set the same NTP server. It is vSAN cluster, so time disbalance is checked also by vSAN health check. The ESXi host have correct UTC time.
When I deploy the server from template without specifications, the time is not related to HOST, but the same as is in template.
With the specification it fully works only for UTC and UTC+ time zones.
For UTC- zones is set the zone in OS, but time itself remains the same (is not moved by "the zone difference" as for the UTC+ zones)