2022.4 Upgrade: Remote PowerShell Broken

We upgraded to the 2022.4 platfrom from 2020.2.6 (had all of the hotfixes applied). Post upgrade we noticed some failurs on our PowerShell monitors. We received the error:

PowerShell script error. Starting a command on the remote server failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.

This occured across multiple polling engine and various application templates. The known items at this time are:

Component: Windows PowerShell Monitor

Preferred Polling Method: Agentless

Execution Mode: Remote Host

We have other local host based monitors that are working with no issue. Some of them make remote calls as well. So communication seems to be good.

Find more posts tagged with

Accepted answers

SteveK

Received an update from Support and made the following changes which appears to correct the issue. These changes were done on the APEs and the Primary server.

File: %SolarWinds Install Directory%\SolarWinds\Orion\SolarWinds.APM.Probes.dll.config

Backup the file above

Launch Notepad.exe in administrator mode and load up the file

Find the line: <add key="UseLegacyPowerShellImpersonation" value="false"

Change the line to: <add key="UseLegacyPowerShellImpersonation" value="true" />

Restart Orion Services

All comments

SteveK

Received an update from Support and made the following changes which appears to correct the issue. These changes were done on the APEs and the Primary server.

File: %SolarWinds Install Directory%\SolarWinds\Orion\SolarWinds.APM.Probes.dll.config

Backup the file above

Launch Notepad.exe in administrator mode and load up the file

Find the line: <add key="UseLegacyPowerShellImpersonation" value="false"

Change the line to: <add key="UseLegacyPowerShellImpersonation" value="true" />

Restart Orion Services

adam.beedell

I suspect i've got the same sort of problem.

Know what the difference between legacy powershell impersonation and i guess "current" powershell impersonation is in this scenario?

adam.beedell

This fix did it for me.

SteveK

The response I have received from support

1. What change occurred to the PowerShell execution? - Nothing changes the execution of PowerShell based on the Development Case.
2. Is this issue currently in the pipeline to get resolved without the work around? Yes, they are working on the issue and it should be resolved in the future update of the product base on the Development Case.
3. Is there any changes we need to make to our servers so that we can get away from “LegacyPowerShellImpersonation”? What happens is that the config file that mentions in the case has changed the value from the original config. From the old version of Orion 2020.2.6, the value is "True" in the upgrade version it was set as "False". That way the work around is to change the value from false to true, as this is the setting before, the application is the one using the LegacyPowerShellImpersonation in your Server, so currently there is no information how your server can get away from the "LegacyPowershellImpersonation", as the application is using this as well.

ascoyne

This fixed it for me too. SolarWinds support was not aware of this known issue. ThankfullyThwack came to the rescue! Thank you @SteveK

mtautfest

Thank you for posting this. I had the same issue and your solution fixed it.

rfackrell

I took all this awesome info and made a simple script to do the work.
I shared it here:
Fix SAM PowerShell Remoting - 2022.4 - Scripts - The Orion Platform - THWACK (solarwinds.com)

Kita

Starting in 2024.1, this option was added to the Advanced Settings:

https://support.solarwinds.com/SuccessCenter/s/article/SAM-Powershell-not-working-after-2022-3-Upgrade?language=en_US

jonathon.privett

For 2024.1 and later:

support.solarwinds.com/.../SAM-Powershell-not-working-after-2022-3-Upgrade

Quick Links

All Categories
Recent Posts
Activity
Unanswered
Groups
Help
Best Of