Windows 10: WDS Deployment Fails on OOBE unattend file every time

Hello, My first post, but follow the site regularly! I am trying for the 1st time, to figure out WDS to deploy a customized W10 image. I have tried many, many times, and just can not get the unattend.xml file to work. I keep getting an error about "microsoft-shell-setup". I have validated the XML file repeatedly in System Image Manager, and it always passes. Nevertheless I keep removing things to try to narrow down the problem, but keeps failing every time. And of course the whole deployment process takes forever each time...so it's getting frustrating. I have included my current version of the file, if someone has thoughts about a possible cause. <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <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>0409:00000409</InputLocale> <SystemLocale>en-US</SystemLocale> <UILanguage>en-US</UILanguage> <UILanguageFallback>en-US</UILanguageFallback> <UserLocale>en-US</UserLocale> </component> <component name="Microsoft-Windows-Shell-Setup" 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"> <OOBE> <HideEULAPage>true</HideEULAPage> <HideLocalAccountScreen>true</HideLocalAccountScreen> <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen> <HideOnlineAccountScreens>true</HideOnlineAccountScreens> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <ProtectYourPC>1</ProtectYourPC> <UnattendEnableRetailDemo>false</UnattendEnableRetailDemo> </OOBE> <UserAccounts> <LocalAccounts> <LocalAccount wcm:action="add"> <Password> <Value>UwAzAHIAdgAxAGMAMwAhADMANgA1ACEARAAzAHMAawAhAFAAYQBzAHMAdwBvAHIAZAA=</Value> <PlainText>false</PlainText> </Password> <Description>Veeam Admin User</Description> <DisplayName>Veeam Admin</DisplayName> <Group>Administrators</Group> <Name>VeeamAdmin</Name> </LocalAccount> </LocalAccounts> </UserAccounts> <RegisteredOrganization>365 Technologies Inc</RegisteredOrganization> <RegisteredOwner>365 Technologies Inc</RegisteredOwner> <TimeZone>Central Standard Time</TimeZone> </component> </settings> <settings pass="specialize"> <component name="Microsoft-Windows-Shell-Setup" 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"> <CopyProfile>true</CopyProfile> <ComputerName></ComputerName> <OEMName></OEMName> <RegisteredOrganization>365Technologies</RegisteredOrganization> <RegisteredOwner>365Technologies</RegisteredOwner> <TimeZone>Central Standard Time</TimeZone> </component> </settings> <cpifflineImage cpi:source="wim:e:/esd/install.wim#Windows 10 Pro" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>

:)

 

WDS Deployment Fails on OOBE unattend file every time

Hello,

My first post, but follow the site regularly! I am trying for the 1st time, to figure out WDS to deploy a customized W10 image. I have tried many, many times, and just can not get the unattend.xml file to work. I keep getting an error about "microsoft-shell-setup".

I have validated the XML file repeatedly in System Image Manager, and it always passes. Nevertheless I keep removing things to try to narrow down the problem, but keeps failing every time. And of course the whole deployment process takes forever each time...so it's getting frustrating. I have included my current version of the file, if someone has thoughts about a possible cause.

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<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>0409:00000409</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UILanguageFallback>en-US</UILanguageFallback>
<UserLocale>en-US</UserLocale>
</component>
<component name="Microsoft-Windows-Shell-Setup" 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">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideLocalAccountScreen>true</HideLocalAccountScreen>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<ProtectYourPC>1</ProtectYourPC>
<UnattendEnableRetailDemo>false</UnattendEnableRetailDemo>
</OOBE>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>UwAzAHIAdgAxAGMAMwAhADMANgA1ACEARAAzAHMAawAhAFAAYQBzAHMAdwBvAHIAZAA=</Value>
<PlainText>false</PlainText>
</Password>
<Description>Veeam Admin User</Description>
<DisplayName>Veeam Admin</DisplayName>
<Group>Administrators</Group>
<Name>VeeamAdmin</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<RegisteredOrganization>365 Technologies Inc</RegisteredOrganization>
<RegisteredOwner>365 Technologies Inc</RegisteredOwner>
<TimeZone>Central Standard Time</TimeZone>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup" 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">
<CopyProfile>true</CopyProfile>
<ComputerName></ComputerName>
<OEMName></OEMName>
<RegisteredOrganization>365Technologies</RegisteredOrganization>
<RegisteredOwner>365Technologies</RegisteredOwner>
<TimeZone>Central Standard Time</TimeZone>
</component>
</settings>
<cpifflineImage cpi:source="wim:e:/esd/install.wim#Windows 10 Pro" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

 

Unattended install question

This one is more on track. W10 1809 WDS unattended configuration - cannot skip oobe - Software Deployment & Patching - Spiceworks

 

WDS 2013 Deployment Error

Hi Deejay,

For in-depth assistance regarding your concern with
WDS 2013 Deployment Error, we recommend posting your concern to
TechNet Forums. In this way, you'll receive the best advice/troubleshooting steps from IT
professionals who are more equipped in resolving this type of issue.

Keep us posted if you need additional help.