W10 answer file

[Tripredacus]

Are you saying you validated Mavericks' XML in WSIM or your own?

If you deploy with DISM, it will use the XML in the WIM.

If you deploy with Setup, it will use the XML in the root, unless otherwise specified.

[MAVERICKS CHOICE]

 

Are you trying to use the ISO from the Media Creation Tool?

 

Yes, though I manually ran setup with no problems.

With a minimal xml it will go straight through to desktop no problem.

[kmaheshkumar]

i am not gonna deploy my xml with dism because we cannot find it in future if we need to modify only some setting so i just kept the xml in wim file but my installation needs user to do everything is there anyway that works with two xml files ? i just asking do anyone tried them

 

it means minimal xml for setup 

and all other full xml for oobe, user creation etc.

[Tripredacus]

Ok, there is no official word that I am aware of concerning the re-imaging rights of the ISO from the Media Creation Tool. We do know it initially comes as a converted ESD file and that DISM can't mount it. We also know some people have done deploy/capture or use N(T?)Lite to convert the file so DISM can mount it.

 

OEM/FPP editions of Windows 10 do not have the ESD type install.wim, which leads me to believe that Microsoft does not want the Free Upgrade ISO to be used to make an image. And there are multiple people on Technet reporting that using this ISO with an XML that certain things in Specialize pass are ignored, the primary one being ComputerName.

 

I can do 1 test to see if OEM/SB Windows 10 uses the ComputerName object in the XML.

 

Update It does not work with OEM System Builder. I deployed my image to Audit Mode, then sysprep /reboot /oobe /unattend using this XML:

 

<?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend">    <settings pass="windowsPE">        <component name="Microsoft-Windows-International-Core-WinPE" 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">            <SetupUILanguage>                <UILanguage>en-us</UILanguage>            </SetupUILanguage>            <InputLocale>en-us</InputLocale>            <UILanguage>en-us</UILanguage>            <SystemLocale>en-us</SystemLocale>            <UILanguageFallback>en-us</UILanguageFallback>            <UserLocale>en-us</UserLocale>        </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">            <ComputerName>NameTest</ComputerName>            <TimeZone>Pacific Standard Time</TimeZone>        </component>    </settings>    <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>            <UserLocale>en-us</UserLocale>        </component>          </settings>    <cpi:offlineImage cpi:source="catalog:d:/sources/install_windows vista business.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" /></unattend>

 

It did not rename the computer.

Edited September 2, 2015 by Tripredacus

[MAVERICKS CHOICE]

Thanks Trip, Have not modified my image at all straight from the MS creation tool. Have added some specialize passes. will do some more

testing with computer name.

[kmaheshkumar]

syspreped images of windows 10 having much issues 

while i did sysprep the below thing worked for me

<ComputerName>NameTest</ComputerName>

[MAVERICKS CHOICE]

Running win 7 x64 & MS say it is ok to use Win 7 as a host to use Win 10.

I cleaned up my rig today & ran sfc /scannow command & voila immediately had the latest WSIM working flawlessly.

There are many previous settings deprecated now in Win 10.

Have made great progress & will do more vigorous testing.

[SunLion]

Hello

I'm trying to create an image for clean installation with autounattend.xml, but am having problems.

My language is Portuguese-Brazil.
 

In tests in VirtualBox are created two users: Administrator and Administrator-USUBDRVG.
 

What am I doing wrong?
 

Follow my autounattend.xml file

I appreciate the help of the Advanced

Autounattend.xml

[Tripredacus]

It looks like you are adding an account called Administrator. It already exists in the OS but is disabled. Try to create a user account with a different name instead.

[kmaheshkumar]

for Hyper V you can try this it generates everything for you but use Custom Product Key if it not provided in application