Hi,
I am running a powershell script which uses the office365 Connect-MsolService cmdlet.
When running the script manually on the probe server, it runs fine. I run this on the same user account as the PRTG sensor does. The cmdlet is obviously installed.
When running the script via the EXE/Script sensor, it stays the cmdlet is not recognized as the name of a cmdlet, function, script file, or operable program.
What might be causing this?
Article Comments
Hello Tony,
Thank you very much for your contact and please apologize the long delay.
The issue is most likely caused, due to the fact that you've tested the script with a 64-bit instance of Powershell. Please note that PRTG uses the 32-bit instance of Powershell per default.
This being said, please test your script in a x86 environment and also consider trying to run the 64-bit version for PRTG using this workaround.
Best regards,
Sebastian
Jul, 2019 - Permalink
Hello Tony,
Thank you very much for your contact and please apologize the long delay.
The issue is most likely caused, due to the fact that you've tested the script with a 64-bit instance of Powershell. Please note that PRTG uses the 32-bit instance of Powershell per default.
This being said, please test your script in a x86 environment and also consider trying to run the 64-bit version for PRTG using this workaround.
Best regards,
Sebastian
Jul, 2019 - Permalink