This article applies as of PRTG 22
Running PowerShell notifications or EXE sensors with Powershell scripts, which PowerShell version is used by PRTG (32-bit, 64-bit) and how do I have to configure the PowerShell Execution Policy
PowerShell 32-Bit and 64-Bit and Execution Policy
Even on a 64-bit Windows system, PRTG starts the 32-bit version of PowerShell. Because of that, the Execution Policy of the 32-bit PowerShell must be correctly set. It is independent from the 64-bit Execution Policy.
Find the 32-bit version of Windows PowerShell here:
%SystemRoot%\syswow64\WindowsPowerShell\v1.0\powershell.exe
Execute the following command from a Windows command line to enable PowerShell scripting:
%SystemRoot%\SysWOW64\WindowsPowerShell\v1.0\powershell.exe "Set-ExecutionPolicy RemoteSigned"
For information about signing PowerShell scripts and the Execution Policy for scripts, see the following external resources:
More
- My PowerShell sensor returns an error message. What can I do? See section "Unauthorized access".
- Force 64-bit PowerShell?
Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.