Here’s a step-by-step guide on configuring WDS on Windows Server

-

Windows Deployment Services (WDS) is a Microsoft tool for network-based installation of Windows operating systems. It enables administrators to deploy Windows images over a network to computers without requiring physical media. Here’s a step-by-step guide on configuring WDS on Windows Server:

Prerequisites:

  1. A Windows Server machine with WDS role installed.
  2. Active Directory, DNS, and DHCP set up and running on the network.
  3. An NTFS partition on the server to store images.

Step 1: Install WDS Role

  1. Open Server Manager and go to Manage > Add Roles and Features.
  2. Click Next until you reach the Server Roles page.
  3. Select Windows Deployment Services and click Next.
  4. Choose WDS Deployment Server and WDS Transport Server and click Next.
  5. Complete the wizard to install the role, then restart the server if prompted.

Step 2: Configure Windows Deployment Services

  1. Open WDS by navigating to Server Manager > Tools > Windows Deployment Services.
  2. In the WDS console, right-click on your server name and select Configure Server.
  3. Follow the wizard:
    • Choose Integrated with Active Directory if you’re in an Active Directory environment.
    • Select the Remote Installation Folder Location (this should be an NTFS partition).
    • Choose whether to respond to all clients or only known clients (clients registered in Active Directory).
  4. Finish the setup.

Step 3: Add a Boot Image

  1. In the WDS console, expand your server, right-click on Boot Images, and select Add Boot Image.
  2. Navigate to the boot.wim file, typically located on the Windows installation media under sources.
  3. Follow the wizard to add the boot image.
  4. Give the image a name, such as "Windows Setup (x64)".
  5. Complete the wizard.

Step 4: Add an Install Image

  1. In the WDS console, expand your server, right-click on Install Images, and select Add Install Image.
  2. Create a new Image Group (for example, "Windows 10 Images").
  3. Browse to the install.wim file on your Windows installation media (usually in the sources folder).
  4. Select the edition(s) of Windows you wish to add and complete the wizard.

Step 5: Configure DHCP Options

If DHCP and WDS are on the same server:

  1. Open DHCP console, navigate to Scope Options, and add the following options:
    • Option 66: Set to the IP address of the WDS server.
    • Option 67: Set to boot\x64\wdsmgfw.efi (for UEFI clients) or boot\x86\wdsnbp.com (for BIOS clients).

Step 6: Configure WDS to Respond to PXE Requests

  1. Go back to the WDS Console, right-click your server, and choose Properties.
  2. In the PXE Response tab:
    • Set your server to respond to PXE requests as required (e.g., respond to all clients or only known clients).
  3. Optional: Set up PXE boot policy to determine which types of devices are allowed to connect.

Step 7: Test Deployment

  1. Connect a client machine to the network, and make sure it’s set to boot from the network (PXE boot).
  2. Restart the client, and it should boot into WDS.
  3. Select the desired boot and install images to deploy the operating system.

This configuration should enable you to deploy Windows images to network-connected devices with WDS.

Comments

Post a Comment

Popular posts from this blog

IIS Installation and Application configuration windows swerver

-
Image
  1.      Using the Server Manager, select  2 Add roles and features . Figure 4-9 Server Manager – Adding Roles and Features Select  Role-based or feature-based installation , and then click  Next . Choose  Select a server from the server pool . 4.      Select the server you are configuring, and then click  Next . Figure 4-10 Server Manager – Select Server 5.      Expand the  Web Server  role service. Figure 4-11 Server Manager – Web Server Role Services Expand the  Web Server  options and select the following  Common HTTP Features : ·         Default Document ·         ·         HTTP Errors ·         ·         Static Content · ...
Read more

IIS Self Signed

-
Image
  Securing the server with SSL Now we want to secure the cats by adding a SSL certificate to our Server. In your IIS Manager go to your server (The top of the tree to the left)  ➜  Scroll down and double-click Server Certificates. (If your self-signed certificate is already here, jump ahead to the bindings steps) We need to import our self-signed server certificate in order to enable https communication with SSL, so click Import… Click the … and find your .pfx file, fill out the password (the -po parameter in your command batch file) and click OK Your certificate is now added Double-click the newly added cert to verify that it is trusted (Your self-signed certificates were added to the correct stores in my previous post, so again: read it if you are lost right now ;-)) So far, so good! Now we can add the https binding, the same way as before but choose https with port 443, your domain as the host name and find yourself signed certificate in the drop do...
Read more