Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security & DevOps Insights

  • Home
  • About
  • Advertise With US
  • Contact
  • Reviews
  • Toggle search form
Home » Windows Server » WDS and DHCP Deployment Scenarios: Configure DHCP Options 60, 66, and 67

WDS and DHCP Deployment Scenarios: Configure DHCP Options 60, 66, and 67

Posted on 26/05/202001/09/2025 Christian By Christian No Comments on WDS and DHCP Deployment Scenarios: Configure DHCP Options 60, 66, and 67

DHCP refers to Dynamic Host Configuration Protocol. Basically, it’s a mechanism that assigns IP addresses to computers dynamically. DHCP is a role (service) running on a server machine in the network in order to assign dynamic IP addresses to hosts. For some information on BOOTP Vendor Extensions and DHCP Options, and for automatic IP Assignment. See the following guide Dynamic Host Configuration Protocol (DHCP). Here are some other vital links “how to install Dynamic Host Configuration Protocol on Windows Server 2019, and how to configure DHCP: Post-deployment of Dynamic Host Configuration Protocol“.

Windows Deployment Services (WDS) enables you to deploy Windows operating systems over the network, which means that you do not have to install each operating system directly from a CD or DVD.

You may also be interested in this guide “How to deploy Windows using ADK, MDT, and WDS“. In this article, you will learn about the WDS and DHCP Deployment Scenarios: Configure DHCP Options 60, 66, and 67.

Why do we need DHCP Options?

DHCP options enable administrators to specify additional DHCP parameters in the form of pre-defined, vendor-specific information that is stored in the options field of a DHCP message. When the DHCP message is sent to clients on the network, it provides vendor-specific configuration and service information.

WDS also supports unicast, multicast transmissions, and scheduled casting. By using multicast, we can send one image over the network to multiple computers. With scheduled casting, we can transfer images at a certain time or after a certain number of computers have contacted the WDS server. This way we can deploy our images at off-peak times. We can configure our WDS server to respond to clients in three different ways.

  • Not Respond: We can enable this if we don’t want the WDS to respond to client requests.
  • Respond to Known: In this method, Active Directory (AD) needs to be available. All devices should be able to contact WDS. This way we can prevent unknown computers from accessing WDS. For devices that are not part of the Domain, they can be pre-staged. By pre-staging our devices, we pre-create the computer account in AD with the relevant names, therefore when the pre-staged computer contacts WDS, it will supply its existing computer name and in this way the WDS server will allow the imaging process.
  • Respond to All: Any computer that requests the image from WDS will receive the image.
PXE Response

Configure DHCP Options

To configure the DHCP options, launch the DHCP Manager as shown below. From the Server Manager, there are two ways to launch this. Simply click on the Tool menu and Select Server Manager or right-click on the DHCP server node, on the server, it is installed. Click on DHCP Manager.

This will open the DHCP Console as shown below. Expand the DHCP server

Expand IPv4 and click on Server Option. Then, click on Configure Options

This will open the DHCP Server options as shown below

Note: The Server Option 60 was enabled by default on the screen above, see scenario one for more details. This is because you have your DHCP server and WDS running on the same host.

You may want to see these How to backup and restore a Windows DHCP Server via the DHCP Manager and PowerShell, Windows Deployment Services: How to setup and install WDS role, and how to fix “Can’t Sign In: Domain Unavailable & 169.254 IP Address Issue.

Scenario 1 – WDS and DHCP Deployment Scenarios

WDS and DHCP on the same server (Clients will find WDS through option 60 in DHCP): For us, this is enough since I have my WDS and DHCP on the same server. The reason it is selected by default.

Scenario 2 – WDS and DHCP Deployment Scenarios

WDS and DHCP in different subnets, you will need the clients to find WDS through Options 66 and 67 set in DHCP.

  • Option 66 tells the client the name of the WDS server.
  • Option 67 tells the client which file to boot from.

You may want to see this article for more information: No valid offer received: WDS PXE-E16 error when booting clients.

Scenario 3 – WDS and DHCP Deployment Scenarios

WDS and DHCP server on the same subnet but different servers: Here the clients will find the WDS by broadcast.

To get PXE working on a server that is running both DHCP and WDS you need to enable options 66 and 67. These settings will help your connecting clients to find the appropriate PXE server.

The setting is found in the DHCP configuration manager window.

  • Expand IPv4 and
  • Right-click and select Configure Options, and
  • Scroll down and select the following options below.
