In our vCloud Director 5.5 instances I’ve noticed that all of our Windows VMs that are sysprepped by vCloud Director have their time zones set to GMT Standard Time.
VMs in vCloud Director will be sysprepped if “Changed SID” is enabled. “Enable guest customization” must be selected as well for any guest customization to occur.
After the guest are customized the time zone resets from the original time zone to the following:
vCloud Director syspreps the VMs by injecting an unattend.xml file into the guest and passes this file to sysprep. Here is the time zone section of this unattend.xml file in VM that was sysprepped by vCloud Director:
Prior to vCloud Director 5.5, the unattend.xml file was on the vCloud Director cells, but I was unable to find it on vCloud Director 5.5 cells. I was thinking that I could perhaps edit the unattend.xml file on cell and correct the problem.
I imagine this issue could be solved several different ways, but for now I decided to edit the customization script and have it set the time zone correctly. We use vCenter Orchestrator to build the customization script, but here is a simple example that sets the time zone to “Mountain Standard Time”.
if "%1%" == "precustomization" ( goto end ) else if "%1%" == "postcustomization" ( tzutil /s "Mountain Standard Time" ) :end
This is a temporary fix until VMware can resolve the issue. I’ve submitted a service request to them and will update this post when I receive an answer.