Replace CIM/WMI calls for wrapper function for proper error/permission handling

[LordHepipud]

Author: @LordHepipud

This issue is a direct reference to #80 of the PowerShell Framework

Tasks: @LordHepipud

• Code review
• Testing
• Update developer guidelines for new handling

Tasks: @Crited

• Testing

[pakyg]

Hi, updating to the latest version of the Plugins, I was presented with this error output:

Get-IcingaWindowsInformation : The term 'Get-IcingaWindowsInformation' is not
recognized as the name of a cmdlet, function, script file, or operable
program.

How can I fix it?
Thanks so much

[yhabteab]

Hiii @patrickgidiuli, When you open a new powershell instance you will either need to run Use-Icinga to load all Icinga related modules or you can run the commands as follows. icinga { Your Commands here; }

Hope this will help you!

Best,
YH

[pakyg]

Hi @Yonas-net ,thanks for the reply. I can see the error output from IcingaWeb .. From the Powershell window everything works.

[yhabteab]

If you use icinga-powershell-plugins release tags it will not work because these new features will be released on Monday. But if you have the branch master it should work. Is the user who runs the checks in Icinga Web 2 identical to the user who tested the checks locally?

[pakyg]

@Yonas-net Yes the user is the same, even with the Master version, the same error output occurs .. Do you recommend waiting for Monday for the final release? this is the first time that I have this problem, with the previous version everything worked great..

Thank you very much!
PG

[yhabteab]

Waiting for the final release on Monday would be an option but you also have to check out the master in your icinga-powershell-framework repo. Because Get-IcingaWindowsInformation is in the framework and unless you check out the master it will not work. And if none of this helps you, please contact us again.

Best,
YH