The voice team cannot edit the camera scope

Windows DHCP Administrators edit every scope on the server. Lattice grants a prefix, subnet, or pool. The voice group can see the camera subnet and cannot change it.

Nov 9, 2026 · Query: DHCP administrators one scope

You want the voice team to edit the voice scope. You do not want them editing the camera scope.

On the DHCP Server role, that split is not a built-in group.

What Windows gives you

The DHCP Server role has two local groups for the service: DHCP Administrators and DHCP Users.

DHCP Users can look. DHCP Administrators can administer DHCP on that server. An administrator can create a reservation and edit scope options on every scope that server holds. Server options, scope options, and reservation options are all in reach of that same group. There is no built-in “this group writes only the voice scope.”

That is the DHCP console. It is not a missing checkbox you have not found.

The nearest Microsoft feature is IPAM

Windows Server IPAM, which many DHCP-only shops never deploy, has access scopes on IP address blocks and ranges. You set them in the IPAM console, including with Set-IpamAccessScope. The objects include address blocks, ranges, and DHCP scopes as IPAM records.

That console is IPAM. It is not the DHCP server. The server that answers Discover is still the DHCP Server role, and DHCP Administrators there are still server-wide. Manage IPAM role-based access control is the current Microsoft Learn page.

What Lattice does

The grant sits on a prefix, a subnet, or a pool in the same product that serves the Offer (Who can change a subnet).

The voice group can open the camera subnet. They cannot change it. The write is 403. The row stays visible. They can change reservations, assignments, and allowed DHCP options inside the voice subnet.

A printer pool grant covers addresses in that pool. It does not rewrite the subnet-wide router or the lease time. Global options and client classes stay with the admin. Creating the subnet or the pool stays with the admin.

Their AD group is the name already in the Lattice SSO group claim. Type that name into the local group. Lattice does not join the domain. It does not replace DHCP Administrators with an LDAP bind.

This does not split the scope, add a failover partner, or move the gateway. HA is still the same pool on every node (HA). Cutover is still dump, map, and point the relays (Replace Windows DHCP, Migrate).

FAQ

Can DHCP Administrators be limited to one scope?
Not on the DHCP Server role. DHCP Administrators and DHCP Users cover the whole server. An administrator can create a reservation and edit scope options on every scope. Who can change a subnet.
Does Windows Server IPAM do this?
IPAM has access scopes on address blocks and ranges. That is a separate IPAM console. It is not the DHCP server that sends the Offer. IPAM access scopes on Microsoft Learn.
Does this split the scope or add a failover partner?
No. The subnet and the gateway stay where they are. Lattice HA is still the same pool on every node. HA.