This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Connect-SWIS Failing in Powershell with -Certificate Credential

We recently moved our Orion platform to a new server. On the old server we had scripts running successfully using Connect-SWIS with the -Certificate option to use the Orion certificate on the server to connect.

Since moving to a new server the scripts cannot authenticate and throw "The credentials supplied to the package were not recognized" errors.

Solarwinds Support said they won't help with anything SDK related. Can anyone offer insight on why these are failing on a new server? I thought the -Certificate switch used the Orion generated certificate on the server to authenticate. I can't see why that would fail.

Parents
  • Which version of the SwisPowerShell module have you installed?

    Get-Module -Name SwisPowerShell -ListAvailable
    
        Directory: C:\Users\[Path]\PowerShell\Modules
    
    ModuleType Version    PreRelease Name                                PSEdition ExportedCommands
    ---------- -------    ---------- ----                                --------- ----------------
    Binary     3.0.309               SwisPowerShell                      Desk      {Connect-Swis, Get-SwisData, Get-SwisOb…

  • The same version you have in your code block. The module was installed with

    Install-Module -Name SwisPowerShell

    in an admin session.

  • And which version of the Orion Platform are you trying to connect to?

    $SwisConnection = Connect-Swis -Hostname localhost -Certificate
    Get-SwisData -SwisConnection $SwisConnection -Query "SELECT Caption, IPAddress FROM Orion.Nodes"

    Caption             IPAddress      
    -------             ---------      
    KMSORION01v         192.168.21.65  
    KMS-NAS             192.168.4.20   
    pi-hole01           192.168.4.7    
    kmssql01v           192.168.21.63  
    Office AP           192.168.0.123  
    KMS-ASUS            192.168.21.20  
    unifi.kmsigma.local 192.168.0.1    
    pi-hole02           192.168.4.8    
    folding             192.168.21.67  
    Work Laptop         192.168.199.209
    Living Room AP      192.168.0.72

    This is running against an Orion server running 2020.2.5.

  • 2020.2.4.

    I'll try updating to 2020.2.5 and see if that makes any difference.

Reply Children
No Data