Configuring and Starting WDS

Windows Deployment Services (WDS) is the successor to, and effectively replaces, Remote Installation Services (RIS). WDS offers enhanced capabilities for network-based OS deployment, including image-based deployments, scripting, and multicast capabilities.
Here is a more detailed explanation:

• RIS (Remote Installation Services): RIS was an older Microsoft technology used for remotely installing Windows operating systems on computers over a network. It allowed administrators to install Windows on computers from across the network with minimal user intervention.
• WDS (Windows Deployment Services): WDS emerged as the next-generation technology for remote OS deployment, built upon the foundation of RIS. WDS provides a more robust and feature-rich solution for deploying Windows operating systems, including Windows Vista and later, and Windows Server 2008 and later.
  • Image-based deployment: WDS uses disk imaging, specifically the Windows Imaging Format (WIM), to deploy operating systems.
  • Scripting and Multicasting: WDS allows for scripting and multicast deployments, offering more flexibility and efficiency in OS deployment.
  • Enhanced Control: WDS provides administrators with more control over the deployment process, including image selection, driver integration, and unattend files.
• Deprecation of WDS: While WDS is a powerful tool for OS deployment, Microsoft has partially deprecated some functionalities of WDS, especially regarding deploying Windows 11 using a boot.wim from installation media.
• Alternatives to WDS: If you're looking for a replacement for WDS, consider alternatives like Windows Assessment and Deployment Kit (WADK), Microsoft Deployment Toolkit (MDT), or System Center Configuration Manager (SCCM).

Windows Deployment Services (WDS) allows network-based installation of Windows operating systems. Below are the step-by-step instructions to install and configure WDS on Windows Server 2022.
Step 1: Install Windows Deployment Services (WDS) Role
Using Server Manager

1. Open Server Manager
   • Click Start → Server Manager.
2. Add Roles and Features
   • Click Manage → Add Roles and Features.
   • Select Role-based or Feature-based installation → Click Next.
3. Select the Server
   • Choose your server from the list → Click Next.
4. Select Server Roles
   • Check the box for Windows Deployment Services.
   • Click Add Features when prompted.
   • Click Next.
5. Select Role Services
   • Ensure both options are checked:
     • Deployment Server
     • Transport Server
   • Click Next.
6. Confirm and Install
   • Click Install.
   • Wait for the installation to complete, then click Close.

Step 2: Configure Windows Deployment Services

1. 1. Open WDS Console
   1. Open Server Manager → Click Tools → Windows Deployment Services.
2. 2. Initialize WDS
   1. In the left pane, expand Servers.
   2. Right-click your server name → Select Configure Server.
   3. On the Welcome screen, click Next.
   4. Choose Installation Mode:
      • If the server is joined to Active Directory, select Integrated with Active Directory.
      • If not, choose Standalone Mode.
3. 3. Select the Remote Installation Folder
   1. Choose a folder (e.g., D:\RemoteInstall).
   2. Click Next.
4. 4. Configure PXE Server Settings
   1. Choose how the WDS server responds to PXE client requests:
      • Respond to all client computers (known and unknown) (recommended for open environments).
      • Respond only to known client computers (requires pre-registered devices in AD).
   2. Click Next and finish the configuration.
5. 5. Start the WDS Service
   1. In the WDS Console, right-click the server and select Start.

Step 3: Add Boot and Install Images

1. 1. Add Boot Image
   1. Expand Servers → Right-click Boot Images → Select Add Boot Image.
   2. Browse to your Windows installation media (ISO/DVD) → Select sources\boot.wim.
   3. Name the image (e.g., Windows 11 Boot Image).
   4. Click Next → Finish.
2. 2. Add Install Image
   1. Expand Servers → Right-click Install Images → Select Add Install Image.
   2. Create an image group (e.g., Windows11Group) → Click Next.
   3. Browse to sources\install.wim from the Windows installation media.
   4. Select the editions you want to deploy → Click Next → Finish.

Step 4: Configure DHCP (if WDS and DHCP are on the Same Server)

1. Open DHCP Manager → Expand your scope.
2. Right-click Scope Options → Click Configure Options.
3. Set these options:
   • Option 66 (Boot Server Host Name) → Enter WDS Server IP Address.
   • Option 67 (Bootfile Name):
     • boot\x64\wdsnbp.com (for legacy BIOS).
     • boot\x64\wdsmgfw.efi (for UEFI).

Step 5: Deploy Windows via Network Boot (PXE)
Test WDS Deployment

1. Boot a client computer and enter the BIOS/UEFI.
2. Enable Network Boot (PXE Boot).
3. Restart the client and boot from the network.
4. The WDS boot menu should appear.
5. Select the Windows Image and proceed with the installation.

Summary

• Installed WDS using Server Manager
• Configured PXE Boot and Remote Installation Folder
• Added Boot and Install Images
• Configured DHCP (if needed)
• Tested PXE Boot and Windows Installation

Microsoft's approach to modern Windows deployment is shifting away from traditional imaging-based methods like WDS towards cloud-centric and automated solutions. Here are the key technologies that represent this shift:

• Windows Autopilot:
  • This is a cloud-based deployment technology that allows for the pre-configuration of new Windows devices.
  • Instead of deploying a full OS image, Autopilot leverages the existing Windows installation on the device and applies configurations and applications from the cloud.
  • This streamlines the deployment process and allows users to get up and running quickly.
• Microsoft Intune:
  • Intune is a cloud-based endpoint management solution that plays a crucial role in modern Windows deployment.
  • It enables organizations to manage and configure devices, deploy applications, and enforce security policies.
  • Autopilot works in conjunction with Intune to provide a comprehensive deployment and management solution.
• Microsoft Deployment Toolkit (MDT):
  • While not a direct "successor" in the sense of completely replacing WDS, MDT is a crucial tool in modern deployment workflows.
  • It's used to create customized Windows images and automate deployment tasks.
  • MDT is often used in conjunction with other technologies, including WDS and increasingly, with the movement to cloud based deployment, in conjunction with Intune.
• Windows Assessment and Deployment Kit (ADK):
  • The ADK is a collection of tools that are essential for Windows deployment.
  • It includes tools like DISM (Deployment Image Servicing and Management), which are used for image servicing and management.

Key trends:

• The shift is toward "modern deployment," which emphasizes cloud-based management and user self-provisioning.
• This approach reduces the need for traditional imaging and allows for more flexible and scalable deployments.

Therefore, while WDS still has its place in certain scenarios, Microsoft is clearly pushing towards a future where Autopilot and Intune are the primary deployment technologies.