ssheehy71 Posted September 11, 2012 Report post Posted September 11, 2012 I am at my wits end here. I have tried everything I can think of and I have had no luck with this. I am trying to get my Task Sequence to modify the time zone setting based on a Collection Variable setting I have created. Here's how it works. 1. Upon bootup, the Task Sequence Wizrd Appears, and the user selects the Taks sequence 2. Next they are prompted for the Task Sequence Variable to edit. The available options are: a. languageValue b. OSDcomputerName c. regionValue All of these variables work great, but my problem is I want the TimeZone to adjust based on the regoinValue that is entered. Here is my unattend.xml file <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="oobeSystem"> <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.micro...nfig/2002/State" xmlns:xsi="http://www.w3.org/20...Schema-instance"> <InputLocale>%OSDInputLocale%</InputLocale> <SystemLocale>%OSDSystemLocale%</SystemLocale> <UILanguage>%OSDUILanguage%</UILanguage> <UILanguageFallback>%OSDUILanguageFallback%</UILanguageFallback> <UserLocale>%OSDUserLocale%</UserLocale> </component> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.micro...nfig/2002/State" xmlns:xsi="http://www.w3.org/20...Schema-instance"> <OOBE> </OOBE> <TimeZone>%OSDTimeZone%</TimeZone> </component> </settings> <cpi:offlineImage cpi:source="wim:c:/sccm/osdeploy/win732enterprisesp1.wim#1" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend> Any help would be AWESOME! Quote Share this post Link to post Share on other sites More sharing options...
ssheehy71 Posted September 12, 2012 Report post Posted September 12, 2012 Nevermind. I fixed my problem and I feel so stupid. LOL! I never added the OSDTimeZone into the Task Sequence Variables at bootup. DUH! Quote Share this post Link to post Share on other sites More sharing options...