tdanner ✭✭✭✭✭

I don't believe the feature was implemented. As a workaround, you could use the Universal Device Poller to fetch the values from that OID and display them on the node details page.

Remanage looks like this: Invoke-SwisVerb $swis Orion.Nodes Remanage @( "N:123" ) Or you can just set UnmanageUntil to the current time (or past): $uris | Set-SwisObject $swis -Properties @{ UnmanageUntil = [DateTime]::UtcNow }

Are these devices things that Orion can normally pull the Service Tag value automatically? If so, it should update it on the next polling cycle (default 10 minutes) if it changes.

There's no minimum. Any access at all will allow him to connect and run queries.

No change in NPM 12.

Your best bet is to go product by product - the development resources to actually address these issues are associated with the individual products, not with the SDK as such.

To acknowledge multiple alerts in one call, you need multiple <AlertInfo> elements inside the single <ArrayOfAlertInfo> element. Like this: Add-PSSnapin SwisSnapin $swis = Connect-Swis latest-stable-builds -UserName admin -Password "" $queryResult = Get-SwisData $swis "SELECT TOP 3 AlertDefID AS DefinitionId, ActiveObject…

We're going to have to follow this another level down. Could you reproduce the error again and look in C:\ProgramData\SolarWinds\InformationService\v2.0\Orion.InformationService.log? That should have the details.

The last parameter for Orion.Nodes/Unmanage is called "isRelative" and it affects how the "remanageTime" parameter is interpreted. If you provide "true" for isRelative, then the time of day portion of remanageTime is treated as an offset to the unmanageTime (and the date portion of remanageTime is ignored). If you provide…

I see - I didn't realize you were including snapin loading time in that number. How long does the query take from after the snapin has loaded?

The snapin is compatible with both x86 and x64 powershell instances. The installer is supposed to register it in both environments, though we have had some reports of this not happening correctly. To register it manually, run these commands: C:\Windows\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe "C:\Program Files…

I added a couple of sentences to PowerOrion A Module for PowerShell · solarwinds/OrionSDK Wiki · GitHub​ about how to get the files. Hopefully that will give the next user a slightly smoother experience getting started.

VM vs. physical and remote database vs. local shouldn't affect this behavior.

Orion loads the MapQuest plugin for Leaflet from www.mapquestapi.com. Currently I have observed this plugin contacting {a,b,c,d}.tiles.mapbox.com and api-s.mqcdn.com, but this is controlled by MapQuest and not by SolarWinds, so it may change without notice.

I'm not sure what's going on here. By "integrated", you mean that you have the "CONFIGS" tab in the website, right? You can do the usual NCM operations from the same website where you can look at NPM data?

I can confirm this is fixed in NPM 12.0.1. Not all the fixes make it into the release notes.

I see. SP1 should be out in a few days. You should try that and see if you can get the behavior you want.

Unfortunately, I don't see anyway around this one. With the Edit Node issue earlier in this thread, there was a place in the webiste code you could just edit to have it skip that property. For this problem the code you would need to edit is all compiled. Bad news - you will probably have to choose between the handy…

"+ 0.0" ought to work. If you post a full query I might be able to give more specific advice.

You can just do "+0" on a string value to convert it to an int.

Here's a SOAP request that works for me: <s:Envelope xmlns:s="">schemas.xmlsoap.org/.../"> <s:Body> <QueryXml xmlns="">schemas.solarwinds.com/.../informationservice"> <query>SELECT NodeID, Caption FROM Orion.Nodes</query> </QueryXml> </s:Body> </s:Envelope>

It's definitely possible that different community strings could return different results. But from your stack trace it looks like both the Community and RWCommunity are "private".

You don't need to make a Create call for custom properties - that entity is created automatically when the node is created. To set custom property values, you need the node's URI (it is returned from the Create call for Orion.Nodes) with "/CustomProperties" appended. Then you can call Update passing that URI and the values…

Yes, that's the right kind. Please check C:\ProgramData\SolarWinds\Logs\Orion\Core.BusinessLayer.log for error details.

What happens if you go to http://127.0.0.1/Orion/Login.aspx?

Ok, with that detail I can see the problem in the original exception now. Look at this part: <PluginConfigurationItem type="string">"<?xml version=\"1.0\" encoding=\"utf-16\"... There are two problems here. The very first character of the string is a double quote ("). That's no good. (And the last character of the string…

Kevin and bama, Since we didn't find your errors in OrionWeb.log, the next place to look would be the Application Event log. Specifically, look for errors where the source is ASP.NET.

I don't think you can give access to an interface but not the node it lives on. The semantics of limitations on interfaces are such that if you don't have access to the parent node, you don't have access to the interface either.

Oops - I forgot to link to the Java sample. It's at https://github.com/solarwinds/OrionSDK/tree/master/Samples/Java/swis-client

Sure. If you have an IP address and you want to check whether NCM knows about it, just run a query like this: SELECT NodeID FROM Cirrus.Nodes WHERE AgentIP=@ip.