Jump to content

Adding settings to Autounattend.xml with WSIM fails


ajua

Recommended Posts

I set the image name to Windows Vista ULTIMATE and it didn't work, the same error.

I also tried making a new xml file, added settings without any luck.

basically im stuck at using vLite xml and without adding nothing more except InstallFrom Image Name for it to not display the version window at WinPE.

Link to comment
Share on other sites


You could poin Wsim at an original install.wim and then u could add all the settings you'd like! Providing you havnt added some from the vlited image. If you have then i would suggest recreating your autounattend using the vlited image.

Link to comment
Share on other sites

i did that, made one autounattend.xml with WSIM and original untouched image to add settings then created one vLite source and one autounattend.xml with it. then i added settings from the first xml file to the one created by vLite but my real-world install failed at what i think would be the specialize pass.

im going to integrate hotfixes and spanish language pack manually and then i will try to use WSIM to create autounattend.

Link to comment
Share on other sites

i just made 4 installations doing the updates and the language pack manually and all worked fine with WSIM.

So im thinking that the problem may reside somewhere between vLite image actions and/or WSIM way of cataloging .wim images that have other versions stripped off.

anyway, im doing the manual way until i figure this out because i really want to use WSIM to improve my XML files...

Link to comment
Share on other sites

  • 1 month later...

I was getting the enumeration error so went ahead a rebuilt the Autounattend.xml file in Windows System Image Manager component by component and watching for differences. This line had the difference that fixed the problem:

From new Autounattend.xml:

		<component name="Microsoft-Windows-Security-Licensing-SLC-UX" 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">

From vLite Autounattend.xml:

		<component name="Microsoft-Windows-Security-Licensing-SLC-UX" 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">

See the difference? Take a look at NonSxS :thumbup

Link to comment
Share on other sites

This time I'm working on an x86 build and notice the same thing with the "n", but different...

Lines from newly built (by hand) Autounattend.xml:

		<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">
<component name="Microsoft-Windows-Security-Licensing-SLC-UX" 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">

and the same lines from vLite:

		<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">
<component name="Microsoft-Windows-Security-Licensing-SLC-UX" 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">

I guess the first "n" in NonSxS is supposed be caps and the in the second line it's upper case? :huh::rolleyes:

Link to comment
Share on other sites

jimanny, that is weird. Especially the part where it matters to the WAIK since it mixes as well, can you recheck that, change the first letter and try to import the XML.

Better yet replace all in vLite xml to big letter first and see if that passes.

Link to comment
Share on other sites

i got the same error when i use waik to enable

Microsoft-Windows-Foundation-Package feathers

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<servicing>
<package action="configure">
<assemblyIdentity name="Microsoft-Windows-Foundation-Package" version="6.0.6001.17051" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="" />
<selection name="DesktopExperience" state="true" />
<selection name="SearchEngine-Server-Package" state="true" />
<selection name="QWAVE" state="true" />
</package>
</servicing>

"Choose WIM, generate catalog, open XML, answer Yes."

tried that not working

Edited by aviv00
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...