Skip to content
INSIGHTS & GUIDES · NETCLOUD24

Giving device classes the right DHCP settings

Give verified device classes the DHCP options they need. Build explicit matching conditions, review address allocation and test both intended devices and ordinary clients before relying on the policy.

Read the article ↓
Editorial illustration: How to Create DHCP Policies for Device Classes

Printers, phones and ordinary workstations may share a subnet while needing different DHCP options or address handling. A DHCP policy can select clients from supported request characteristics and apply a reviewed configuration. It should be designed from what devices actually send, not from a friendly label invented by an administrator.

For managed networks, Netcloud24 prepares the agreed DHCP arrangement and coordinates changes with the network owner. Customers describe the device requirements and impact; individual users should not change server scopes to make one device connect.

Identify the device signal and its limitations

Determine whether the intended devices provide a vendor class, user class, client identifier or another supported characteristic. Capture or inspect that information through authorised diagnostics and vendor documentation. A manufacturer's name on the case does not prove the exact DHCP class string.

DHCP identifiers are not strong device authentication. Clients can imitate some fields, and MAC randomisation or replacement hardware can change others. Do not use a policy match as the sole security boundary for a privileged network.

Record positive and negative test devices, their current leases and normal option values. Include a device that must remain on the ordinary scope behaviour. Without that control, a policy that accidentally matches everyone can appear successful.

Review the scope before adding rules

Get-DhcpServerv4Scope
Get-DhcpServerv4Policy -ScopeId 192.0.2.0
Get-DhcpServerv4Class
Get-DhcpServerv4OptionValue -ScopeId 192.0.2.0

The subnet is a documentation example. Use the real approved scope and server context. Check existing server-level and scope-level policy, reservations, exclusions, utilisation and failover arrangements before choosing an order or address range.

Understand where options currently originate. Server, scope, policy and reservation configuration can interact. A device receiving a surprising DNS server may already have a more specific assignment elsewhere.

Preserve a current supported backup and a lease-aware configuration export. If a policy will change address allocation, rollback must consider leases issued under the new arrangement rather than just deletion of the policy object.

Define the class and processing logic

Register a vendor or user class through the DHCP management workflow where the chosen policy requires one. Its data must correspond to the client's actual request. A class must exist before it is referenced in the relevant condition.

Choose AND or OR according to the intended condition. Combining a vendor class and a MAC criterion with OR is much broader than requiring both. Explain the logic in the change record using ordinary language before expressing it in the wizard.

Set processing order deliberately among existing policies and test overlapping conditions. Avoid assuming the newest item automatically has the intended priority. Keep policy names tied to purpose and ownership rather than a vague “Special devices” label.

Create a disabled pilot

The example below references an already defined illustrative vendor class. Replace the class and scope only after validation:

Add-DhcpServerv4Policy -Name 'PrintDevices-Pilot' `
 -ScopeId 192.0.2.0 -Condition OR `
 -VendorClass EQ,'ManagedPrintClass' `
 -ProcessingOrder 1 -Enabled $false -PassThru

Inspect the resulting condition before activation. Do not copy an arbitrary prefix from a vendor example and assume it identifies every device you own. Some models or firmware versions can send different values.

Configure only required policy options through the supported console or cmdlets. A default gateway, DNS server or vendor option has different consequences; changing all of them to prove a match makes the cause of any failure harder to identify.

Plan address ranges without overlap

If the policy assigns a specific range, verify that it lies within the intended scope and fits the existing exclusions, reservations and other policy allocations. Size it for expected growth and temporary replacements, not merely the number currently online.

A policy-specific pool can exhaust while the ordinary scope still has space, creating a failure limited to one device class. Include that utilisation in monitoring. Do not solve exhaustion by overlapping another pool or enabling an independent DHCP server for the same addresses.

Where failover is configured, follow its supported configuration replication and validation process. A policy present on one partner but absent or different on the other can make behaviour depend on which server answers.

Activate and observe a controlled renewal

Enable the reviewed pilot during the approved window. Use a test device or a renewal method that will not remove the administrator's only management connection. Existing leases may delay visible changes, so record exactly how the client obtained its new configuration.

Inspect the actual client address, mask, router, DNS servers and relevant vendor options. Confirm the lease and matching policy evidence on the intended DHCP server. A successful address allocation alone does not prove that every option is correct.

Test the device's business function, such as reaching its approved print or management service. An option string that looks correct in the console can still be unsupported by a particular firmware release.

Prove the unaffected case

Renew an approved ordinary client and confirm its previous intended behaviour remains. Test an overlapping or near-match device where that possibility exists. Review server events and available diagnostics for unexpected allocation patterns.

If the intended device misses the policy, compare its real request fields with the class definition and condition. If too many devices match, inspect OR logic, wildcards and policy order. Do not keep adding conditions until one test passes without understanding the combined expression.

If no remote-subnet devices receive service at all, examine relays, routing and firewall paths separately. A class policy cannot repair an absent DHCP relay destination.

Withdraw and maintain the arrangement

Disable the specific policy first when investigating unexpected effects, preserving its configuration. Then plan how devices return to their intended options and allocations. Already issued leases and cached device configuration do not vanish simply because a rule is disabled.

Document the class data, supported models, option values, owner and review date. Revalidate after firmware or device replacement. Microsoft documents DHCP policy conditions; related preparation includes scope migration and DNS record lifecycle.

Retain a small model-and-firmware validation list with the policy. When new devices arrive, check the request characteristics before assuming they belong to the established class. This prevents a successful historic pilot from becoming an unsupported permanent assumption.


Was this answer helpful?

« Back
Contact

Write to us

Do you have questions about our services or need a quote? Write to us and we will respond as soon as possible.

Contact form

Fields marked * are required.