Since Windows has been default 64bit for a while and PRTG using PowerShellx86 for executing the EXEXML-scripts this causes problems when using certain PowerShell modules like failoverclusters when monitoring the witness-state of a SQL HA-cluster.
Now I have to use unsupported third-party applications like PSx64.exe from PRTG family, or I have to trick around is using command-blocks. This adds extra complexity and opportunities for failure.
Could you please add the possibility to switch the probe to use the 64-bit version of PowerShell for running EXEXML scripts?
I currently struggle as well, not for the first time. Using StorageQoS Powershell and CIM sessions. With a normal x64 PowerShell it takes a second to execute and get a result. No matter which option for 32-to-64 I tried, the script takes at least x3-5 longer and the probe needs more CPU. @Paessler: Come on guys, it's 2023 - switch the probe to x64 as well please.
Aug, 2023 - Permalink