Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

202.1 SAM Powershell Monitors no longer work - and work around doesnt work either

Upgraded to 2024.1, all of my PowerShell monitors no longer work, they say "wrong password" its the same password and script that has been working for months.

Previously, i would update the config file (SolarWinds.APM.Probes.dll), but this doesn't work anymore either.

Release notes say that they removed the need for that manual work around but now nothing is working at all

01256771, 01266011, 01276421, 01464931

After an upgrade, PowerShell and App Insight monitors are functional. Users no longer need to manually update a configuration file to use these monitors.

SAM 2024.1 release notes (solarwinds.com)

Find more posts tagged with

Accepted answers

acurrent

I received the response below, and it resolved my issue. One outstanding issue were the components were stuck in unknown for hours. The only way i found to resolve it was to individually test every powershell component and click submit. The statuses then updated.

Please follow below steps and let me know if it helps to resolve issue.

SolarWinds Platform 2022.3 - 2023.4

The following setting will need to be manually added after each software upgrade.

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

SolarWinds Platform 2024.1

Starting in 2024.1, a new setting was added and will be preserved after future upgrades.

Log in to the Orion Web Console using an account with administrative privileges.
To access Advanced Configuration Settings, copy /Admin/AdvancedConfiguration/Global.aspx.
Paste it into your browser address bar, after /Orion, as shown here: http://YOUR_SERVER/Orion/Admin/AdvancedConfiguration/Global.aspx
Press Enter.
Search the PowerShell in the Search Bar
Find the APM.WMI.Setting "UseLegacyPowerShellImpersonation"
Select the checkbox
Click Save

All comments

acurrent

SolarWinds Platform 2022.3 - 2023.4

The following setting will need to be manually added after each software upgrade.

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

SolarWinds Platform 2024.1

Starting in 2024.1, a new setting was added and will be preserved after future upgrades.

Log in to the Orion Web Console using an account with administrative privileges.
To access Advanced Configuration Settings, copy /Admin/AdvancedConfiguration/Global.aspx.
Paste it into your browser address bar, after /Orion, as shown here: http://YOUR_SERVER/Orion/Admin/AdvancedConfiguration/Global.aspx
Press Enter.
Search the PowerShell in the Search Bar
Find the APM.WMI.Setting "UseLegacyPowerShellImpersonation"
Select the checkbox
Click Save

adam.beedell

I think you're talking about the legacypowershellimpersonation setting, it's on the advanced settings page now, there's a few threads on it using that as a search query.

Wrong password is nor usually the message though. Could be.

adam.beedell

(whatever it's set to, try the opposite setting and see if it's all suddenly fixed)