Information Technology Reference
In-Depth Information
10.
Select the capture boot image you created and follow the steps of the Windows
Deployment Services Image Capture Wizard to save the image.
NOTE
SAVING IMAGES LOCALLY
Ensure that you have sufficient room on the template computer to save a local copy of
the image you are capturing. You can automatically upload the image to your WDS server
as well, but you must always save a copy on a locally mounted drive. It can be a Server
Message Block (SMB) share from a network computer, as long as the share has an assigned
drive letter.
WDS enables you to add hardware-specific drivers to your deployment images and to allow
images to request a specific set of images from the available driver store. You can create driv-
er groups to host and organize collections of drivers. The initial configuration of WDS creates
a default driver group called “DriverGroup1”. You can use the Windows Deployment Services
console to add or remove driver groups, rename or duplicate driver groups, and modify the
properties of driver groups.
In addition to the Windows Deployment Services console, you can use the Windows
PowerShell *-WdsDriverPackage cmdlets to manage your drivers and driver packages. The
cmdlets available include these:
■
Add-WdsDriverPackage
Adds a driver package from the WDS driver store into a
driver group or injects it directly into a boot image.
■
Disable-WdsDriverPackage
Makes a driver package in the WDS driver store
unavailable to clients without removing it from the driver store.
■
Enable-WdsDriverPackage
Makes a driver package in the WDS driver store avail-
able to clients. Packages are enabled by default when added to the WDS driver store.
■
Get-WdsDriverPackage
Gets the properties of all the driver packages in the WDS
driver store, or the properties of a specific package if you specify the name or ID
(GUID) of the package.
■
Import-WdsDriverPackage
Imports a driver package into the WDS driver store and
optionally adds it to a driver group.
■
Remove-WdsDriverPackage
Removes a driver package from a WDS driver group,
or removes it from all driver groups and deletes it completely from the driver store.
The WDS Windows PowerShell cmdlets do not allow you to create or directly manage the
properties of driver groups. You can manipulate the contents of driver groups, but not create
new driver groups.
You can inject drivers into an existing image or virtual hard disk by using the
Add-WdsDriverPackage cmdlet. After you add a driver package to an existing image, WDS
