In the previous post we chose Windows 10 1709 here’s the reason why.
To prepare a VM we use a script named "Convert-WindowsImage.PS1" . This script does not work with the current setup media. The reason for this is the change in structure of the disk image. Before Windows 10 1803 the Operating System itself was contained by a WIM file. Starting with Windows 10 1803 all deployment streams share the same ESD file. This breaks the current version of the script. If the 1709 is fine for you, the script will do a great job. Detail for 1803 is contained further on in this blog
This script is a function which means you have to pre-load it to run it. You can do this in 2 ways either
Then use the following command to create the VHD: Convert-WindowsImage -SourcePath ".\en_windows_10_multi-edition_vl_version_1709_updated_dec_2017_x64_dvd_100090741.iso" -VHDPath '.\AppVAutosequencer.vhd' -VHDPartitionStyle "MBR" -VHDFormat "VHD" -SKU "Education" (-SKU since this example uses multi-edition, so you have to specify one)
Depending on the performance of your system, this process will take approximately 10 minutes . Result will be a VHD file containing a clean Windows 10 setup ready to run.
For versions newer than 1709 OS you'll need to create a own virtual machine, install Windows 10 and successfully execute a Sysprep. The result will be similar to the result shown before.
Create the Virtual Machine
After manually creating or using the Convert-WindowsImage script you're ready to finally prepare the Virtual Machine for sequencing:
Use the following PowerShell command on your newly created VHD. New-AppVSequencerVM -VMName "AppVSequencerVM" -ADKPath ".\Windows10ADK" -VHDPath ".\AppVAutosequencer.vhd" -VMMemory "2048" -VMSwitch "Internal"
VMName should not contain spaces or other unsupported special character
During OOBE the VMName is used by the OOBE Template to create the Hostname of the VM as shown below:
The Unattend.xml is stored in "C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\AutoSequencer\Unattend_Sequencer_User_Setup_Template.xml" if further customizations are needed.
VMMemory Switch does not work for Windows 10 1709 - just apply the desired memory configuration in the Hyper-V Manger/Settings for the VM, and remove it from the command
The ADKPath must match of the path used to install the ADK on the Host machine.
To avoid errors, execute Enable-PSRemoting on the Host machine
After this step you're ready to proceed into the next step. We'll cover this in the next post.
Johannes Freundorfer, Ingmar Oosterhoff and Matthias Herfurth