Create your own Autounattend.xml All-In-One (x86/amd64)

ar_seven_am · December 1, 2011

myselfidem, you dont need to set 2 setting in "<settings pass="windowsPE">" becuz that only for boot.wim which we used only one (x86 boot.wim), if we do add x64 setting too, some automated task like "Accept EULA" will be asked again if we choose x64 image.

also I'm still tryin' to find out how to make custom menu so incase we need to repair our windows installation, we can still use our customized dvd (if we add autounattended setting there, it will skipped n directly to windows installation).

also guys, if you use usb as ur installation media, it's recommended to follow ricktendo methode (copy the autounattend.xml into boot.wim image index 2, offcourse you need to mount that first and unmount with option commit), that methode work for me everytime.

myselfidem · December 1, 2011

myselfidem, you dont need to set 2 setting in "<settings pass="windowsPE">" becuz that only for boot.wim which we used only one (x86 boot.wim), if we do add x64 setting too, some automated task like "Accept EULA" will be asked again if we choose x64 image.

Weird! Tested whithout error my Autounattend.xml file AIO (x86/amd64) and no double messages (like "Accept EULA")!

Could you share your Autounattend.xml file ?

Edited December 1, 2011 by myselfidem

bphlpt · December 2, 2011

Thanks! Link works fine.

Cheers and Regards

ar_seven_am · December 2, 2011

Weird! Tested whithout error my Autounattend.xml file AIO (x86/amd64) and no double messages (like "Accept EULA")!
Could you share your Autounattend.xml file ?

this is what I used now, I do clean install yesterday so I've deleted temporary files in my pc (I'm sorry, I dont know u need that) :

Autounattend.xml

the only different with the non working one is there's no ""<settings pass="windowsPE">" for x64. (I hope u understand with that, I havent install the english translator, sorry).

myselfidem · December 2, 2011

Yes, I understand. Many thanks.

I haven't this problem.

Missing inside your Autounattend.xml file AIO the first lines:


<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">

I will make an test with your values BUT adding subfolders (x86 and x64) for RunSynchronousCommands and FirstLogonCommands.

Examples:


<FirstLogonCommands>
				<SynchronousCommand wcm:action="add">
					<CommandLine>hidcon %SystemDrive%\Install\x64\FirstLog_x64.cmd</CommandLine>
					<Description>Post Setup Installation</Description>
					<Order>1</Order>
					<RequiresUserInput>false</RequiresUserInput>
				</SynchronousCommand>
			</FirstLogonCommands>


<component name="Microsoft-Windows-Deployment" 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">
			<RunSynchronous>
				<RunSynchronousCommand wcm:action="add">
					<Order>1</Order>
					<Path>%SystemDrive%\Install\Apps\Daemon\x86\SPTDinst-x86.exe add /q</Path>
				</RunSynchronousCommand>
			</RunSynchronous>
		</component>

Edited January 21, 2012 by myselfidem

ar_seven_am · December 2, 2011

Yes, I understand. Many thanks.

I haven't this problem.

Missing inside your Autounattend.xml file AIO the first lines:


<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">

I will make an test with your values BUT adding subfolders (x86 and x64) for RunSynchronousCommands and FirstLogonCommands.

Examples:


<FirstLogonCommands>
				<SynchronousCommand wcm:action="add">
					<CommandLine>hidcon %SystemDrive%\Install\x64\FirstLog_x64.cmd</CommandLine>
					<Description>Post Setup Installation</Description>
					<Order>1</Order>
					<RequiresUserInput>false</RequiresUserInput>
				</SynchronousCommand>
			</FirstLogonCommands>


<component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="[url="http://schemas.microsoft.com/WMIConfig/2002/State"]http://schemas.microsoft.com/WMIConfig/2002/State[/url]" xmlns:xsi="[url="http://www.w3.org/2001/XMLSchema-instance"]http://www.w3.org/2001/XMLSchema-instance[/url]">
			<RunSynchronous>
				<RunSynchronousCommand wcm:action="add">
					<Order>1</Order>
					<Path>%SystemDrive%\Install\Apps\Daemon\x86\SPTDinst-x86.exe add /q</Path>
				</RunSynchronousCommand>
			</RunSynchronous>
		</component>

edit: I've mistakenly upload file, that's only some copy paste I made before so I can check in panther folder. yes it doesn't have what u specified above, havent notice that until I download the attachment (the current firstlogon.cmd doesn't add hidcon.exe binary file).

