clum09

Honza, What other alternative can I try to be able to add the WMI credential to the Orion node for SolarWInds Orion during adding node? Has this script ever worked at another settings in the past? Thanks.

#Adding NodeSettings $nodeSettings = @{ NodeID=$nodeProps["NodeID"]; SettingName="WMICredential"; SettingValue="12"; } #Creating node settings $newNodeSettings = New-SwisObject $swis -EntityType "Orion.NodeSettings" -Properties $nodeSettings Instead of SettingValue=($credentialId.ToString());, I just set the value to a…

tdanner, I tried to set the credentialId = 12, but the credential was still not added. What else I can I try? Thanks.

Hi tdanner, I am sorry for be late in responding to your post. I still cannot add the WMI credential to the Orion node even with your new script. In fact, I had already corrected the dash issues on my script after I learned it from you when you pointed out to me. Yes, the $credentialId variable is a system.object array…

tdanner, You said you had corrected the WMI credential issue in your previous post. I want to know if it was the problem with the code of the script or the SDK itself. If the problem was with the script, can you let me know the code that can add the WMI credential to the Orion node? Thanks.

I still get the error: PS C:> Get-SwisData $swis "Select [Caption],[City] FROM Orion.NodesCustomProperties cp INNER JOIN NodesData nd on cp.NodeID = nd.NodeID" Get-SwisData : Source entity [NodesData] not found in catalog At line:1 char:1 + Get-SwisData $swis "Select [Caption],[City] FROM Orion.NodesCustomProperties cp ...…

tdanner, Basically, after I launched the script code to add the WMI credential that I listed on my previous post and then I went to the Orion webpage Settings, Manage Windows Credentials page, and I tried to browse for the credential names that were list on the table of that page, I could not find them on that page. The…

I tried using the Orion.NodesCustomProperties as you indicated, but it still does not work. PS C:>Get-SwisData $swis "Select City FROM Orion.NodesCustomProperties cp INNER JOIN NodesData nd on cp.NodeID = nd.NodeID" Get-SwisData : Source entity [NodesData] not found in catalog At line:1 char:1 + Get-SwisData $swis "Select…

tdanner, Thank you for the information. When will the next release of the SDK package be available? Also, I forgot to mention that when the ran the code to add the WMI credential for the node, it seemed to temporarily wipe out the Windows credentials on the list I have on the Manage Windows Credential page for some reason,…

I did not get any error. The script ran fine, but the custom properties were not created. To bypass the certificate issue, I just used the following code before the Invoke-RestMethod cmdlet. Add-Type @' using System.Net; using System.Security.Cryptography.X509Certificates; public class TrustAllCertsPolicy :…

I tried: Get-SwisData $swis "Select City FROM NodesCustomProperties cp INNER JOIN NodesData nd on cp.NodeID = nd.NodeID", but I got the following error: Get-SwisData : Source entity [NodesCustomProperties] not found in catalog Thanks.

tdanner, Thank you for pointing this out. Actually, the sample scripts that came with the SDK 1.9 have a longer dash (hyphen) character on some of the parameter lines. That was the reason why the script failed. One more thing I still have a problem is I am not able to add the WMI credential for the node which is handled by…

tdanner, From the SELECT statement in the query, it appears that the CredentialOwner is different for the two numbers. The correct number to use is the one with the CredentialOwner = Orion. The other number has the CredentialOwner as the APM. Therefore, I get the answer to my problem now. Thank you very much for the help.

See my other thread how to bypass the SSL certificate error.

tdanner, What is the syntax for the Get-SwisData cmdlet to pull the node data including the custom properties? I tried danofa's code, but it generated an error below: Get-SwisData $swis "Select * FROM NodesCustomProperties cp INNER JOIN NodesData nd on cp.NodeID = nd.NodeID" which results in this error: Get-SwisData : no…

It still not did not work. It could be that my SAM version 6.2.2 has some bug in it. Have you ever got it working?

I used PrimalScript 2012 to edit the script. There should not be any change to the characters in the script. I don't know if this could be the permission issue or not, but the script simply failed at the line where it attempted to add the WMI node. Below is the part of of code I used after I have successfully made the…

tdanner, Thank you for the information. The $credentialId variable from the query has an array of number 8 and 9. When I selected the first one, it generated an error and it did not even let me open the Edit Node page on the Orion Console page. When I select the last one from the array, the WMI credential was added…

Thank you for the response. Currently I add the server node to the Orion SAM 6.2.2 using the swis snapin, but I want to switch to using the Rest API instead because I don't want run the swis snap fro another server or installed the swis snapin on the local computer during the server deployment. I just wan to use the rest…

Per my code above, I already had /CustomProperties in my url - the $swisUri variable already had CustomProperties appended to it. See below. $swisUri = "swis://server/Orion/Orion.Nodes/NodeID=$($NodeID)/CustomProperties" $url = "https://server:17778/SolarWinds/InformationService/v3/Json/$swisUri"

Thank you for the response. I am trying to add the server node to the Orion SAM 6.2.2. The script did not generate any error when I tried to add the custom properties per the instruction listed in the above link, but the custom properties were not added for some reason. Although I was able to create the node using the REST…

There is no curly quotes in the script. The sample script that came with the SDK 1.9 was what I used. I just edited some settings in the script to match my environment and launched the script. The Orion version is 6.1.

tdanner, Thank you for the response. The section of code below is from the CRUD.AddWMINode.ps1 sample script that came with the SDK. #Creating the node $newNodeUri = New-SwisObject $swis -EntityType "Orion.Nodes" -Properties $newNodeProps $nodeProps = Get-SwisObject $swis -Uri $newNodeUri #Getting the Credential ID…

danofa, Thank you for the quick response. I am sorry for being late in responding back to you. Actually, I need to query all the nodes from SolarWinds including built-in and custom properties. I need this information to true up the SolarWinds inventory for my company. I would assume that the syntax you provided is for one…