Windows Server 2012 IPAM

Server 2012 has a lot of really good new features. This isn’t one of them.

Firstly, for those who haven’t heard of it yet, IPAM is IP Address Management, a new feature in Windows Server 2012. As Microsoft describes it:

IP Address Management (IPAM) in Windows Server® 2012 is an integrated suite of tools to enable end-to-end planning, deploying, managing and monitoring of your IP address infrastructure, with a rich user experience. IPAM automatically discovers IP address infrastructure servers on your network and enables you to manage them from a central interface.

I have been wanting to get away from the Excel spreadsheets that I have been using that people frequently neglect to update and are out of date. This sounded like a great place to start, and it’s built into Server 2012, so there wouldn’t be any additional money needed, which companies always love.

I followed this TechNet article to get everything up and running. The steps are pretty easy. First I installed the feature, then connected to it via Server Manager and chose the option to use GPOs to configure the firewall and security settings. It basically creates three GPOs, one each for DNS, DHCP, and domain controllers.

Provisioning Completed

Next you let it scan, it figures out what your DNS, DHCP, and domain controllers are in the domains that you specify.

Next, a simple line of PowerShell on the server:

Invoke-IpamGpoProvisioning -Domain -GpoPrefixName IPAM1 -DelegatedGpoUser user1 -IpamServerFqdn

That sets up your GPOs. Once they are in place, you just change the status of the servers you want to manage from the discovery process from Unspecified to Manage. Once the servers pick up the new GPOs, do a refresh to show the servers are managed, then tell it to retrieve all the data from the servers.

It was very easy to set up. If you don’t count the time it took to log into the eight servers I added to do a gpupdate, the whole thing took less than 10 minutes.

Once I got all the data in, I started looking around, though, I was pretty disappointed. The main thing I was looking for was a way to more easily manage my manual server IPs. IPAM has nothing for that. Basically it’s just a DHCP pool aggregation tool. There are a few things you can’t get from your trusty DHCP administrative tool like DHCP scope usage trending:


I’ve only got a day’s worth of data, so nothing exciting there. That would be something useful, but other than that, there’s just not much there. It has what it calls DNS Zone Monitoring, but all I get is this:


With no explanation anywhere I can find of what the warning is, so I can’t see how that is of any use. The only right-click option on the DNS zones is to reset the status, so I can get zones from Warning back to OK, but you can’t reset multiple zones at once, which is a pain.

There is also PowerShell that will let you export DHCP pool data from SCVMM so that it can be tracked as well, but it’s not automatic as regular DHCP servers are. I’m not using DHCP pools in VMM, so not a feature I could test.

I suppose if you have a huge organization with DHCP servers and scopes everywhere and wanted to have a place to see utilization info at a glance, then this tool is for you. If not, then you’re probably not going to get much out of it.

I think a few additions in R2 would make this feature much more useful. Better integration with System Center, such as Ops Manager alerting, and Service Manager pool requests. Also, it would be nice if it would do ping sweeps and lookups for subnets that are manually assigned and report back on those. And perhaps a tie-in with AD Sites and Services to let you know if you’re using scopes that AD isn’t aware of. If they could add a few features like that in the next version, I think it would be a much more valuable tool.

PowerShell and the Not enough storage is available to complete this operation error

Recently while running a PowerShell script, I started having some problems that had never happened before. I hadn’t made any changes to the script, but the section of the script that remotes into a SharePoint server and updates a list quit working for some reason. The script was just hanging there, and would eventually time out on that section and move on. Luckily, PowerShell threw an error at me to give me some idea of what was happening.

Processing data for a remote command failed with the following error message: Not enough storage is available to complete this operation. For more information, see the about_Remote_Troubleshooting Help topic.

“Not enough storage is available”? The first thing my brain did was flashback to NT4 Service Pack 3. Do I need to set the IRPStackSize registry key? Probably not, and I was really surprised I remembered that issue, it’s been a decade or so.

After some Googling with Bing, I discovered that by default, WSMan allocates only 150M of memory to each remote shell. You can verify that by running this one-liner:

(Get-Item WSMan:localhostShellMaxMemoryPerShellMB).Value

That should return 150 if you haven’t made any modifications. My script wasn’t putting that much data into SharePoint, but I figured this looked like a likely culprit, and hey, memory is cheap these days. So I bumped that 150M up to 1G.

Set-Item WSMan:localhostShellMaxMemoryPerShellMB -Value 1024

After changing that setting and running the script again… Bingo! The SharePoint data was successfully input and the script was fully functional again. I’m not sure what might have caused that to happen as nothing had changed in the script or on the server, but as long as it’s working, I’m happy.

How To Create Windows 8 Tiles To Reboot or Logoff

One of the things that I did not like in Windows Vista and Windows 7 was that in order to logoff, shutdown, or reboot, you had to make quite a few clicks. It seems to me that the process was just way too complicated, and it was blogged about by many people. I thought that certainly after all the complaints Microsoft heard that it would be better in Windows 8 and Server 2012. Nope.

Now, in Windows 8, you have to get the charms bar up by either putting your mouse in the lower-right hand corner, or by using the Win+C shortcut, then click on Settings, then click on Power, then pick the option you want from the pop-up menu. It’s different, but still way too many steps to have to go through. Ok, if you have PowerShell open, you could just type Restart-Computer, but not everyone always has PowerShell open, especially if you are using a Surface RT. A good solution would be a little more universally available.

Like the guy yelling out the window in “Network”, I decided I didn’t want to put up with that for several years. So I decided to find an alternate method.

I found some control panel add-ins, taskbar shortcuts, and some other things that would get me where I wanted, but I was looking for something a little… well, sexier, from a geek perspective. Like doing it via PowerShell, that would be sweet. Then I found this gem over on the Microsoft Script Center. If you’re an IT person dealing with Microsoft technologies, I would highly recommend keeping that site in your favorites, as well as the Hey Scripting Guy! blog. Because you are using PowerShell already, right? I thought so.

This PowerShell solution comes with a module that you import, then you just run New-OSCWindowsTile and BAM! you have tiles for Shutdown, Restart, and Logoff. Once that’s done if you hit your Windows key on the keyboard, then type “res” you should see the Restart option. On my computer, I can now reboot with just five keystrokes instead of all that mouse clicking.

Fruit Ninja Won’t Update In Windows App Store

If you were one of the people who had Windows 8 up and running before the release to the general public, and installed Fruit Ninja when it was free, you might be running into an issue now where the store tell you that it needs an update, but it just throws an error every time you try and actually install the update. Here’s what I was able to do to fix that. First, open a PowerShell prompt as administrator and run this:

Get-AppxPackage HalfbrickStudiosPtyLtd.FruitNinja | Remove-AppxPackage

That will uninstall the app. For me, doing the uninstall from the Start screen didn’t actually remove it. Once you have done that, then run:


which will reset your Windows Store cache. Once that’s done, you should be able to go back to your list of apps and successfully install the newest version.