here's the correct autounattend.xml (sorry) :

Autounattend.xml

Edited December 2, 2011 by ar_seven_am

myselfidem · December 2, 2011

Thanks.

It's not recommended to use "hidecon.exe" inside: %SystemDrive%\System32...exept, if you remove the command after the silent installation !

Edited December 4, 2011 by myselfidem

RicaNeaga · December 3, 2011

About Input Locales - it's best from my experiences with the unattended file made by myselfidem to use the windows 7 values instead of xp/vista ones.

I mean this values instead of this values.

If not, for example if I choose the usual US input locale from xp/vista (0409:00000409), I get two inputs in win7 - US International and US English, instead of only US International if I use the win7 values (0x00020409).

RicaNeaga · December 3, 2011

And one more thing - the setting <RegisteredOrganization>xxxxxx</RegisteredOrganization> isn't required for an unattended setup for windows 7.

I've deleted the .xml from 2 days ago, because my final complete unnatended xml file looks like the one attached right now, perfect for me. Thanks again, myselfidem

Autounattend.xml

myselfidem · December 4, 2011

@RicaNeaga

Thanks

@ar_seven_am

About Autounattend.xml AIO (x86/amd64).

I made many, many tests...

- First, I see that all passes are proceded, even when they are reversed (first amd64 and after x86).

(We can see that inside: C:\Windows\Panther\unattend.xml)

- Second: If the same batch is used, it will be launched two times and the installation may fails.

A workaround is to use different batches for each version (x86 and amd64) using "RunSynchronousCommand" and/or "FirstLogonCommand"

Example working fine for me with Autounattend.xml AIO (x86/amd64):

Tested successfully with my DVD Windows 7 AIO for image 32-bit and image 64-bit ! No errors.

Autounattend.xml (using default key for Windows 7 Ultimate. The name is fictitious...)

