IPAM 2016 in PowerShell

I recently got asked to help out to get IPAM installed and configured in our environment.
Now that’s not really hard to do, but I thought I’d do it all through my favourite tool: PowerShell.

What is IPAM

Let’s go back a step quickly and answer the obvious question:

What is IPAM and why do I need it

IPAM stands for IP Address Management and it’s a built-in feature for Windows Server since 2012 and up.
To quote Microsoft:

IPAM provides highly customizable administrative and monitoring capabilities for the IP address and DNS infrastructure on an Enterprise or Cloud Service Provider (CSP) network. You can monitor, audit, and manage servers running Dynamic Host Configuration Protocol (DHCP) and Domain Name System (DNS) by using IPAM.

Now there are a plethora of IPAM installation and configuration guides, but I noticed that while some of them touch on PowerShell cmdlets available, none of them actually seem to do the installation and configuration through PowerShell itself!

Give me the good stuff!

I’ve made a script which uses all the techniques the “manual” guides say are best practice, along with the IPAM troubleshooting guide to make sure all permissions work as a charm [don’t be fooled by the beta name, this still applies to 2016 server as well].

The entire script should be run region by region on the actual IPAM to be server, assuming it is domain joined and the person installing has all the required permissions to do so [as well as simple AD query permissions].

While the latest version can be found on my GitHub repo, I’ve added a copy here so you can start playing around ASAP!

Happy Scripting! 🙂



Introducing Windows Server 2019

This just out by the Windows Server team

Windows Server 2019 is now available for Preview!

With this release of the latest server OS, Microsoft will try and focus on the following items:

  • Hybrid Cloud Scenarios
  • Security
  • Application Platform
  • Hyper-converged Infrastructure [HCI]

General availability is expected for the second half of calendar year 2018.

Read all about it on Microsoft’s release post here!


Installed the VHDX and tried the ISO file, but nothing really spectacular so far.
Did notice the GUI install option has been completely removed, so I guess some of my colleagues will be running Windows Server 2016 quite some time 😉


Once I have more time to play with this, I’ll be sure to create another post with all the goodies 🙂