> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/2pxe-server/4.0/configuration/dhcp-configuration/using-dhcp-scope-options.md).

# Using DHCP Scope Options

DHCP scope options provide PXE clients with the information they need to locate the 2PXE server and download the correct network boot file. This approach is useful when you cannot, or do not want to, configure IP Helpers on your network routers.

Unlike IP Helpers, DHCP scope options require changes to the DHCP server configuration. The DHCP server must provide the 2PXE server address, the correct boot file for the client's firmware architecture, and the HTTPS URL that the iPXE loader uses to communicate with 2PXE.

## How DHCP scope options are used

During a network boot, the client sends a DHCP request that identifies it as a PXE-capable device. The DHCP server uses the request and its configured policies to return the boot information.

The main DHCP options used for this configuration are:

| DHCP option                             | Microsoft DHCP field | Purpose                                                                                                                                         | Example                              |
| --------------------------------------- | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------ |
| **66 – TFTP Server Name / Next Server** | Next-Server (SIADDR) | Provides the IP address of the 2PXE server for the initial boot file download.                                                                  | `192.168.10.30`                      |
| **67 – Bootfile Name**                  | Filename             | Specifies the boot file. The value must match the client's firmware architecture.                                                               | See the architecture examples below. |
| **175 – 2PXE URL**                      | Option 175           | Provides the HTTPS URL that the iPXE loader uses to communicate with 2PXE.                                                                      | `https://pxe01.example.com:8050/`    |
| **60 – PXEClient**                      | Option 60            | Identifies the PXE client/vendor class for DHCP PXE handling and policy matching. It may be required when DHCP and 2PXE run on the same server. | `PXEClient`                          |

### Selecting the boot file (Option 67)

The boot file must match the client's firmware architecture. Typical examples are:

| Client firmware    | Boot file                    |
| ------------------ | ---------------------------- |
| BIOS (x86 and x64) | `Boot\\x86\\undionly.kpxe`   |
| UEFI x64           | `Boot\\x64\\snponly_x64.efi` |
| UEFI x86           | `Boot\\x86\\snponly_x86.efi` |

Other architectures, such as ARM64 UEFI, may require a different boot file. Configure DHCP policies or equivalent logic so that clients receive the correct value for their architecture. The exact path must also match the boot files available in your 2PXE installation.

### Configuring the 2PXE URL (Option 175)

Option 175 provides the HTTPS URL that iPXE uses to establish communication with the 2PXE service. Because this communication uses HTTPS, the URL must match the 2PXE server's HTTPS host name.

{% hint style="warning" %}
**Important:** Use the server FQDN in lowercase, spell it correctly, include the correct port, and add a trailing slash.

For example:

`https://pxe01.example.com:8050/`
{% endhint %}

### Option 60 considerations

Option 60 is used for PXE identification and DHCP policy matching. When the DHCP server and 2PXE run on the same server, the DHCP response may also need Option 60 set to `PXEClient`. Whether this is required depends on how DHCP and 2PXE are deployed and configured.

## Configure DHCP scope options

Follow the [Configuring DHCP Scope Options](/2pxe-server/4.0/configuration/dhcp-configuration/configuring-dhcp-scope-options.md) guide to configure Microsoft DHCP Server. It includes two alternatives for creating the required vendor classes: PowerShell or the DHCP management console. The remaining DHCP options and policies are configured in the same way regardless of which method you choose.

For an explanation of the alternative IP Helpers approach, see [DHCP Configuration](/2pxe-server/4.0/configuration/dhcp-configuration.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.2pintsoftware.com/2pxe-server/4.0/configuration/dhcp-configuration/using-dhcp-scope-options.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.