<?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="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">
<SetupUILanguage>
<UILanguage>fr-FR</UILanguage>
</SetupUILanguage>
<InputLocale>100c:0000100c</InputLocale>
<SystemLocale>fr-CH</SystemLocale>
<UILanguage>fr-FR</UILanguage>
<UserLocale>fr-CH</UserLocale>
</component>
<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>fr-FR</UILanguage>
</SetupUILanguage>
<InputLocale>100c:0000100c</InputLocale>
<SystemLocale>fr-CH</SystemLocale>
<UILanguage>fr-FR</UILanguage>
<UserLocale>fr-CH</UserLocale>
</component>
<component name="Microsoft-Windows-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">
<Diagnostics>
<OptIn>false</OptIn>
</Diagnostics>
<DiskConfiguration>
<WillShowUI>OnError</WillShowUI>
<Disk wcm:action="add">
<DiskID>0</DiskID>
<WillWipeDisk>true</WillWipeDisk>
<CreatePartitions>
<CreatePartition wcm:action="add">
<Order>1</Order>
<Type>Primary</Type>
<Size>100</Size>
</CreatePartition>
<CreatePartition wcm:action="add">
<Order>2</Order>
<Type>Primary</Type>
<Extend>true</Extend>
</CreatePartition>
</CreatePartitions>
<ModifyPartitions>
<ModifyPartition wcm:action="add">
<Active>true</Active>
<Format>NTFS</Format>
<Label>system</Label>
<Order>1</Order>
<PartitionID>1</PartitionID>
</ModifyPartition>
<ModifyPartition wcm:action="add">
<Format>NTFS</Format>
<Label>SEVEN</Label>
<Letter>C</Letter>
<Order>2</Order>
<PartitionID>2</PartitionID>
</ModifyPartition>
</ModifyPartitions>
</Disk>
</DiskConfiguration>
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1280</HorizontalResolution>
<VerticalResolution>1024</VerticalResolution>
<RefreshRate>60</RefreshRate>
</Display>
<DynamicUpdate>
<Enable>false</Enable>
<WillShowUI>Never</WillShowUI>
</DynamicUpdate>
<ImageInstall>
<OSImage>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>2</PartitionID>
</InstallTo>
<WillShowUI>OnError</WillShowUI>
<InstallToAvailablePartition>false</InstallToAvailablePartition>
</OSImage>
</ImageInstall>
<UserData>
<ProductKey>
<WillShowUI>OnError</WillShowUI>
<Key>D4F6K-QK3RD-TMVMJ-BBMRX-3MBMV</Key>
</ProductKey>
<AcceptEula>true</AcceptEula>
<FullName>Paul Dupont</FullName>
<Organization>particulier</Organization>
</UserData>
<EnableFirewall>true</EnableFirewall>
</component>
<component name="Microsoft-Windows-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">
<Diagnostics>
<OptIn>false</OptIn>
</Diagnostics>
<DiskConfiguration>
<WillShowUI>OnError</WillShowUI>
<Disk wcm:action="add">
<DiskID>0</DiskID>
<WillWipeDisk>true</WillWipeDisk>
<CreatePartitions>
<CreatePartition wcm:action="add">
<Order>1</Order>
<Type>Primary</Type>
<Size>100</Size>
</CreatePartition>
<CreatePartition wcm:action="add">
<Order>2</Order>
<Type>Primary</Type>
<Extend>true</Extend>
</CreatePartition>
</CreatePartitions>
<ModifyPartitions>
<ModifyPartition wcm:action="add">
<Active>true</Active>
<Format>NTFS</Format>
<Label>system</Label>
<Order>1</Order>
<PartitionID>1</PartitionID>
</ModifyPartition>
<ModifyPartition wcm:action="add">
<Format>NTFS</Format>
<Label>SEVEN</Label>
<Letter>C</Letter>
<Order>2</Order>
<PartitionID>2</PartitionID>
</ModifyPartition>
</ModifyPartitions>
</Disk>
</DiskConfiguration>
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1280</HorizontalResolution>
<VerticalResolution>1024</VerticalResolution>
<RefreshRate>60</RefreshRate>
</Display>
<DynamicUpdate>
<Enable>false</Enable>
<WillShowUI>Never</WillShowUI>
</DynamicUpdate>
<ImageInstall>
<OSImage>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>2</PartitionID>
</InstallTo>
<WillShowUI>OnError</WillShowUI>
<InstallToAvailablePartition>false</InstallToAvailablePartition>
</OSImage>
</ImageInstall>
<UserData>
<ProductKey>
<WillShowUI>OnError</WillShowUI>
<Key>D4F6K-QK3RD-TMVMJ-BBMRX-3MBMV</Key>
</ProductKey>
<AcceptEula>true</AcceptEula>
<FullName>Paul Dupont</FullName>
<Organization>particulier</Organization>
</UserData>
<EnableFirewall>true</EnableFirewall>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Security-SPP-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">
<SkipAutoActivation>true</SkipAutoActivation>
</component>
<component name="Microsoft-Windows-Security-SPP-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">
<SkipAutoActivation>true</SkipAutoActivation>
</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">
<ComputerName>Paul-PC</ComputerName>
<TimeZone>W. Europe Standard Time</TimeZone>
</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">
<ComputerName>Paul-PC</ComputerName>
<TimeZone>W. Europe Standard Time</TimeZone>
</component>
<component name="Microsoft-Windows-Deployment" 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">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Path>cmd /c %SystemDrive%\Install\SPTDinst_x86.cmd</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
<component name="Microsoft-Windows-Deployment" 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">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Path>cmd /c %SystemDrive%\Install\SPTDinst_x64.cmd</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
</settings>
<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>100c:0000100c</InputLocale>
<UILanguage>fr-FR</UILanguage>
<UserLocale>fr-CH</UserLocale>
</component>
<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>100c:0000100c</InputLocale>
<UILanguage>fr-FR</UILanguage>
<UserLocale>fr-CH</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">
<TimeZone>W. Europe Standard Time</TimeZone>
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1280</HorizontalResolution>
<VerticalResolution>1024</VerticalResolution>
<RefreshRate>60</RefreshRate>
</Display>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Home</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
</OOBE>
<AutoLogon>
<Enabled>true</Enabled>
<LogonCount>9999999</LogonCount>
<Username>Paul</Username>
</AutoLogon>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<Description>Post Setup Installation</Description>
<CommandLine>cmd /c %SystemDrive%\Install\FirstLog_x86.cmd</CommandLine>
<Order>9</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
</FirstLogonCommands>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value></Value>
<PlainText>true</PlainText>
</Password>
<DisplayName>Paul</DisplayName>
<Name>Paul</Name>
<Group>Administrators</Group>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
</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">
<TimeZone>W. Europe Standard Time</TimeZone>
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1280</HorizontalResolution>
<VerticalResolution>1024</VerticalResolution>
<RefreshRate>60</RefreshRate>
</Display>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Home</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
</OOBE>
<AutoLogon>
<Enabled>true</Enabled>
<LogonCount>9999999</LogonCount>
<Username>Paul</Username>
</AutoLogon>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<Description>Post Setup Installation</Description>
<CommandLine>cmd /c %SystemDrive%\Install\FirstLog_x64.cmd</CommandLine>
<Order>9</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
</FirstLogonCommands>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value></Value>
<PlainText>true</PlainText>
</Password>
<DisplayName>Paul</DisplayName>
<Name>Paul</Name>
<Group>Administrators</Group>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
</component>
</settings>
</unattend>