066 Boot Server Host Name
067 Bootfile Name

For Option 066 Boot Server Host Name

Enter the string value in the field for “066 Boot Server Host Name”. You can enter the FQDN of your server or the IP Address of the server in the string below.

For Option 067 Bootfile Name

Click on 067 Bootfile Name as shown below. Enter the string ” \smsboot\x64\wdsnbp.com” in the field. Click on Apply and if you have other settings to enter, click on apply otherwise click on OK.

Screenshot 2020 05 26 at 00.15.38
Screenshot 2020 05 26 at 00.27.29

Where is the BootFile Name located ” \smsboot\x64\wdsnbp.com”?

Navigate to the Remote Installation Folder location on the drives. The folder contains the boot images, install images, Windows Deployment Services Management Tool, and PXE Boots.

This drive MUST be NTFS formatted. See the image below for the location of the bootfile.

For how to configure Windows Deployment Services on Windows Server 2019” Now all the needed server options to support WDS has been successfully configured. I had to configure options 66 and 67 just to demonstrate how this works.

It does not apply to scenario 1. I only need option 60 as I have both my WDS and DHCP server on the same device.

Note: If you have WDS and DHCP on the same server. Clients will find WDS through option 60 in DHCP).

For this, we do not need our server to listen to options 67 and 66. This is why option 60 was selected by default. For this, you can see the WDS settings for DHCP below.

What happens when WDS and DNS are installed on the same server: DNS issues with WDS to resolve this.

I hope you found this blog post helpful. Now you have learned the various WDS and DHCP Deployment Scenarios: Configure DHCP Options 60, 66, and 67. If you have any questions, please let me know in the comment session.

5/5 - (1 vote)

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Windows Server Tags:DHCP, DHCP Boot option, DHCP Boot Options, DHCP Server, Dynamic Host Configuration Protocol, WDS, Windows Deployment Services, Windows Server 2016

Post navigation

Previous Post: Windows Package Manager: How to install applications using Chocolatey?
Next Post: What happens when WDS and DNS are installed on the same Windows Server? DNS issues with WDS

Related Posts

  • unnamed 2
    How to create a contact in Active Directory Windows Server
  • WDSMDT
    What are the differences between MDT and WDS Windows Server
  • telnet
    Could not open a connection to the host, on the port, connect failed Windows Server
  • screenshot 2020 04 17 at 17.09.01
    How to configure a remote Windows Server to Support Ansible Windows Server
  • Specifiy the right credential for adding a domain
    Specify user account name when adding a DC to an existing Forest Windows Server
  • Banner
    Enabling and Configuring WinRM via GPO Windows

More Related Articles

unnamed 2 How to create a contact in Active Directory Windows Server
WDSMDT What are the differences between MDT and WDS Windows Server
telnet Could not open a connection to the host, on the port, connect failed Windows Server
screenshot 2020 04 17 at 17.09.01 How to configure a remote Windows Server to Support Ansible Windows Server
Specifiy the right credential for adding a domain Specify user account name when adding a DC to an existing Forest Windows Server
Banner Enabling and Configuring WinRM via GPO Windows

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

sysadmin top30a

  • Building VPC
    Build a Scalable VPC for Your AWS Environment [Part 1] AWS/Azure/OpenShift
  • SQL Error
    Fix “the server was not found or was not accessible: Verify that the instance name is correct and that SQL Server is configured to allow remote connections” Oracle/MSSQL/MySQL
  • drivelock 1280x720 1
    The server could not be reached or validated: Timeout expired. The Time out expired prior to obtaining a connection from the pool Security | Vulnerability Scans and Assessment
  • BitLocker renamedevicefghjkl
    What are the effect of renaming an MBAM-Protected Computer Windows
  • screenshot 2020 05 11 at 20.03.56
    How to remove printers from HP Utility Mac
  • postgresql on windows
    Install PostgreSQL on Windows server as Veeam Database Engine Oracle/MSSQL/MySQL
  • Map and disconnect Virtual Disk in VMware Workstation
    Map and disconnect Virtual Disk in VMware Workstation Virtualization
  • S3 Bucket 1
    How to delete AWS S3 Bucket and Objects via  AWS CLI from Linux AWS/Azure/OpenShift

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,823 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

Active Directory AWS Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Server 2016

Copyright © 2025 TechDirectArchive

 

Loading Comments...
 

You must be logged in to post a comment.