DHCP Reservation vs Static IP address

Using DHCP reservations offers you a sort of poor-man's IP address management solution. You can see and change IP addresses from a single console and makes it so you can see what addresses are available without having to resort to an Excel spreadsheet (or worse, a ping and pray system).

That being said, many applications require a static IP. If the server is configured to use DHCP, the application has no way of knowing that a reservation exists and may refuse to install. Also some applications tie their license to an IP address and therefore must be static as well.

Personally I prefer to use reservations when I can, and statics when I have to. But when I do use a static, I make a reservation for that address anyway so that A) it can be within the scope with the rest of the servers, and B) still provides the visual accounting of the address.

NOTE: If you're referring to network devices like IP cameras and printers, reservations are definitely the way to go because you can add a comment in the reservation as to what the device is and where it's located. Depending on the device, this may be your only means of documenting that information within the system.

I have never ran into a situation that I NEEDED to use a static but was more profitable to use one such as office laser jet printers (when you do always block the ip address from DHCP).

In my opinion laptops, phones, and any "mobile" devices should be reserved not static. It requires no set up on the device and the server will reserve that address for that device.

When it comes to printers and in certain cases workstations (if you need to know the address... for remote desktop ect.) always go static but remember to block the address from DHCP.

Remember though if you need to re-configure your subnet mask for any reason any and all static devices must be changed. Always think about future needs.