PSAutoDeploy is a PowerShell script used to build a simple deployment solution for Windows 10. The real benefit of this script is the driver injection process, which occurs after the Windows deployment, so that you can use a single generic image and leverage a driver repository, instead of having different images just due to device driver differences. With Windows 10 releasing twice per year, managing many model-specific images may not be the most efficient method of deployment.
Use DISM to add the following WinPE optional components;
WinPE-WMI
WinPE-Scripting
WinPE-NetFx
WinPE-PowerShell
WinPE-DismCmdlets
DISM commands to add the above required Optional Components.
Save the Windows 10 image to the deployment share. The image should be named install.wim or you will need to modify the PowerShell script to match your image name.
Example; Z:\Share\Images\x64\Install.wim
Copy INF device drivers to the distribution share into sub-folders named after the BIOS values as determined by WMIC. The folder should contain a folder for each device driver, separated into sub-folders based on the device names.
Note: DISM /Export-drivers command will automatically name the sub-folders for each driver when extracting them, so you only need to create the Manufacturer, Model, and OS architecture folders.
32-bit Driver Example;
Z:\Share\Drivers\Lenovo\G40\32-bit\
Z:\Share\Drivers\Lenovo\G40\32-bit\intelaud
Z:\Share\Drivers\Lenovo\G40\32-bit\igdlh32
etc... for each device in the PC needing drivers you wish to include
64-bit Driver Example;
Z:\Share\Drivers\Lenovo\G40\64-bit\
Z:\Share\Drivers\Lenovo\G40\64-bit\intelaud
Z:\Share\Drivers\Lenovo\G40\64-bit\igdlh64
etc... for each device in the PC needing drivers you wish to include
In order to setup driver files in the correct folder names, so that PSAutoDeploy.ps1 or other scripts like the driver injection script can find them, you need to run a few commands to see what the device manufacturer has entered into the BIOS or UEFI tables, for each device. This can be done rather easily using PowerShell and WMIC from within a running Windows installation by running the following commands;
Get the BIOS Value for System Manufacturer using PowerShell
$SysManufacturer = (Get-WmiObject -Class:Win32_ComputerSystem).Manufacturer; Write-Host "PC Manufacturer: " -NoNewline; Write-Host "$SysManufacturer"`Get the BIOS Value for System Model using PowerShell
$SysModel = (Get-WmiObject -Class:Win32_ComputerSystem).Model; Write-Host "PC Model: " -NoNewline; Write-Host "$SysModel"Get the Value for OS Architecture using PowerShell
$OSArch = (Get-WmiObject Win32_OperatingSystem).OSArchitecture; Write-Host "OS Architecture: " -NoNewline; Write-Host "$OSArch"Note: You can also run these same commands from within WinPE, but the WinPE will need to have the optional components added so that it supports running PowerShell and WMI queries. More details and example script can be found here: https://github.com/HaroldMitts/Build-CustomPE
This demo shows a virtual machine booting from Windows PE, installing Windows 10 using PSAutoDeploy.ps1, and the Driver Injection solution as described in this repository.