tdanner ✭✭✭✭✭

I merged your pull request. Thanks for that. Support would take your question as a feature request for enhancing how the platform handles certificates, or at least making it more flexible so that savvy users like yourself can plug in to their internal PKI. There's some value in that - it's easier for the product managers…

This is fixed now. You can download a release with working grid copy at Release v2.1.1-beta · solarwinds/OrionSDK · GitHub .

I don't see any workaround other than "save as". I have opened this as an issue in the SDK project: Can't copy table out of SWQL Studio · Issue #22 · solarwinds/OrionSDK · GitHub

This part is not right: #Getting the first part of the WMI string before the period (.), which Solarwinds needs for it's database.$NetobjectPrefix = $Pollertype.split("{.}")#setting params for the database fields$poller["PollerType"]=$PollerType;$poller["NetObject"]= $NetObjectprefix[0]…

The MST file is supposed to include the credential that allows the newly-deployed agent to be automatically provisioned as a node. For some reason that is not working on your system. I recommend you open a ticket with SolarWinds support to get this figured out.

Comparing floating point values for equality is a tricky thing. In general, when working with floating point values you should expect a certain amount of error, so it is better to test if the values are close enough rather than exactly equal. So rather than test if A = B, you can test if ABS(A - B) < 0.0001.

Both of these features are supported. You can modify custom properties of Nodes and Interfaces on the web console. Multi-select and edit custom properties is also supported. Grouping by custom properties is also supported in web node management.

What was your alert definition?

The rest api requires Basic authentication. I would not have expected the query call to work. Try it with something like this instead: $cred = Get-Credential $Post = @('8aaa3f9e-ba13-425f-b662-069d06a17383', 'Interface', '5644', 'Testing ACK With API') $Json = $Post | ConvertTo-Json $Response = Invoke-RestMethod -Method…

Can you post the full query?

When you query Metadata.Relationship, are you looking at both SourceType and TargetType?

Use this for the custom query resource's query: SELECT Caption, DetailsUrl + '&ViewID=68' AS _linkfor_Caption FROM Orion.Nodes And the search query: SELECT Caption, DetailsUrl + '&ViewID=68' AS _linkfor_Caption FROM Orion.Nodes WHERE Caption LIKE '%${SEARCH_STRING}%' You will need to replace the "68" there with the actual…

Here's a trivial powershell script that will do this. gc .\servers.txt |% { $nodeId = get-swisdata $swis "SELECT NodeID FROM Orion.Nodes WHERE Caption=@c" @{c=$_.Trim()} Invoke-SwisVerb $swis Orion.Nodes Unmanage @("N:$nodeId", [DateTime]::UtcNow, [DateTime]::UtcNow.AddDays(1), $false) } It assumes that each line…

You don't need to mess with XML to do this. Something like this should work: Invoke-SwisVerb $swis Orion.Accounts CreateAccount @( "System", @{ AccountId="superuser"; Password="letmein" } )

That looks like an issue Vic Cato reported a few weeks ago. The problem is that the summary status icons are being computed without respecting Account Limitations, View Limitations, or the SQL Filter configured for that resource. This bug has been fixed for the next major release.

At this point, the API doesn't give you any help figuring out which interfaces to monitor - you have to find out the interface name and index independently. In other words, there is no programmatic access to the "List Resources" UI.

Yes, you can tell NCM to execute a script on a device (or many devices). In the Samples\PowerShell directory, the NCM.ExecuteScript.ps1 script should get you started. Let me know if you need any other details.

We do not yet have an API for import/export templates, but when we add one that is where I would expect us to put it.

Orion.AlertStatus.Acknowledge takes one argument that is an array of AlertInfo structures. Orion.Nodes.Unmanage takes four arguments: a net object id (basically "N:" and then the node id value), the DateTime to start the unmanage period, the DateTime to end the unmanage period, and a boolean for "is relative" (if you pass…

Did you install VM Monitor and configure it to poll one of your ESX servers? The readme file should have some information to help you get started.

There is no API for re-firing the trigger actions on alerts, so you will have to build this repopulation capability externally. Here's how I would do it: 1. Modify the existing trigger action that sends the alerts to the central system so that it records its command line in a simple table where the key is the alert…

What version of NCM are you using? That python SwisClient class is a wrapper for the JSON interface to SWIS, which is only supported in SWISv3. SWISv2 has a SOAP interface if you really need access to SWISv2 from Python.

A few questions: 1. Are these systems connected to the internet? I have seen behavior like this from certain clients when trying to check certificate revocation lists - if you are not connected to the internet, some clients will wait for the CRL check to timeout before moving on. 2. What client/language are you using? 3.…

What kind of account is SolarWindsServAcct? Orion (database) account? Active Directory? Windows local user?

At this time, only nodes and interfaces can be placed on maps.

You can't specify the NodeID when adding a node, so there is no danger of conflict/duplication of NodeID values. What versions are you moving from/to?

This has been fixed and will be shipped in the upcoming service release.

What PowerShell error did you get? I think all you need to change is removing the [xml] piece from your last script. Like this: $TestImport = Get-Content 'PathToFile' $AlertImportResult = Invoke-SwisVerb $swis Orion.AlertConfigurations Import $TestImport

Our testing was with ESX 3.5.0 - would upgrading your ESX servers be an option?

SWIS works in UTC. So when you pass in 10:45PM, it interprets that as UTC. The time shown in the audit message is also UTC, though it would be better if it were clearly labeled as such. I can infer from your post that you are in US Eastern Daylight Time (UTC-4), because at 6:45PM local time, your node went managed again.…