tdanner ✭✭✭✭✭

You can also do this as a bulk operation. For larger numbers of objects it is much faster. Like this: $swis = Connect-Swis -Hostname $hostname -Username $username -Password $password $CustomPropstoUpdate = @{ Environment = "QA"; } $uris = Get-SwisData $swis "SELECT Nodes.CustomProperties.Uri FROM Orion.Nodes WHERE…

We will investigate and let you know what we find.

"System" is the responsible user for things that happen automatically or otherwise not in the context of any particular real user.

Re: UnDP - if you just need to assign existing pollers to nodes, this is already supported. See NPM Universal Device Pollers · solarwinds/OrionSDK Wiki · GitHub

Another way to work around this is to use the version of SolarWinds.InformationService.Contract2.dll from your Orion install directory (typically C:\Program Files (x86)\SolarWinds\Orion) instead of the outdated one that the SDK installs.

Here's a sample script: https://github.com/solarwinds/OrionSDK/blob/master/Samples/PowerShell/AlertSuppression.ps1

When you query SWIS, you are querying SWIS entities, not database tables. There is a rough correspondence between many of the database tables and SWIS entities, but they are not the same. SolarWindsOrion.NodesData is a database table. The corresponding SWIS entity is "Orion.Nodes". I recommend you start by reading the…

That's the server running the SolarWinds software (NPM or SAM or whatever you are using).

This sounds like either a problem with network connectivity (could a firewall be blocking port 17777?) or a problem with the Orion server (is SWISv3 running?). The next troubleshooting step I would try it connecting to SWIS locally on 100-swdb-v-p01. If that succeeds then you have a network issue. If that fails then you…

The first argument to Get-SwisData needs to be a connection object returned by Connect-Swis.

You have a space between the "$password" and the ".ToCharArray()". That's not allowed in PowerShell. Tip: when confronted with these kinds of syntax errors, open your script in an editor with syntax highlighting for PowerShell like the built-in "Windows PowerShell ISE". That can help zoom in on the problem.

If you want to make API calls without installing the PowerShell snapin, just use the REST API. It can do all of the same operations - just the syntax is different.

I think you need two more instances of Orion.Pollers with the PollerType values V.Statistics.SNMP.Generic and V.Status.SNMP.Generic. For an example of calling the discovery API using PowerShell, see this post: Re: Re: How do we programmatically discover the non-interface properties [in Orion] and enable them

You could delete the Node Details view, then run the Web Configuration Backup tool and have it Merge (not Overwrite!) the "NetPerfMon Initial Configuration" file. This will give you a new view called "Node Details" with the default resource setup, but it will have a different view id number in the database. It may be…

After reading your message again I realized it was not quite clear what you meant by "But it doesn't seems to work for which I conclude that there some other hidden entries somewhere on the database." Is it just that you are still seeing the hardware and vlan data that was collected before you disabled that collection?

VoIP Monitor 1.0 is built around IP SLA. You are correct that for it to be useful, you will need IP SLA-capable hardware in more than one location. Several low-end Cisco routers support IP SLA. You could purchase one of these for each of your remote sites. It isn't necessary for the IP SLA router to actually be routing…

What does "(Get-PSSnapin swissnapin).Version" say?

Have you tried using the debugger in PowerShell ISE to inspect the actual value right before the error? Set a breakpoint on the "$nodes = $captions |? {(get-swisdata..." line.

And what is the value of $serverlist at that point?

What is the text of the error?

Current versions of Orion won't live in a virtual directory or coexist well with other websites on the same IP/port. qle's first suggestion, running each website on a different port, is the way to go.

You can also do this with an existing report. When you edit the "Report From Report Writer" resource, just add a Filter like: Nodes.NodeID=${NodeID}

The control we use to generate maps seems to be sensitive to the bit-depth of RDP sessions on the web server (even if they aren't doing anything Orion-related). Use the Terminal Services Manager app to see what sessions are open on the server. Make sure they are all connected with greater than 8-bit color depth. Log out…

I believe the "The HTTP request was forbidden with client authentication scheme 'Basic.'" error indicates a bad username/password. Are you sure those are correct? Are you using a Windows account or a regular Orion user account?

Thanks for sticking with this and finding the combination of factors that is not working. The factors are: 1. Authenticating as an AD group member 2. Over the https/REST channel 3. To change data in IPAM (invoke/update) Is that an accurate summary of what you are seeing?

Probably best to open a support ticket for this. It looks like your database is missing a chunk of configuration data that the website depends on. Sending the output of the SolarWinds Diagnostics tool to support should let us figure out how much is missing and why.

Yes. There are two ways to do this: 1. With a SQL-style LEFT/INNER JOIN syntax. Like this: SELECT N.Caption AS NodeCaption, V.Caption AS VolumeCaption FROM Orion.Nodes N LEFT JOIN Orion.Volumes V ON N.NodeID=V.NodeID 2. With a navigation property. Navigation properties are a SWQL construct that give you a simpler way to…

Oh! Now I get the ****. This forum apparently has an aggressive filter. SWQL Studio is a windows gui tool for running SWQL queries. It includes a tree control with all of the entities and properties. You can download it from https://github.com/solarwinds/OrionSDK/releases Yes, that's the right link for the schema reference.

Interface naming gets a little complicated. When you refer to Orion's description, you probably mean our Name property for the interface (stored in the Caption field of the Interfaces table in the database). This is the one you can edit in the Interface Details screen and its the one Orion uses to display the interface in…

Sorry for the delay. The relevant table is AlertStatus. When an alert condition no longer holds, the alert record is removed from AlertStatus.