Time Zone Automation

Question

I've seen some other threads and info online about automating time zone application during OSD, but it just isn't working for me.
I've added the following settings in my CustomSettings.ini. Running through a MDT simulation I get the correct settings. Doing an actual OSD, I see the correct time zone applied in the SMSTS.log file. But when the deployment is finished, it is back to Pacific
time zone. I have Pacific as the time zone in my "Apply Windows Settings" step which is after the gather step, so I thought that was the cause. Disabling "Apply Windows Settings" and adding in the info from that step to my answer file got
rid of the Pacific time zone, but made it some other zone I don't have defined anywhere.
So my question is if I am placing steps out of order? Is my CS.ini not formatted correctly? Should I not have disabled the "Apply Windows Settings" step?
[Settings]
Priority=DefaultGateway, Default
[DefaultGateway]
10.100.51.1=Site1
10.100.50.1=Site1
10.100.204.1=Site2
10.100.205.1=Site2
[Site1]
TimeZoneName=Hawaiian Standard Time
[Site2]
TimeZoneName=Greenland Standard Time

Answer 1

As mentioned, run-time configuration of value overwrites design time. Basically, everything set while creating or editing a task sequence is stored in a task sequence variable. You can thus conceptually think about these as being set at the start of the
task sequence executing. Thus, anything set while the task sequence is running, like things from MDT, will overwrite things set earlier.
There must be something else re-setting the timezone somewhere *or* MDT is not actually setting the value correctly.
Based on the MDT documentation, setting TimeZoneName is valid for ConfigMgr and thus should work. Are you using a default MDT task sequence in ConfigMgr?
You can try directly setting OSDTimeZone as that will directly overwrite the variable from the task.
Jason | http://blog.configmgrftw.com