How to install the Windows Deployment Services role

How to install the Windows Deployment Services role

This article is designed to address installing the Windows Deployment Services (WDS) role on a server running Windows Server Core.

Perform the following steps to install the WDS role on a server running Windows Server Core.

1. Type Start PowerShell in the Command Prompt window to start Windows PowerShell.

2. Type Install-WindowsFeature WDS and press Enter to install the WDS role.

Additional Information:

This information applies to Windows Server 2012 and Windows Server 2012 R2.

The following Windows PowerShell cmdlets are available for managing WDS on a server running Windows Server Core.

Add-WdsDriverPackage - Adds an existing driver package to a driver group or injects it into a boot image.
Approve-WdsClient - Approves clients.
Copy-WdsInstallImage - Copies install images within an image group.
Deny-WdsClient - Denies approval for clients.
Disable-WdsBootImage - Disables a boot image.
Disable-WdsDriverPackage - Disables a driver package in the
WDS driver store.
Disable-WdsInstallImage - Disables an install image.
Disconnect-WdsMulticastClient - Disconnects a multicast client from a transmission or namespace.
Enable-WdsBootImage - Enables a boot image.
Enable-WdsDriverPackage - Enables a driver package in the
WDS driver store.
Enable-WdsInstallImage - Enables an install image.
Export-WdsBootImage - Exports an existing boot image from an image store.
Export-WdsInstallImage - Exports an existing install image from an image store.
Get-WdsBootImage - Gets properties of boot images from the image store.
Get-WdsClient - Gets client devices from the pending device database, or pre-staged devices from AD or the standalone server device database.
Get-WdsDriverPackage - Gets properties of driver packages from the WDS driver store.
Get-WdsInstallImage - Gets properties of install images from an image store.
Get-WdsInstallImageGroup - Gets properties of install image groups.
Get-WdsMulticastClient - Gets a list of clients connected to a multicast transmission or namespace.
Import-WdsBootImage - Imports a boot image to the image store.
Import-WdsDriverPackage - Imports a driver package into the WDS driver store.
Import-WdsInstallImage - Imports an install image to an image store.
New-WdsClient - Creates a pre-staged client.
New-WdsInstallImageGroup - Creates an install image group.
Remove-WdsBootImage - Removes a boot image from the image store.
Remove-WdsClient - Removes a pre-staged client from ADDS or the stand-alone server device database, or clears the Pending Devices database.
Remove-WdsDriverPackage - Removes a driver package from a driver group or removes it from all driver groups and deletes it.
Remove-WdsInstallImage - Removes an install image from an image store.
Remove-WdsInstallImageGroup - Removes an install image group.
Set-WdsBootImage - Modifies settings of a boot image.
Set-WdsClient - Modifies a pre-staged client device.
Set-WdsInstallImage - Modifies the properties of an install image.
Set-WdsInstallImageGroup - Modifies the name and access permissions of an install image group.

Additional information about Windows PowerShell cmdlets for WDS can be found on TechNet.

Quick Tips content is self-published by the Dell Support Professionals who resolve issues daily. In order to achieve a speedy publication, Quick Tips may represent only partial solutions or work-arounds that are still in development or pending further proof of successfully resolving an issue. As such Quick Tips have not been reviewed, validated or approved by Dell and should be used with appropriate caution. Dell shall not be liable for any loss, including but not limited to loss of data, loss of profit or loss of revenue, which customers may incur by following any procedure or advice set out in the Quick Tips.

Article ID: HOW10124

Last Date Modified: 08/28/2014 03:29 PM

Rate this article

Easy to understand
Was this article helpful?
Yes No
Send us feedback
Comments cannot contain these special characters: <>()\
Sorry, our feedback system is currently down. Please try again later.

Thank you for your feedback.