Scribd
Upload
83 views36 pages

Windows Deployment Services (WDS) : Presented by - Ashwani Kumar - System Admin I (Windows Server) - 01 March 2023

Windows Deployment Services (WDS) allows administrators to remotely deploy Windows operating systems across a network. It provides the ability to set up new computers without having to directly install the OS on each one. The document reviews how to install and configure WDS, including adding a boot image, to enable network deployment of a base Macrium Deployment Kit image to new client computers on the network.

Uploaded by

Sakshi Gupta
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
83 views36 pages

Windows Deployment Services (WDS) : Presented by - Ashwani Kumar - System Admin I (Windows Server) - 01 March 2023

Windows Deployment Services (WDS) allows administrators to remotely deploy Windows operating systems across a network. It provides the ability to set up new computers without having to directly install the OS on each one. The document reviews how to install and configure WDS, including adding a boot image, to enable network deployment of a base Macrium Deployment Kit image to new client computers on the network.

Uploaded by

Sakshi Gupta
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 36

Windows Deployment

Services (WDS)
Presented by - Ashwani Kumar
- System Admin I (Windows Server)
- 01 March 2023
Topics
• Introductions to WDS
• About WDS
• Purpose
• Requirements
• Installations of WDS
• Configuration of WDS
• References
Introductions
• Windows Deployment Services is a server role that gives administrators the ability to
deploy Windows operating systems remotely.
• WDS can be used for network-based installations to set up new computers so
administrators do not have to directly install each operating system (OS).
• If an administrators is thinking of using WDS, Microsoft recommends having a good
understanding of common networking components and deployment technologies,
including Active Directory Domain Services, DNS and DHCP. Microsoft also recommends
that it may be helpful for administrators to have a good understanding of the Preboot
Execution Environment PXE.
• If a Windows Deployment Services server is running Windows Server 2012 R2, WDS can
be managed with PowerShell cmdlets. These cmdlets can help with specific tasks such as
cloning disk images, adding driver packages and disabling or enabling install and boot
images.
Purpose

• Windows Deployment Services (WDS) is the revised version of


Remote Installation Services (RIS). WDS enables the deployment of
Windows operating systems. You can use WDS to set up new clients
with a network-based installation without requiring that
administrators visit each computer or install directly from CD or DVD
media.
• Open Server Manager and select the Local Server
• Click on Manage, then select “Add Roles and Features”
• Select “Role-based or feature-based installation”. Click “Next” when done.
• Select the destination server. Click “Next” when done.
• Select “Windows Deployment Services” from the Roles list. Click “Next” when
done.
• To confirm the features that are required, click “Add Features”.
• Click “Next” on the Features list.
• Read through the notes for WDS installation and click “Next”
• Confirm the Role Services and click “Next”.
• One last chance to make changes. Confirm by clicking “Install”.
• Wait for the installation to complete and click “Close”
• In the search pane type “Windows deployment services” and click on the app
when it comes up.
• Now we begin the process of configuring WDS. Right click on your server and select “Configure Server”.

• Read through the information screen and click “Next”.


• Select “Standalone Server” and click “Next”.
Note: While you can select “Integrated with Active Directory”, that is beyond the scope of this document.
• Create a remote installation folder or use the default given. In this example, we’re using the default
“C:\RemoteInstall”. Click “Next”.
Note: If you select a folder on the same volume as your operating system, you’ll have a System Volume Warning pop up. Read
it and click “Yes” if you’re comfortable with moving forward, or pick another volume to store the Remote Install folder.
• For your PXE Initial Settings, please select “Respond to all client computers (known and unknown)”. Click
“Next”.
• Wait for the WDS initial configuration to complete.
• Click on “Finish” once the initial configuration is completed.
• There are still a few things to set up. Right click on your server again and this time select “Properties”.

• Go to the PX Response tab. If you need to make any changes for your environment, change it here. Otherwise, leave
the earlier selection of “Respond to all client computers (known and unknown)” as your choice.
• Select the “Boot” tab and change the PXE Boot Policy. For known clients (computers that have already been identified on
the network), select “Require the user to press the F12 key to continue the PXE boot”. This will allow known clients to
boot into their installed OS if you don’t interact with the keyboard within the time limit.

For unknown clients, select “Always continue the PXE boot”. This will ensure that new machines use PXE boot to get their
base Macrium Deployment Kit image.
• Now we need to add a boot image to the WDS server. Insert your Macrium Deployment Kit Technician’s USB stick (or
mount the ISO) to your server, and navigate to the sources folder. In this example, the USB stick is mounted as drive “D”,
so the path is “D:/Sources”. You’ll find the “boot.wim” boot image file there.

Right click on the “boot.wim” file and select “Copy”.


• Go to your desktop, right click and select “Paste”. You should see a copy of the “boot.wim” file on your desktop now.

• Go back to the WDS Console, expand your server, and right click on
“Boot Images”. Select “Add Boot Image”.
• Click “Browse” and go to your desktop. Double-click on the “boot.wim” file we copied over above.
• Confirm the path and click “Next”.
• Give the image a name and description. For this example, we used “Macrium Deployment Kit Recovery
Environment” as the Image Name, and “Microsoft Windows PE (amd64)” as the description. Click “Next”
when done.
• Review the final summary, and click “Next”.

• Wait for the operation to complete and


click “Finish”.
• Confirm the boot image by going back into the WDS Console, click on “Boot Images” and see your new
boot image in the right-hand pane.

•WDS is setup and ready, however you still need to ensure that PXE is enable on DHCP.
References:
• https://
learn.microsoft.com/en-us/previous-versions/windows/it-pro/windo
ws-server-2012-r2-and-2012/hh831764(v=ws.11)

• For information about getting started with Windows Deployment


Services, see
Windows Deployment Services Getting Started Guide for Windows Se
rver 2012
.

• For more information about Windows PowerShell cmdlets for WDS,


see Windows Deployment Services Cmdlets in Windows PowerShell.

You might also like