Knowledge Base FAQ Items

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\ActiveXperts\Network Monitor\Server\Trace\ThreadPowerShell001 For instance: c:\powershell00.log c:\powershell01.log After that, restart the service. Then, all PowerShell operations will be wr...
Network Monitor > Monitoring Powershell

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, simply because PowerShell cannot deal with long filenames when used from the command line. Sometimes, 8dot3 naming convention is DISABLED on the file system, and PowerShell scripts will not work, endin...
Network Monitor > Monitoring Powershell