SCCM Deployment OOBE issue using xml File

Hi All

I am rolling out windows 10 Enterprise using SCCM. The image that I have taken is from the msdn network and has a option of which Image i would like to use. (Please see pic labelled 1)

I am trying to create an automation so that it does not prompt me for network setup and also i would like it to add the UK region as default. My XML looks as follows:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="specialize">
<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>0809:00000809</InputLocale>
<SystemLocale>en-GB</SystemLocale>
<UILanguage>en-GB</UILanguage>
<UILanguageFallback>en-GB</UILanguageFallback>
<UserLocale>en-GB</UserLocale>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="wow64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideLocalAccountScreen>true</HideLocalAccountScreen>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<ProtectYourPC>3</ProtectYourPC>
</OOBE>
</component>
</settings>
<cpifflineImage cpi:source="wim:c:/temp/install.wim#Windows 10 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>


It is very basic and that is all i need for it to do.

I have used something similar on a 1803 and it works fine

I created the 1809 XML using the Windows System Image Manager which i got from 1809 adk tools

Can anybody see any errors in this code?

Just for information it seems to be skipping OOBE now but when windows loads it is not loading the uk keyboard. For example my @ sign is mixed up with my number 2 symbol

Thanks

Andy

There's nothing wrong in that answer file, assuming that original ISO is in UK English. The input locale is correct, as are other localisation settings.

I'll test the answer file later today and post my findings here.

Kari

Screenshot from your answer file, you've used processor architecture wow64 here:



Only change I made was to change that to amd64, UK English keyboard was made default after running Sysprep with that only slightly modified answer file.

Kari

andy12345 said:

Hi

Thanks for that tip above. I tested this and it works perfect! thanks

You are welcome!

Nice catch, @Kari! It's always the "little things" that cause problems.
--Ed--