"Username or password incorrect" in bulk across accounts known to be good after upgrade to 2022.4

Hi Team,

I've got a load of identical servers in different domains who all are no longer able to run a custom powershell monitor after patching. I know there wasnt several different passwords changed during my change window.

I know these accounts are OK, because the same accounts are used for NPM monitoring, which is running fine. Also the logic of the monitor shouldnt really respond in this way to a failed account.

Something's broke. Anyone had the same?

Find more posts tagged with

broke

sam

PowerShell

Accepted answers

acurrent

yes... try this:

Find and open the following with notepad or other text editor (may need to run as administrator): Program Files\SolarWinds\Orion\SolarWinds.APM.Probes.dll.config
In line: <add key="UseLegacyPowerShellImpersonation" value="false" />change value to <add key="UseLegacyPowerShellImpersonation" value="true" />.

All comments

acurrent

yes... try this:

Find and open the following with notepad or other text editor (may need to run as administrator): Program Files\SolarWinds\Orion\SolarWinds.APM.Probes.dll.config
In line: <add key="UseLegacyPowerShellImpersonation" value="false" />change value to <add key="UseLegacyPowerShellImpersonation" value="true" />.

adam.beedell

@acurrent Do you know what's going on here?

-1) What is legacy vs non-legacy powershellimpersonation?
-2) how are we to use credentials in the non-legacy format?
-3) The new method is implimented for security reasons, what are those reasons? - What is the impact of switching back to the presumably flawed method?

SteveK

Hi Adam, I updated my post here: (+) 2022.4 Upgrade: Remote PowerShell Broken - Forum - Server & Application Monitor (SAM) - THWACK (solarwinds.com)

So the response I got from support was that in 2020.2.6 and earlier, the value in the config was already set to "True." In 2022 it was switched to false. So essentially this work around is to default the value back to the previous setup.