In this example I created 4 batch files:

SPTDinst_x86.cmd


@echo off
echo.
if not exist "%SystemDrive%\Windows\SysWOW64" set Arch0=x86 && goto :Cpu86
if exist "%SystemDrive%\Windows\SysWOW64" goto :exit
echo.
:Cpu86
cmd /c %SystemDrive%\Install\Apps\Daemon\86\SPTDinst-x86.exe add /q
:exit

SPTDinst_x64.cmd


@echo off
echo.
if exist "%SystemDrive%\Windows\SysWOW64" set Arch9=AMD64 && goto :Cpu64
:Cpu64
cmd /c %SystemDrive%\Install\Apps\Daemon\64\SPTDinst-x64.exe add /q
:exit

FirstLog_x86.cmd


@echo off
echo.
if not exist "%SystemDrive%\Windows\SysWOW64" set Arch0=x86 && goto :Cpu86
if exist "%SystemDrive%\Windows\SysWOW64" goto :exit
:Cpu86
cmd /c for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\wpi\wpi.exe start %%i:\wpi\wpi.exe
:exit

FirstLog_x64.cmd


@echo off
echo.
if exist "%SystemDrive%\Windows\SysWOW64" set Arch9=AMD64 && goto :Cpu64
:Cpu64
cmd /c for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\wpi\wpi.exe start %%i:\wpi\wpi.exe
:exit

*Edit: SetProductKey.rar updated with this new example and the batch files as examples. You can adapt the batch files to your needs!

Edited January 21, 2012 by myselfidem

crashfly · December 4, 2011

@myselfidem - It would seem to me that if all of those batch files are being run (no matter which OS [x86 or x64]), then your x64 batch files need to be "reworked" just a bit. Just to remove the "excess", the command 'goto :Cpu64' can be dropped as the next label is the appropriate one to jump to. Alternatively, the next command after the 'if' command on the x64 batch files should be 'goto :exit'.

myselfidem · December 4, 2011

Yes, I think we can improve this batch file!

Or, we can also do like this:


@echo off
echo.
if exist "%SystemDrive%\Windows\SysWOW64" set Arch9=AMD64 && goto :Cpu64
if not exist "%SystemDrive%\Windows\SysWOW64" goto :exit
echo.
:Cpu64
cmd /c for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\wpi\wpi.exe start %%i:\wpi\wpi.exe
echo.
:exit

Could you show here your example, please? Thanks

Edited December 4, 2011 by myselfidem

crashfly · December 6, 2011

You can easily combine your batch files down to two. I am not sure why you are setting an environment variable to the architecture, but those can easily be combined.

SPTDinst.cmd (Combined)


@echo off
if exist "%SystemDrive%\Windows\SysWOW64"  goto :Cpu64
set Arch0=x86
cmd /c %SystemDrive%\Install\Apps\Daemon\86\SPTDinst-x86.exe add /q
goto :exit
:Cpu64
set Arch9=AMD64
cmd /c %SystemDrive%\Install\Apps\Daemon\64\SPTDinst-x64.exe add /q
:exit

FirstLog.cmd (Combined)


@echo off
if exist "%SystemDrive%\Windows\SysWOW64"  goto :Cpu64
set Arch0=x86
REM ## Put more x86 type setups here
goto :exit
:Cpu64
set Arch9=AMD64
REM ## Put more x64 type setups here
:exit
cmd /c for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\wpi\wpi.exe start %%i:\wpi\wpi.exe

It just seems kind of redundant to have two similar batch files for each OS. Combining allows to use one to cover both types.

myselfidem · December 6, 2011

Thanks!

