MicroNugget: What is Different about Windows Server 2012 IPaM?

In this video, Tim Warner covers IP Address Management, or IPAM, which is a new feature in Windows Server 2012. Many security compliance auditing and administrative functionality tools are available at a high price, but Windows Server 2012 offers quite a few options in these areas right out of the box.

One of the struggles systems administrators have is maximizing functionality at an economical cost. Being able to aggregate all DNS servers in a forest and analyze their statistics, or pull together information from network access protection (NAP) policy servers — these are incredible capabilities that are commercially available but have generally required a pretty high premium. One of the revolutionary aspects of Windows Server 2012 is that many of these tools are included right out of the box, substantially boosting a sysadmin’s capabilities at no extra cost. IPAM is one of these features, and Tim digs deep into what this looks like and how you can leverage it.

Start learning with CBT Nuggets:

[rogerv]

Note You can't install IMAP on a DHCP and on a DC.
IPAM in Windows Server 2012 R2 introduces the ability to view and manage the
address space used for virtual networks separately from the address space used for physical networks.

[jodelboy]

Nice vid, thank you! Gonna give it a try next week.

[jodelboy]

So I installed IPAM on a new server in my network. Seems like it cannot handle Windows Server 2012 Failover. There is no single option which says Failover, which means you have to do it all over the good ol' MMC.
Also IPAM does not import the MAC addresses of my Client-IPs as a "MAC address" - Instead it imports it as a "ClientId" which causes the IP reservation not to function - It looks for "MAC address" but that cell is empty.
It would be such a nice tool if it just was programmed better ;)