Windows Server 2012 IPAM feature - "Unblock IPAM Access" error/recomended action

So, I'm in the process of setting up an IP Address Management server, using the built-in IPAM feature in Server 2012, and have run into a problem that I'm hoping someone else has successfully solved.

Following the technet guide here, I've installed and configured IPAM, and have provisioned it via GPO. After verifying that the PowerShell invoke-ipamgpoprovisioning command is successful, managing the desired servers in IPAM, running gpupdate /force on the servers and refreshing my view in IPAM, I'm still getting the less-than-useful recommended action of "Unblock IPAM Access" for all servers. (First done 3 hours ago, so it's not a give-it-time-to-propagate issue.)

Can't, for the life of me, seem to figure out what's causing this, find anything useful in the logs, or find much about this on Google or in the help files, so I was wondering if anyone here had any ideas about how to fix this, or even where to start looking.

I'd really like to get this working, because if not, I have to resume work on creating an Excel spreadsheet for IP address management.

Solution 1:

Probably you already resolved this long ago, but answering for other people with the issue.

Solution taken from here: http://khellman.blogspot.com/2014/02/unblock-ipam-access-to-dc.html (and worked for me):

Editing the problem server in the IPAM Server Inventory panel to untick DNS - OK - then reticked DNS fixed it.

Solution 2:

I experienced the same error yesterday. Basically, I resolved the issue by making some changes to my firewall settings on the server which I use to host my DHCP and DNS server.

Based on the screenshot, I see that DNS RPC Access Status is marked as blocked. What I did was to open the management console for Windows Firewall with Advanced Security and enabled the RPC (TCP, Incoming) and the RPC Endpoint Mapper firewall rule for the DNS Service group.

To resolve the Event Log Access Status issue, add your IPAM machine to the Administrators group in Active Directory.

Hope the above will resolve your issue. :)