tdanner ✭✭✭✭✭

Hard to say what's going on without more details, but my guess would be that you are logging in to the web console as different user accounts in these two contexts. If that doesn't answer it for you, could you provide screenshots and software version details?

First, the PowerShell cmdlets do support Windows authentication. You can use the "-Trusted" switch to the Connect-Swis cmdlet instead of providing credentials. This will cause it to connect using the current user's Windows token. From C#, you can use the REST format for the API. Sample code: OrionSDK/Program.cs at master ·…

What version of NPM are you using? Could you post the commands you are using to connect to SWIS and call the verb?

No, there is not. You will need to maintain the SWQL query on the client end.

Richard is right. Orion.Nodes does not have an EntityType property. There is an InstanceType property shared by all SWIS entities that you can query if you want.

We totally agree. This will be coming in a future release.

What is the name and version of the SolarWinds product(s) on that server? What version of SWQL Studio? What server type are you specifying in the SWQL Studio connection dialog? Are the laptop and server on the same AD domain?

It uses TLS. The exact details (TLS version and cipher suite) will depend on the Windows versions and configurations involved. The easiest way to see what is being negotiated on your actual systems would be wireshark.

For the "Definition" field in the group member, just use the SWIS uri of the child group instead of a filter. Like this: swis.invoke('Orion.Container', 'CreateContainer', 'Sample Parent Group', 'Core', 60, 0, 'This is the parent', True, [ {'Name': 'child group', 'Definition':…

The index for volumes and interfaces is just an snmp bookkeeping detail. It might mean that a volume was added or removed from the device, or it might mean nothing.

You can run more than one discovery at a time, but don't do it in two tabs in the same browser - the discovery wizard keeps state in the asp.net session and all of the tabs/windows in a browser have the same asp.net session cookie. Use a different browser (like Chrome and Firefox) if you need two separate sessions at the…

You should be able to shut off those alerts by adding a "Node status is not equal to Unmanaged" condition to the trigger criteria.

We don't currently have cross-domain or JSONP support for the API. Could you tell us more about what you are building?

Sure. Setting custom properties using a script is a common task. You can get started here: https://github.com/solarwinds/OrionSDK/wiki If PowerShell is a good scripting language for you, here's a sample showing how to set a custom property value:…

Unfortunately the code that handles Flow data queries does not have an optimized code path for these date manipulation functions. While it can handle simple +/- on date/times, using functions like AddMonth and DateTrunc will throw you into the brute-force table scan code path. On any non-trivial flow database the queries…

Powershell would be a reasonable tool for this job. At a high level, you would want to export the node list from NPM like this: $swis = Connect-Swis # your connection details here $npmNodes = Get-SwisData $swis "SELECT Caption, DNS, IPAddress, Uri FROM Orion.Nodes" # maybe add a WHERE clause to exclude network devices from…

When you install the Orion SDK, a sample VB.NET client application gets copied to C:\Program Files (x86)\SolarWinds\Orion SDK\Samples\VBClient.

The next release has SWIS entities for "Orion.Views" and "Orion.Resources".

An alert action to unmanage the interface seems like a good way to handle this requirement. Obviously when you unmanage the interface, NPM won't be polling it and therefore won't detect when the interface comes back up. When the unmanage expires, the polling will resume and the status will be detected again. Here's a…

You can use this technique: Triggering discovery of SNMPV2 device through JSON API to add a node with all volumes. To avoid monitoring removable drives, you would need to wait for the discovery to complete and then delete the unwanted volume monitors.

We don't have a way to uninstall the website, but if you just want to delete the files they are normally installed in \Inetpub\Solarwinds.

I added an explanation for this one here: https://github.com/solarwinds/OrionSDK/wiki/Creating-custom-properties

Not really. Orion is flexible, but it's not a general purpose graphing tool. I believe you can hook up MS Excel to an external data source like SQL - that might be a good way to generate your graphs. You could even use its VBscript automation interface to regenerate the graphs on a schedule.

REST API uses HTTPS on port 17778.

This is not really something we recommend you do. We don't have any documentation for that file format. That said, if you do want to try it the parameters for InsertFile are: 1. path - this is the filename that Network Atlas will know the file as, not the path of the file you are uploading. It corresponds to the FileName…

The Alerts web page in Orion 9.1 displays Basic and Advanced alerts together, so you don't have to switch back and forth.

In the API, deleting the agent and deleting the associated node are two separate operations. The agent management UI combines them. Your PowerShell for deleting the agent looks correct. You can also do it by getting the Uri for the agent record and calling "Remove-SwisObject $swis $agentUri" on it. It leads to the same…

It is a serialized .NET DataTable, so the XML is a little weird. You can either deserialize it back to a DataTable using DataContractSerializer, but this is a bit awkward to set up in PowerShell. You can also just access the data directly. If $xml holds the value returned from Invoke-SwisVerb, the collection of results is…

SWIS Invoke/... calls always take a JSON array. The parameters are positional, not named. Try something like this: [ "Orion123", "Core", 60 0 "hello", true, [ { "Name":"Test1234", "Definition":"filter:/Orion.Nodes[CustomProperties.IT_Service='WAN' AND CustomProperties.Site_Code='USA']" } ] ]

There are python samples showing how to run SWQL queries. IPAM data is available through SWQL queries, so this will just be a matter of defining the right query and then plugging it in to the python script. I recommend installing SWQL Studio (you can get it here: https://github.com/solarwinds/OrionSDK/releases/latest) and…