How To Create Unattend Xml Windows 10
The original post is here, use it to setup a PE image to capture the WIM.
In windows 10 PE you capture the image using DISM.
Dism /Capture-Image /ImageFile:<path_to_image_file> /CaptureDir:<source_directory> /Name:<image_name>
Where path_to_image_file is where the image will be saved.
source_directory is the drive letter of the drive you will be capturing.
image_name is a short descriptor/name of the image.
Also be aware that as of version 1809 of the AIK, Microsoft has separated the PE installation environment from the AIK kit.
You will need to download it separately here. It's on the same page as the AIK download, look for the link there.
If you get any installation errors you can bring up command prompt via Shift + F10, run notepad.exe and locate the installation logs in the c:\%windir%\panther folder.
1903
For version 1903 use AIK version 1809, you will not be able to edit the autounattend with AIK 1903 and AIK 1809 is able to edit and use 1903 images.
Also for version 1903 make sure you populate the windows PE – Microsoft Windows Setup neutral – UserData – ProductKey – Key … some previous versions of Windows did not require this.
In Windows 10 version 1803 a new installation prompt has been added. As such in pass 7 oobeSystem, you need to add input locale Component which is located in amd64_Microsoft-Windows-International-Core_neutral.
One other thing that I have changed in the newer version of the Autounattend.xml is that the installer now formats the drive to boot as UEFI and the install.wim (Windows image) is located on my network. Custom wim files over 4GB will not fit on a FAT32 formatted flash drive, so your option is to format it as NTFS or put the image on the network. For complexity we will use the network method. As such because you are now grabbing the installation image of the network you may need to inject network drivers into the boot.wim image in the sources folder on the flash drive/installation media. This will allow the installation media to connect to the network and grab the windows installation image from a shared folder. Note that there are two images in the boot.wim file, index 1 and index 2, you want to inject the network drivers into the index 2 in the image file which is the Microsoft Windows Setup image.
C:\>dism /Get-ImageInfo /ImageFile:c:\temp\bootwim\boot.wim Deployment Image Servicing and Management tool Version: 10.0.17134.1 Details for image : c:\temp\bootwim\boot.wim Index : 1 Name : Microsoft Windows PE (x64) Description : Microsoft Windows PE (x64) Size : 1,394,055,012 bytes Index : 2 Name : Microsoft Windows Setup (x64) Description : Microsoft Windows Setup (x64) Size : 1,553,327,748 bytes The operation completed successfully.
DISM GUI no longer seems to support the latest version of Windows 10 either, so all DISM commands need to be performed from the Deployment and Imaging Tools Environment.
Mount the boot.wim and perform the following commands to add the network driver(s) to your image. Note in the above example that the image is 64 bit so only 64 drivers are required for your hardware.
C:\>dism /Mount-Image /ImageFile:c:\temp\bootwim\boot.wim /Index:2 /MountDir:c:\temp\mount Deployment Image Servicing and Management tool Version: 10.0.17134.1 Mounting image [==========================100.0%==========================] The operation completed successfully. C:\>dism /Image:c:\temp\mount /Add-Driver:c:\temp\drivers\64 /Recurse Deployment Image Servicing and Management tool Version: 10.0.17134.1 Image Version: 10.0.14393.350 Searching for driver packages to install... Found 1 driver package(s) to install. Installing 1 of 1 - oem1.inf: The driver package was successfully installed. The operation completed successfully. C:\>dism /Unmount-Image /MountDir:c:\temp\mount /Commit Deployment Image Servicing and Management tool Version: 10.0.17134.1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully.
As you can see they are 3 simple commands and with the Recurse switch you can add multiple network drivers to the image if you have varying pieces of hardware deployed on your network.
Below is an example of an UEFI Autounattend.xml used to install windows from the network.
- In pass 1, windowsPE, the Autounattend.xml, formats 2 drives in the machine, a primary one and a secondary one.
- Also in pass 1 the image is then installed from a network location using domain credentials. You need to make sure the account has read permissions to the network location. The image is installed to disk "0" partition "4".
- In the specialize pass, pass 4, the machine is added to the domain using the "joinadmin" account using the Microsoft-Windows-UnattendedJoin component.
- Finally in version 1803 of windows maybe even 1709 a new installation component was added that asks for Network and Locale information, you can fill this in using the Microsoft-Windows-International-Core component in pass 7
My suggestion would be to copy and paste the below text into a blank text file and save it as an .xml extension. Then take that and open it in Windows System Image manager.
<?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> <UserLocale>en-CA</UserLocale> <UILanguageFallback>en-CA</UILanguageFallback> <SystemLocale>en-US</SystemLocale> <InputLocale>en-US</InputLocale> <UILanguage>en-US</UILanguage> </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"> <DiskConfiguration> <Disk wcm:action="add"> <CreatePartitions> <CreatePartition wcm:action="add"> <Order>1</Order> <Type>Primary</Type> <Size>250</Size> </CreatePartition> <CreatePartition wcm:action="add"> <Order>2</Order> <Type>EFI</Type> <Size>100</Size> </CreatePartition> <CreatePartition wcm:action="add"> <Order>3</Order> <Size>128</Size> <Type>MSR</Type> </CreatePartition> <CreatePartition wcm:action="add"> <Order>4</Order> <Extend>true</Extend> <Type>Primary</Type> </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Order>1</Order> <PartitionID>1</PartitionID> <Format>NTFS</Format> <Label>Recovery</Label> <TypeID>de94bba4-06d1-4d40-a16a-bfd50179d6ac</TypeID> </ModifyPartition> <ModifyPartition wcm:action="add"> <Order>2</Order> <PartitionID>2</PartitionID> <Label>System</Label> <Format>FAT32</Format> </ModifyPartition> <ModifyPartition wcm:action="add"> <Order>3</Order> <PartitionID>4</PartitionID> <Label>SOCO</Label> <Format>NTFS</Format> <Letter>C</Letter> </ModifyPartition> </ModifyPartitions> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> </Disk> <WillShowUI>OnError</WillShowUI> <Disk wcm:action="add"> <CreatePartitions> <CreatePartition wcm:action="add"> <Extend>true</Extend> <Order>1</Order> <Type>Primary</Type> </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Label>Storage</Label> <Format>NTFS</Format> <Order>1</Order> <Letter>D</Letter> <PartitionID>1</PartitionID> </ModifyPartition> </ModifyPartitions> <DiskID>1</DiskID> <WillWipeDisk>true</WillWipeDisk> </Disk> </DiskConfiguration> <UserData> <ProductKey> <WillShowUI>Never</WillShowUI> </ProductKey> <AcceptEula>true</AcceptEula> <Organization>Some Company</Organization> <FullName>Some Company Inc.</FullName> </UserData> <EnableFirewall>false</EnableFirewall> <EnableNetwork>true</EnableNetwork> <ImageInstall> <OSImage> <InstallTo> <DiskID>0</DiskID> <PartitionID>4</PartitionID> </InstallTo> <InstallFrom> <Path>\\server\IT\WIM\Win10-image.wim</Path> <Credentials> <Domain>domain.local</Domain> <Password>MyP@ssw0rd!</Password> <Username>netadmin</Username> </Credentials> <MetaData wcm:action="add"> <Key>/IMAGE/NAME</Key> <Value>Windows 10 Pro</Value> </MetaData> </InstallFrom> <WillShowUI>OnError</WillShowUI> </OSImage> </ImageInstall> </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"> <BluetoothTaskbarIconEnabled>true</BluetoothTaskbarIconEnabled> <ComputerName>DTPC-0032</ComputerName> <TimeZone>Mountain Standard Time</TimeZone> <ShowPowerButtonOnStartScreen>true</ShowPowerButtonOnStartScreen> <RegisteredOrganization>Some Company</RegisteredOrganization> <ProductKey>VK7JG-NPHTM-C97JM-9MPGT-3V66T</ProductKey> <DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet> <DoNotCleanTaskBar>true</DoNotCleanTaskBar> <RegisteredOwner></RegisteredOwner> <OEMName></OEMName> </component> <component name="Microsoft-Windows-UnattendedJoin" 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"> <Identification> <Credentials> <Domain>domain.local</Domain> <Username>joinadmin</Username> <Password>MyP@ssw0rd!</Password> </Credentials> <JoinDomain>domain.local</JoinDomain> <MachineObjectOU>OU=DesktopOU,OU=ComputersOU,DC=domain,DC=local</MachineObjectOU> </Identification> </component> </settings> <settings pass="oobeSystem"> <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> <VMModeOptimizations> <SkipWinREInitialization>true</SkipWinREInitialization> <SkipNotifyUILanguageChange>true</SkipNotifyUILanguageChange> <SkipAdministratorProfileRemoval>true</SkipAdministratorProfileRemoval> </VMModeOptimizations> <HideEULAPage>true</HideEULAPage> <HideLocalAccountScreen>true</HideLocalAccountScreen> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <ProtectYourPC>2</ProtectYourPC> <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen> <HideOnlineAccountScreens>true</HideOnlineAccountScreens> </OOBE> <UserAccounts> <LocalAccounts> <LocalAccount wcm:action="add"> <Password> <Value>BAAcwADAAcgBCEAUAAcwG8Ak=</Value> <PlainText>false</PlainText> </Password> <Description>Local User Account</Description> <DisplayName>LocalUser</DisplayName> <Group>Administrators</Group> <Name>User</Name> </LocalAccount> </LocalAccounts> </UserAccounts> <TimeZone>Mountain Standard Time</TimeZone> <RegisteredOrganization>Some Company</RegisteredOrganization> <RegisteredOwner>IT Department</RegisteredOwner> </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>en-US</InputLocale> <SystemLocale>en-CA</SystemLocale> <UILanguage>en-US</UILanguage> <UILanguageFallback>en-CA</UILanguageFallback> <UserLocale>en-CA</UserLocale> </component> </settings> <cpi:offlineImage cpi:source="wim:d:/iso/install_w10_1803.wim#Windows 10 Pro" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>
How To Create Unattend Xml Windows 10
Source: https://nerddrivel.com/2018/09/10/windows-10-1803-uefi-autounattend-xml-network-installation/
Posted by: singletonbectinced.blogspot.com
0 Response to "How To Create Unattend Xml Windows 10"
Post a Comment