Hi,
Guess it's a basic question. The thing is that we are migrating our TS from a standard SCCM task sequence to an SCCM MDT task sequence and we are facing an issue. Some context below:
We have our cs.ini file properly configured and it's working fine, everything gets configured as expected. Basically we have a userexit script that determines the site every computer belongs to reading a specific variable configured during our preprovision web front-end. Once the site has been determined, several regional settings are configured per site (keyboard layout, timezone...etc). Find below a sample of our CS.ini (just an example, not real sites):
[Settings]
Priority=BySite, Site, Default
[BySite]
UserExit=ZTIGetSite.vbs
Site=#GetSite()#
[Site1]
KeyboardLocale=de-at
UserLocale=de-at
UILanguage=de-at
TimeZoneName=Romance Standard Time
[Site2]
KeyboardLocale=en-US
UserLocale=en-US
UILanguage=en-US
TimeZoneName=Tasmania Standard Time
...
_SMSTSOrgName=Running %TaskSequenceID% on %OSDComputername%
OSInstall=Y
SkipAdminPassword=YES
SkipApplications=YES
SkipAppsOnUpgrade=YES
SkipBDDWelcome=YES
SkipBitLocker=YES
....
The file works fine, no issue on it but, we prefer not typing the local admin password on the cs.ini file and when we enable the step "apply windows settings" to configure the local admin password, we are obligated to configure a time zone for this step -see the picture:
Well, the problem is that when we enable this steps, all the the time zone values in our cs.ini file get overwritten by this one and all clients finish the OSD process with the Eastern Time configured instead of their regional value. Is there a way to change this behavior and keep the "apply windows settings" step enabled to configure the local admin password? We wouldn't like to move the password into the cs.ini file using clear text (or even 64base encoded).
Thanks.
Regards.