Using DISM to inject Windows Drivers post imaging
Article ID: 268164
Updated On:
Products
Issue/Introduction
Is it possible to inject/install Windows drivers with Ghost Solution Suite or Deployment Solution post Imaging without DeployAnywhere?
Environment
DeployAnywhere
Used with:
Deployment Solution 8.x
Ghost Solution Suite 3.x
Cause
When deploying an image that doesn't contain critical Windows drivers needed for destination hardware, there are methods to inject drivers post imaging without using DeployAnywhere. Alternate methods may be preferred or required if DeployAnywhere fails to identify, inject, or install the driver.
Resolution
There may be several ways to accomplish driver injection/installation without using DeployAnywhere and most include custom processes which are outside the scope of Technical Support.
However, we have been able to successfully accomplish driver injection/installation using DISM with 'Copy File' and 'Run Script' tasks while in WinPE after a 'Deploy Image' task completes.
Here is an example of the process used in Deployment Solution. Please note: drive letters and commands may differ by image and environment. This is a reference example and should not be used without verification, testing, and an understanding of the process. Broadcom Technical Support does not assist in customizations.
Create a new client job and add appropriate 'Boot to' and 'Deploy Image' tasks.
In the 'Deploy Image' task, deselect 'Include DeployAnywhere for hardware independent imaging.'
Download the driver pack or individual critical drivers matching the serial number or service tag of the computer you are deploying an image to. For example, If you are deploying to a Dell machine, navigate to Dell's drivers and downloads site, enter the service tag for the machine you are deploying to and download the storage, and network drivers for the Windows version you are deploying. In some cases, a chipset driver may also be needed.
Zip up the downloaded drivers, then create a 'Copy File' task. Select 'Copy folder contents' and browse to the location of the zipped up critical drivers. Enter credentials to this location if required and set the 'Destination:' to 'c:\windows\drivers' (where 'c:' is the Windows installation volume as seen in WinPE)
NOTE: the volume letter 'c:' in 'c:\windows\drivers' may be identified as a different letter in the automation/WinPE environment. Substitute 'c:' with the drive/volume of Windows installation as seen in WinPE. Even if the Windows volume is known to be c: while booted to production, WinPE may list this as w: or another letter entirely. This can be verified in WinPE after imaging by opening the minimized command prompt and entering the following:
"diskpart"
"list volume" (note the letter associated with Windows production installation on the newly imaged machine)
"exit" (to exit diskpart)
Then create a 'Run Script' task to install the driver pack using DISM.
NOTE: the following example command uses letter c: for Windows OS installation volume as seen while booted to WinPE. This letter may be different depending on image and environment and should be verified directly in WinPE with diskpart commands (listed above):
Example DISM command: "dism.exe /image:c:\ /add-driver /driver:c:\windows\drivers /forceunsigned /recurse /quiet /norestart"
After this task completes we should be ready to boot to Windows and test the drivers. Finish the job sequence with a 'Boot To' task.
Ensure the computer boots to Windows and can connect to a network.
The same process can be achieved in Ghost Solution suite by using built in tasks 'Distribute Disk Image', 'Copy File to...' and 'Run Script...' .
Feedback
