PrtgShell module not loaded: ensure the module is visible for 32-bit PowerShell

Hello,

would it be possible to share the script here? Without more details it's hard to pinpoint the reason.

best regards.

If I may guess you are using powershell based sensors which require a custom tool written by Brian Addicks with the name PrtgShell.

Get if from: https://github.com/brianaddicks/prtgshell check out the code, place them in your powershell modules folder, import them and your sensor probably works.

My guess would be that you stuck this into the default PowerShell Module path ( c:\Windows\system32\WindowsPowerShell\v1.0\Modules ). This would make you subject to something I've didn't know exist and could lead to some confusing stuff called File System Redirector: http://msdn.microsoft.com/en-us/library/aa384187%28v=VS.85%29.aspx

This is built in to windows to make 32bit/64bit applications work nicely on the same filesystem. But if you run gci on that folder from x86 powershell and 64bit powershell I bet you get totally different results. In my case, it was a difference of 25 folders not showing up at all in the x86. You have 2 options:

1. Copy your prtgshell folder to c:\windows\SysWOW64\WindowsPowerShell\v1.0\Modules
2. Create a separate folder to store modules in and add it to your x86 (and 64bit for good measure) $env:PsModulePath.

I do the latter, so it's easy for me to find my modules and manage them. Hopefully that helps!