gtalton

FWIW .. I just tested these macros .. ${USER} works and ${IP} always worked .. however ${PASSWORD} clearly does NOT work at I can code other ways around this not working .. however I think the documentation should be fixed to reflect this .. BTW I tested on SAM 6.22

To further build on this ... the original request/post was to get the community string for a device .. and that's exactly what I needed also. Using the ${Node.ID} .. and the Orion Powershell SDK.. you can get the community string .. here's the code for my SAM Powershell template .. (BTW I put username/pass in CSV file)…

Excellent thank you Jan!

Actually clearing the alert on the website wasn't working for me either .. the AlertStatus record was in fact remaining in the table .. the double record delete with a pause has fixed it. It is a shame that this isn't a part of the API ... because there are some compelling reasons to have it there. In fact, on the other…

Yep I was aware of that ... but thanks a lot for the reply.

chrispaap, I basically need this Centos 6 version .. even if in beta .. ASAP. Our internal security scanners have detected vulnerabilities that I'm tasked with fixing .. and right now with Centos 5.11 being end-of-life .. I have no options. If I can't get this from Solarwinds .. then I will have to hold off on our next…

Hi Jan, First off thanks for replying to the request. However I already looked at Acknowledge and found it doesn't implement the semantics I'm looking for ... what I'm looking for is a way to force the Alerting Engine to forget entirely that an Alert has happened. Specifically so that if the problem is still occurring ..…

So if I run this in SWQL Studio .. it works: SELECT Notes FROM Orion.AlertStatus WHERE ObjectType = 'Node' AND ActiveObject = 9 if I run this, I get a very scary error: SELECT Notes FROM Orion.AlertStatus WHERE ObjectType = 'Node' AND ActiveObject = 9 AND AlertDefID = '68C0553A-1303-41BA-924F-07D1C4CE5A98' and I am getting…

So the fix here was to uninstall both Microsoft SQL Server Management Objects 64-bit and 32-bit .. then the install does it and completes.

This seems to be working now .. thanks tdanner for all your help.

Here's the latest test run ... where I print the Select before I run it: PS C:\Users\Administrator\Documents> .\findRForceTicketId.ps1 68C0553A-1303-41BA-924F-07D1C4CE5A98 9 Node alertDefId is : 68C0553A-1303-41BA-924F-07D1C4CE5A98 nodeid is : 9 objectType is : Node SELECT Notes FROM Orion.AlertStatus WHERE…

Yep, I noticed that right before you posted, rather embarrassing but fixed .. I am still getting these errors however and that's even after a restart cannot be used for communication because it is in the Faulted state

So here's the other data point .. I am really simply just trying to get my lame Powershell script below to do this query and this seems to always fail if I try to do the select using the UUID in the WHERE clause: ------------------------- LAME NEWBIE POWERSHELL SCRIPT ------------------------ Add-PSSnapin SwisSnapin…

FWIW, I found that yes, by the time the Reset action is executed this record is gone.