stolliv

i'm now leaning towards this issue being related to using a custom wim for installation instead of the OEM media.... what would i need to include in the WIM to make this work?

i dont think its currently the pen pairing causing the crash when i select another language as i dont get that far. I'm thinking it might be the winpe image, as i dont have that as multi-lingual right now either ... so i may need to do that. this is the relevant portion of the smsts.log but its pretty generaic and isnt really providing much help ... <![LOG[Expand a string: WinPE]LOG]!><time="15:24:50.700+300" date="10-19-2015" component="TSManager" context="" type="0" thread="940" file="executionenv.cxx:783"> <![LOG[Executing command line: osdwinsettings.exe /config]LOG]!><time="15:24:50.700+300" date="10-19-2015" component="TSManager" context="" type="1" thread="940" file="commandline.cpp:828"> <![LOG[============================[ OSDWinSettings.exe ]============================]LOG]!><time="15:24:50.731+300" date="10-19-2015" component="OSDWinSettings" context="" type="1" thread="1556" file="osdwinsettings.cpp:578"> <![LOG[Command line: "osdwinsettings.exe" /config]LOG]!><time="15:24:50.731+300" date="10-19-2015" component="OSDWinSettings" context="" type="0" thread="1556" file="osdwinsettings.cpp:579"> <![LOG[!sInstallType.empty(), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdcore\infanswerfile.cpp,322)]LOG]!><time="15:24:50.731+300" date="10-19-2015" component="OSDWinSettings" context="" type="0" thread="1556" file="infanswerfile.cpp:322"> <![LOG[Failed to read installation type from environment.. Please ensure you are running this executable inside a properly configured OS Deployment task sequence. Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="15:24:50.731+300" date="10-19-2015" component="OSDWinSettings" context="" type="3" thread="1556" file="infanswerfile.cpp:322"> <![LOG[OSD::Utility::BaseAnswerFile::CreateAnswerFile( pAnswerFile ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdwinsettings\osdwinsettings.cpp,363)]LOG]!><time="15:24:50.731+300" date="10-19-2015" component="OSDWinSettings" context="" type="0" thread="1556" file="osdwinsettings.cpp:363"> <![LOG[Failed to initialize answer file.]LOG]!><time="15:24:50.731+300" date="10-19-2015" component="OSDWinSettings" context="" type="3" thread="1556" file="osdwinsettings.cpp:363"> <![LOG[ConfigureWinSettings(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdwinsettings\osdwinsettings.cpp,636)]LOG]!><time="15:24:50.731+300" date="10-19-2015" component="OSDWinSettings" context="" type="0" thread="1556" file="osdwinsettings.cpp:636"> <![LOG[Failed to open the Task Sequencing Environment. Code 0x80004005. Please ensure you are running this executable inside a properly configured OS Deployment task sequence. Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="15:24:50.731+300" date="10-19-2015" component="OSDWinSettings" context="" type="3" thread="1556" file="osdwinsettings.cpp:636"> <![LOG[Exiting with return code 0x80004005]LOG]!><time="15:24:50.731+300" date="10-19-2015" component="OSDWinSettings" context="" type="1" thread="1556" file="osdwinsettings.cpp:646"> <![LOG[Process completed with exit code 2147500037]LOG]!><time="15:24:50.731+300" date="10-19-2015" component="TSManager" context="" type="1" thread="940" file="commandline.cpp:1124"> <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="15:24:50.731+300" date="10-19-2015" component="TSManager" context="" type="1" thread="940" file="instruction.cxx:805"> <![LOG[Failed to run the action: Apply Windows Settings. Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="15:24:50.747+300" date="10-19-2015" component="TSManager" context="" type="3" thread="940" file="instruction.cxx:911">

I am using Using Windows 10 Enterprise media from VLSC

this did in fact resolve my %OSDTimeZone% variable issue.... but i still get a task sequence error when i pick any language other than english. the error is: Failed to read required deployment parameter 'OSVersionNumber'. Please ensure you are running this executable inside a properly configured OS Deployment task sequence. Unspecified error (Error: 80004005; Source: Windows) which i havent been able to find any information about.

i dont have OEM installs for each region unfortunately. but what i noticed was .... every time i image my system in english, my OSDTimeZone variable doesnt apply, the system always comes up with pacific standard time, and when i try to select german the Task sequence crashes with a generic error. SO, while looking for these files for the different languages ... i opened the oobe.xml and i noticed it has the time zone specified as pacific standard time so i changed the file to read like this: <?xml version="1.0" encoding="utf-8"?> <FirstExperience> <oobe> <defaults> <locale>1034</locale> <keyboard>%KeyboardLocale%</keyboard> <timezone>%OSDTimeZone%</timezone> </defaults> <hidSetup> <title>Pen Setup</title> <accessoryImagePath>C:\Windows\System32\oobe\info\Default\1033\PenPairing_en-US.png</accessoryImagePath> <accessoryErrorImagePath>C:\Windows\System32\oobe\info\Default\1033\PenError_en-US.png</accessoryErrorImagePath> <accessoryText>Insert the battery, then press and hold the top button until the light blinks.</accessoryText> <accessoryErrorText>Pairing was not successful. Go to www.surface.com/support.</accessoryErrorText> <accessorySuccessImage>C:\Windows\System32\oobe\info\Default\1033\PenSuccess_en-US.png</accessorySuccessImage> <accessorySuccessText>Pairing was successful!</accessorySuccessText> </hidSetup> </oobe> </FirstExperience> so what i have done is removed the <location> tag entirely, set the <locale> line to match the parent folder - 1034 for spanish for this particular xml - and i put my task sequence variables in both <keyboard> and <timezone> because my feeling here is that this xml is being used after oobe is complete, which is why my task sequence time zone variable never seems to apply and my task sequence crashes when i select german because there is no 1031 folder for pen pairing. so (with DISM) i've made a folder for each language i have available from UDI in the c:\windows\system32\oobe\info\defaults directory and added the same XML with the appropriate <locale> tag in the xml currently i'm recapturing my wim, and then i'll have to update my distribution points before i can test and i'll post back the results .... seems like a good solution to me though? also, yes i just left all of the <Accessory...> tags pointing back to the 1033\en-us.png files because i dont feel like re-creating them in 8 languages (some of them are in the original OEM though)

Where can i find the oobe/info files in different languages for the SurfacePro3 pen pairing?

Setting up windows 10 deployment from SCCM, using UDI and I'm having a problem with the UILanguage variable from UDI not working. I had the same problem with Windows 7 and gave up looking for a solution. My WIM file that is used has english, chinese, french, italian, spanish, dutch, and german language packs installed in it before it was captured with DISM. My unattend file has the following section with the UDI variables in it: <settings pass="oobeSystem"> <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <InputLocale>%KeyboardLocale%</InputLocale> <SystemLocale>%SystemLocale%</SystemLocale> <UILanguage>%UILanguage%</UILanguage> <UILanguageFallback>en-US</UILanguageFallback> <UserLocale>%UserLocale%</UserLocale> </component> everything works except UILanguage, including the rest of the unattend file to join the domain and a bunch of other settings. When Windows boots, instead of the task sequence continuing along i get prompted by OOBE to select a language of the ones installed. after i select a language, the task sequence continues until its done. Does anyone have an thoughts or ideas on this?