Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Getting the error of "Set-SwisObject : Access to IPAM.IPNode denied." using PowerShell

When doing the set-swisobject I get an access denied error. The account "admin" is marked as an admin in the Orion website.

Is there another location to set permissions that enable read/write on the nodes?

Find more posts tagged with

Accepted answers

All comments

tdanner

That error message could be improved. Access is denied not because of your account rights, but because updates to IPAM.IPNode are not supported.

Could you tell me more about your use case? What kind of updates would you like to make?

patrickm

I am trying to use Powershell to update the status and names of IP addresses. For example create a over all process that provisions and IP Address, sets its status to assigned and enters the computer name. All of this in the IPAM.IPNode

Is this a read only node? Is there another way to enter this information?

Thanks

tdanner

That makes a lot of sense. I don't believe it is possible today, but I have sent this as a feature request to the product manager for IPAM.

patrickm

Do you know of any other way to achieve this outside of powershell perhaps a webservice call or something?

dusting

Is this now fixed with IPAM API · solarwinds/OrionSDK Wiki · GitHub ?

If so, we are running IPAM 4.5.0 and still getting access denied while running

Set-SwisObject $swis -Uri 'swis://localhost/Orion/IPAM.IPNode/IpNodeId=2' -Properties @{ Alias = 'test1' }

but when running

Get-SwisObject $swis -Uri 'swis://localhost/Orion/IPAM.IPNode/IpNodeId=2'

we are getting the results we expect. Is there permissions somewhere I am missing?

Thanks,

Dustin

justin.richert

When the account was just an IPAM Admin, this would happen, when we made the account a full admin across the board, it was able to do what it needed. Is there other permissions that need to be set with the IPAM 4.5.0 update that enables CRUD actions on the IPAM Module?

Thanks,

Justin

tdanner

I would have expected it to work as an IPAM admin. Let me check with the IPAM dev team and see if we can figure this out.

yarl

Hi,

IPAM API requires Site Admin IPAM account for any not readonly operation including managing IPAM.IPNode entity.

Hope this helps.

yarl

Hi,

IPAM API requires Site Admin IPAM account for any not readonly operation including managing IPAM.IPNode entity.

justin.richert

Hi yarl,

We had this set for the user prior to turning it into a full Solarwinds Orion Admin, and it was still getting the Access Denied. We had to set this user up as a Full Solarwinds Orion Admin to get the Access Denied to go away.

Justin