Solved Ensure DHCP scope adheres to company policy?

---

Wanted to have a quick discussion regarding this practice question. In my experience I would usually handle this by adding an exclusion range to the scope and either setting a static address on the server within that range or using a reservation. I am thinking "B" is step one. What does the ITPro community think?

Wondering if there was also a way to get this job done using Vendor Class? not sure if that applies to the version of OS, it is a feature of DHCP on Windows Server that I haven't deployed.

Regards,
Adam Tyler

You are implementing a new network. The network contains a DHCP server named DHCP1 that runs Windows Server 2016. DHCP1 contains a scope named Scope1 for the 192.168.0.0/24 subnet. Your company has teh following policy for allocating IP addresses:

1. All server addresses must be excluded from DHCP scopes.
2. All client computers must receive IP addresses from Scope1.
3. All Windows servers must have IP addresses in the range of 192.168.0.180 to 199.

You deploy a print device named Print1. You need to ensure that Print1 adheres to the policy for allocating IP addresses.

Which command should you use?

A. Add-DhcpServerv4Lease
B. Add-DhcpServer4ExclusionRange
C. Add-DhcpServer4Filter
D. Add-DhcpServerv4Reservation

Adam,

I hope all is well. Answer 'B' would be way to go here.

In terms of whether using Vendor Class to get this done in the real world would also work, that is an interesting approach. The initial answer is "not on the surface", as Vendor Class is designed to ensure that vendor-specific scope options are delivered to just the vendor's devices. The specifics can be read if you look up RFC 2132 https://tools.ietf.org/html/rfc2132

A good example of what Vendor Class could be extended to be used for via PowerShell is here:

https://blogs.technet.microsoft.com/poshchap/2015/12/18/use-powershell-to-add-a-vendor-specific-class-to-windows-dhcp/

However, never accept the initial answer, as it is often not the final answer. In this case the answer is that it actually can be as part of a larger DHCP thought process that starts to be available in Server 2012, which is the use of DHCP Policies, sometimes called Policy based IP address and option assignment or just Policy Based Assignment (PBA) for short. Read about it here:

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn425039(v%3Dws.11)

Hope that helps

Cheers,

Adam