Already tested...but unfortunatly doesn't work, because all passes are proceded and the batch files will be launched two times: for x86 and amd64 passes.

Even if the batch is correct with this particular Autounattend.xml file, the best method is to create different batch files for each architecture, like shown with my example above.

However may works for 32-bit selected Editions, but not for 64-bit selected Editions and the installation fails!

https://skydrive.liv...98&sc=documents

Edited December 6, 2011 by myselfidem

ar_seven_am · December 6, 2011

Thanks!
Already tested...but unfortunatly doesn't work, because all passes are proceded and the batch files will be launched two times: for x86 and amd64 passes.
Even if the batch is correct with this particular Autounattend.xml file, the best method is to create different batch files for each architecture, like shown with my example above.
However may works for 32-bit selected Editions, but not for 64-bit selected Editions and the installation fails!
https://skydrive.liv...98&sc=documents

u set that in WPI, but what crashfly mention is in "specialize" or "OOBE" which doesn't need additional "Post Installation" there.

also I still dont get why do u mention the command where my question is here :

myselfidem, you dont need to set 2 setting in "<settings pass="windowsPE">" becuz that only for boot.wim which we used only one (x86 boot.wim), if we do add x64 setting too, some automated task like "Accept EULA" will be asked again if we choose x64 image.
also I'm still tryin' to find out how to make custom menu so incase we need to repair our windows installation, we can still use our customized dvd (if we add autounattended setting there, it will skipped n directly to windows installation).

