Thank you for your interest in the SDK.
What's new in SDK v1.9?
What’s new in SDK v1.8?
What’s new in SDK v1.7?
What’s new in SDK v1.6?
What's new in SDK v1.5?
o Adding a node
o Adding an interface
o Discovering interfaces
o Setting a custom property
o Configuring Orion Groups
This package contains:
A couple of notes regarding the SDK.
SolarWinds Orion SDK Team
No, this is not currently possible. (There is a CreateAccount verb on Orion.Accounts, but at this time it only allows you to create system-level accounts. It is not suitable for creating regular website user accounts.)
If you use Active Directory authentication, you could [manually] create one or more AD groups for your Orion users. Then all you automation needs to do is add the relevant users to the appropriate AD groups and they will naturally have Orion login access. This is probably simpler to manage long term anyway.
tdanner's method makes the most sense and is exactly what we do. Now that NPM is AD aware using AD groups to control who has what access to Orion and to what seems to me the only way to go.
I've tried both Powershell 2 and 3 with version 1.6 of the SDK and the unmanage verb is not working for me.
I don't get any errors. When I and check in Orion, the node is still showing managed.
The event log shows....
changed node xyz property UnManageUntil from 5/9/2013 7:54:25 AM to 5/9/2013 12:55:29 PM Logged at 5/9/2013 12:40:33 PM.
Note the from ad to times.
NPM has an API for pulling information out. You can download the documentation for this API right from this page. What you do with the data after you have extracted it is up to you.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.