IPAM managed DHCP server requirements

In the last post we discussed IPAM , a technology that allows you to centralize the management of your organization’s DHCP server. It’s important to realize that you are not limited to using IPAM to manage DHCP servers running Windows Server 2012 and Windows Server 2012 R2.

You can use IPAM to manage DHCP servers running on Windows Server 2008 R2 and above. So while you won’t be able to use IPAM to manage those 2003 DHCP servers before you migrate them, if you have migrated DHCP servers to Windows Server 2008 R2, you can still get the benefit of IPAM without being forced to upgrade from that platform.

Of course the IPAM server itself must run on Windows Server 2012, Windows Server 2012 R2, or Windows Server vNext and you’ll have to upgrade those Windows Server 2008 R2 servers eventually. But at the moment, this blog post series is more concerned about all those servers running Server 2003. We can worry about migrating off Server 2008 R2 when that product only has a few months of extended support left.