we used only one boot.wim (for x86, which the image contain 2 image name, it's "Microsoft Windows PE (x86)" in index 1, and "Microsoft Windows Setup (x86)" in index 2), now this setting :


    <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>0421:00000421</InputLocale>
		    <SystemLocale>id-ID</SystemLocale>
		    <UILanguage>en-US</UILanguage>
		    <UserLocale>id-ID</UserLocale>
	    </component>
	    <component name="Microsoft-Windows-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">
		    <ComplianceCheck>
			    <DisplayReport>Never</DisplayReport>
		    </ComplianceCheck>
		    <Diagnostics>
			    <OptIn>false</OptIn>
		    </Diagnostics>
		    <DiskConfiguration>
			    <WillShowUI>Always</WillShowUI>
		    </DiskConfiguration>
		    <DynamicUpdate>
			    <Enable>true</Enable>
			    <WillShowUI>OnError</WillShowUI>
		    </DynamicUpdate>
		    <UserData>
			    <ProductKey>
				    <Key>xxxxx-xxxxx-xxxxx-xxxxx-xxxxx</Key>
				    <WillShowUI>OnError</WillShowUI>
			    </ProductKey>
			    <AcceptEula>true</AcceptEula>
			    <FullName>User</FullName>
			    <Organization>MS USER</Organization>
		    </UserData>
	    </component>
    </settings>

it doesn't needed since we only used x86 boot.wim (in clean installation windows 7).

myselfidem · December 6, 2011

Feel free to remove these passes, if you want...

Yes it's about: <settings pass="specialize"> and <settings pass="oobeSystem">!

I have no errors even if I keep this passes with my Autounattend.xml file for 32-bit Editions or 64-bit Editions!

Edited December 6, 2011 by myselfidem

myselfidem · January 19, 2012

SetProductKey.rar updated with Autounattend.xml examples files improved!

Same download link at the first post. Enjoy.

nice_guy75 · January 20, 2012

Thanks mate, I have added your updated file in my account.

myselfidem · January 22, 2012

Thanks mate, and also many thanks to all the guys who appreciate this topic!

Regards

myselfidem · January 22, 2012

tried and it doesn't work.. i copied and pasted the text, renamed the txt to autounattend.xml, but when i try the image on a virtual machine, it gives me an error in line 4, column 200 or something... i try to open the file with xml editor but it doesn't open... with other unattended files you made no problems, just with mine..

Sorry it was my error, because when I copy/paste the Autounattend.xml files I haven't see the option to break the URL's inside the editor and when I post my files the lines with are writed twice and gives errors and the silent installation fails!

Example with error : http:// duplicated


<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="[url="http://schemas.microsoft.com/WMIConfig/2002/State"]http://schemas.microsoft.com/WMIConfig/2002/State[/url]" xmlns:xsi="[url="http://www.w3.org/2001/XMLSchema-instance"]http://www.w3.org/2001/XMLSchema-instance[/url]">

Correct example and URL's desactivated :


<component name="Microsoft-Windows-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">

Attach your Autounattend.xml file and I will see with WSIM!
The trouble is when the file is copied on notepad...On all Editors Forum the URL is writed twice!!!
Try this one and let me know!

Now this problem is solved and all my posts have been updated, because I use now the tab on the top editor to desactivate the url's inside the Autounattend.xml files!

Note: We must remember to save the file as UTF-8 format!

A new time, I apologize for this problem.

Edited January 22, 2012 by myselfidem

myselfidem · February 2, 2012

Some errors fixed inside the new SetProductKey.rar.

You can download the file at the first page of this topic, or on my SIG below !

Regards

Edited February 7, 2012 by myselfidem

myselfidem · February 7, 2012

SetProductKey.cmd updated !

Please, remove all previous dowloaded files and use the new SetProductKey.cmd!

Never stop the wimserv.exe inside a batch file or on your computer !

Regards

Escorpiom · June 9, 2012

Hello all,

I've made an Autounattend.xml for both x86 and amd64.

On x86 based systems it works perfect, but on x64 the earlier discussed problem with firstlogon.cmd appears.

I have set the command in the oobeSystem pass, and there is a section for both x86 and x64.

My firstlogon.cmd is the same for both x86 and x64, as it basically sets the RunOnceEx registry entries to do post install tasks.

In fact, the problem is that firstlogon.cmd executes twice, and that causes two separate RunOnceEx processes that do in fact the same thing.

This of course breaks the whole post install routine on x64 systems.

From reading this topic I understand it is because in x64 setup, the x86 section is also processed.

I understand what is happening, why it is happening but now, what would be the best way to deal with it?

- Just delete the firstlogon.cm instruction from the x64 section so it will only be processed once, by the x86 section;

- Move the x64 component before the x86 component;

- Maintain two unattended.xml files.

Over at MSFN I saw that bphlpt asked the same question,

http://www.msfn.org/board/topic/139572-ask-your-seven-xml-here/page__view__findpost__p__998530

he was referred to this thread but I only got more confused, because how about the other things like user account creation, will that also run twice?

I hope people can share their views on this issue.

Cheers.

myselfidem · June 9, 2012

I tested successfully using differents batch files for 32-bit and 64-bit architecture.

Firstlogon.cmd must be different depending on the architecture.

Have you tried like my example above:

http://www.wincert.net/forum/topic/9178-create-your-own-autounattendxml-all-in-one-x86amd64/page__st__40#entry79903

bphlpt · June 9, 2012

The key is that for myselfidem's cmd batch files SPTDinst_x86.cmd and FirstLog_x86.cmd, or whatever you use that is called from the "RunSynchronousCommand" and/or "FirstLogonCommand" sections, are skipped if it is determined that this is a 64bit OS. Those extra exit points are not needed in either SPTDinst_x64.cmd or FirstLog_x64.cmd since those will only be called in a 64bit OS. myselfidem uses a test for the existence of "%SystemDrive%\Windows\SysWOW64" to determine the bit-ness of the OS. You might want to check out this thread - http://www.ryanvm.ne...opic.php?t=9672 for a more detailed discussion of this particular problem. If you find the "improved" method mentioned there suits your needs then the part of myselfidem's batches that currently reads:

if not exist "%SystemDrive%\Windows\SysWOW64" set Arch0=x86 && goto :Cpu86
if exist "%SystemDrive%\Windows\SysWOW64" goto :exit

could be changed to:

if not exist "%SystemRoot%\SysWOW64\cmd.exe" (
	if not defined PROCESSOR_ARCHITEW6432 set Arch0=x86 && goto :Cpu86
)
goto :exit

Note that the variables Arch0 and Arch9 in the batch files must be used elsewhere in myselfidem's batches. You might not need them. But with an understanding of the concept you should be able to modify the batches for your needs.

Read both myselfidem's reference and the one that I gave carefully and consider your personal circumstances to decide on a course of action. Then test carefully in a VM before trying it on actual hardware. Please let us know how it goes and share your final solution if you feel it would be of benefit to anyone.

Cheers and Regards

Edited June 9, 2012 by bphlpt

Sign In

Create your own Autounattend.xml All-In-One (x86/amd64)

Recommended Posts

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

myselfidem

myselfidem

myselfidem

Posted Images

Join the conversation