Vista Mini-setup answer file error after Sysprep

[Chad Skinner]

Using WAIK WSIM 6.1.7100 to create an answer file for the mini-setup. I'm
using Vista SP2 that I got from my MSDN Account Free Build 342266 and the
lincense key from my account. After I customize my image:
sysprep /generalize /oobe /reboot /unattend:myanswerfile.xml

I get an error "Windows setup could not configure windows to run on this
computer's hardware" about 80% of the way through mini-setup. From what I
understand this is exactly the situation it should work?!?

My answer 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.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>en-US</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="x86" publicKeyToken="31bf3856ad364e35"
language="neutral" versionScope="nonSxS"
xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<AutoLogon>
<Password>

<Value>UABAAHMAcwB3ADAAcgBkAFAAYQBzAHMAdwBvAHIAZAA=</Value>
<PlainText>false</PlainText>
</Password>
<Enabled>true</Enabled>
<LogonCount>5</LogonCount>
<Username>User</Username>
<Domain>Fresh</Domain>
</AutoLogon>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>

<Value>UABAAHMAcwB3ADAAcgBkAFAAYQBzAHMAdwBvAHIAZAA=</Value>
<PlainText>false</PlainText>
</Password>
<Group>administrators;power users</Group>
<DisplayName></DisplayName>
<Name>User</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<RegisteredOwner>PRST</RegisteredOwner>
<RegisteredOrganization>Intel</RegisteredOrganization>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Home</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
<SkipUserOOBE>true</SkipUserOOBE>
</OOBE>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup"
processorArchitecture="x86" publicKeyToken="31bf3856ad364e35"
language="neutral" versionScope="nonSxS"
xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ComputerName>Fresh</ComputerName>
<ShowWindowsLive>false</ShowWindowsLive>
<ProductKey>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</ProductKey>
<TimeZone>Pacific Standard Time</TimeZone>
<RegisteredOwner />
</component>
</settings>
<cpifflineImage cpi:source="wim://wim/images/pkvistasp2.wim#Vista SP2"
xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

 

[Zaphod Beeblebrox]

Using WAIK WSIM 6.1.7100 to create an answer file for the
mini-setup. I'm
using Vista SP2 that I got from my MSDN Account Free Build 342266
and the
lincense key from my account. After I customize my image:
sysprep /generalize /oobe /reboot /unattend:myanswerfile.xml

I get an error "Windows setup could not configure windows to run on
this
computer's hardware" about 80% of the way through mini-setup. From
what I
understand this is exactly the situation it should work?!?

My answer file:

<snip>

Since it sounds like a driver problem, you might try setting the
answerfile to keep all the installed drivers so that Vista doesn't
re-detect and re-install them.You do that using the
PersistAllDeviceInstalls property of the Microsoft-Windows-PnpSysprep
component in the generalize pass, like this:

<settings pass="generalize">
<component name="Microsoft-Windows-PnpSysprep"
processorArchitecture="x86" publicKeyToken="31bf3856ad364e35"
language="neutral" versionScope="nonSxS"
xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
</component>
</settings>

Hope this helps.

 

[Chad Skinner]

ZB,
Thanks for the response, I think I figured it out. Being this is the first
time using ImageX I negelected a very important step which is formatting the
drive before imaging the system. What was happening is some of the license
information (or sysprep data, not sure which yet) was not wiped out by ImageX
as it doesn't care as long as there is not a conflict.

Thanks,
Chad