I've had a powershell script that uses the Orion SDK that's been working for the past year that suddently stopped working after an Orion upgrade. I end up making this call
Invoke-SwisVerb $swis Orion.Nodes Unmanage @("N:$nodeid",$start,$end,"false")
I get a successful response from the server. If I look at the results on the node (which tells me it's talking to Orion,and has the right node ID), I see an event where it updates the unmanagedfrom and unmangeduntil for the 1 hour unmanaged window that the script is supposed to set.
8/22/2013 9:03:43 AM | User scriptusr changed node myserver.my.domain property UnManageUntil from 8/22/2013 5:55:36 AM to 8/22/2013 10:03:23 AM | ||
8/22/2013 9:03:43 AM | User scriptusr changed node myserver.my.domain property UnManageFrom from 8/22/2013 4:55:36 AM to 8/22/2013 9:03:23 AM |
Noting has changed with the script that was working fine up until last week when some Orion updates were done. I'm not the one that did the updates, so I'm not sure what was applied. This is what version shows in the Orion footer:
Orion Platform 2013.1.0, SAM 5.5.0, NPM 10.5, IVIM 1.6.0
I was running v1.5 of the SDK, but upgraded to v1.7 and get the same exact results.
If I log into the GUI as scriptusr and click unamange from there, it does unmanage the node. So it seems like I can authenticate, send the unmanage command, have access to unmanage the node, but it's still not working all of a sudden.
Any suggestions on what may be causing this are very much appreciated.