ActiveXperts Network Monitor KB - Monitoring Powershell

'Monitoring Powershell' Knowledge Base Articles

Q6960010	When I run a Powershell-based check. I get an error: "Execution of PowerShell scripts is disabled on this system."
	You must allow Powershell scripting on the machine that has ActiveXperts Network Monitor running. Read more on allowing Powershell scripting here:activexperts.com/support/network-monitor/online/powershell/ Please note that allowing Powershell on 32-bit operating systems is different from 64 ...
Q6960020	We use PowerShell scripts to monitor several servers. Is there a way to see how the PowerShell interpreter is invoked by the Network Monitor Engine?
	You can turn on PowerShell logging for the Network Monitor Engine. To do so, enter a valid file name in the following registry entries (there's a registry entry for each PowerShell thread/subprocess): HKLM\Software\ActiveXperts\Network Monitor\Server\Trace\ThreadPowerShell000 HKLM\Software ...
Q6960030	When a PowerShell is executed by ActiveXperts Network Monitor, I get the following error: "The term 'ps1' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again". What is the problem?
	Under the hood, ActiveXperts executes all PowerShell checks by executing a command like this: cmd /q /c "C:\Windows\System32\WindowsPowerShell\v1.0\PowerShell.exe "C:\PROGRA~1\ACTIVE~1\NETWOR~1\scripts\MONITO~2\CPU.PS1" As you can see, a 8dot3 naming convention is used for powershell files ...

---

If you cannot find an answer to your question(s) in our Knowledge Base, or if you need additional information or assistance, please contact our Customer Support using our Contact Support Form