PoSh Based Component Monitor Issues

SmittySmith

I've run up against a seeming unmovable wall while using PoSh based component monitors and I'm seeking some THWACK knowledge.

Here's the situation.  I have several application templates that use Windows PoSh monitoring components.  The Application templates used to work great.  But now they don't work at all.  The components are configured to "run on remote host" .  I'm seeing two different results when the application template runs against the target node(s).

1. "The security database on the server does not have a computer account for this workstation trust relationship"

2.  "Logon failure: the user has not been granted the requested logon type at this computer"

#1 occurs when I try to run the application template against a node in a trusting domain, Polling engine is in domain A and target node is in domain B

#2 occurs when I try to run the application template against a node in the same domain

The service account used is a member of the local Admins group and that group is allowed log on locally and logon on using RDS.  As I mentioned these PoSh components used to work without issue.  Also note that all other "non-PoSh" based application templates work without error using the same service account.  I've worked with out networking and firewall teams and we are not seeing any blocks/denies.

Any insight on this issue would be greatly appreciated

acurrent

YES.... I had these exact errors.

In the SAM 2022.3 release notes, there's a work around listed for issues with the powershell component authentication. It doesnt cite these specific errors youre getting, but i decided to try it out anyway and it resolved these issues for me

1. 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

2. In line: <add key="UseLegacyPowerShellImpersonation" value="false" /> change value to <add key="UseLegacyPowerShellImpersonation" value="true" />

Source:
SAM 2022.3 Release Notes (solarwinds.com)

I also posted my issue on thwack, and listed this as the resolution:
(+) Powershell script works with credentials and remote execute from the polling engine, but fails once added to a component moniotor. Component ErrorThe security database on the server does not have a computer account for this workstation trust relationship - Forum - Server & Application Monitor (SAM) - THWACK (solarwinds.com)