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! ๐Ÿ™‚

 

Facebooktwitterredditlinkedinmail

Let’s start over…

Many times over I thought about what I should be blogging about.

PowerShell’s the future and I really like everything PowerShell related, so a theme for the blog was ‘easy’.
Howeverย I’m not really a front runner when it comes to IT, so most of the things I’d be playing with have been done before.

I’d get stuck on what to write about, because surely no one would be interested in ‘another basic PowerShell blog’.
Writing doesn’t come naturally to me and English is not my native language, so transferring thoughts to a blog post can be challenging.
Besides that I normally overthink whatever I write, causing a ‘simple’ blog post to take me hours if not days.

What changed?

In 2018 I had a few breakthroughs that jump-started my love for PowerShell again:

All in all, I’m coding more and more again, finding new reasons to look into it and wanting to share my findings with others.

What does this mean for the blog?

Well, besides an updated colour scheme and logo, I want to grow through teaching more and attending/speaking at more seminars.

But I won’t just blog about PowerShell anymore.
I’ll try and write more about various things, such as other technologies I’m playing with [PowerShell related or not], share interesting articles/tweets that I’ve read.

This should mean some posts will be shorter than ‘normal’, but I’m hoping that like with coding,ย  writing more will help me become a better writer.
Possibly it will even help me create content more easily.

All in all, let’s start writing again ๐Ÿ™‚

Facebooktwitterredditlinkedinmail

Quick Tip – Find available versions on .wim files

Just a quick tip for personal reference [as I keep forgetting it ๐Ÿ™‚ ].

You can easily find out which versions of the Windows OS are available on an install.wim file [generally found within a Windows ISO file] using the following command:

This will provide you both the Index number as well as the name of the version.
It can come in handy when using other tools, such as [in my case] Convert-WindowsImage

Happy Scripting! ๐Ÿ™‚

Facebooktwitterredditlinkedinmail