After uninstall other programs with own PowerShell-Modul (e.g. MS SCOM), Icinga-PowerShell-Framework doesn't work

[stevie-sy]

Because of using more and more Icinga Agent on our Windows servers incl. more and more checks from the icinga-PowerShell-Framework, my colleagues from the server admin uninstall SCOM where it isn't needed anymore.

Here we observe that after uninstalling it on Windows 2012R2 servers, every check quits with following output:

On our servers with Windows 2016 and 2019 everyhting is fine.

background information:
SCOM install also a PowerShell module. But not in the standard directory C:\Program Files\WindowsPowerShell\Modules. It installs it under C:\Program Files\Microsoft Monitoring Agent\PowerShell\Microsoft.MonitoringAgent.PowerShell

We don't know what happens during (un)installation because SCOM is closed source. But something is happening with PowerShell and as result this strange behavior. There are also no eventlogs.

The only thing which helps is to restart the icinga daemon.

We want to mentioned it but we think also this isn't something what could be really fixed. So maybe it's something for your knowledge base.

[LordHepipud]

Thank you for the report!

If you restart the Icinga Agent, everything works again as expected?

[stevie-sy]

yes

[stevie-sy]

Do you need further information to put this into the KB in your docs?

[tbauriedel]

ref/NC/761567