Scripting PowerShell Active Monitors
- Last Updated: December 11, 2024
- 2 minute read
- WhatsUp Gold
- Version 2024
PowerShell Active Monitors provide remote access of the monitored device and the ability to leverage the PowerShell modules and .NET libraries installed there.
Keep In Mind
WhatsUp Gold uses a 32-bit (in other words, "x86") PowerShell engine. Only 32-bit PowerShell snap-ins are supported and 64-bit only snap-ins will not function properly. Snap-ins that work on both 32-bit and 64-bit operating systems are configured for 64-bit systems by default and must be manually configured for 32-bit PowerShell engine to function properly with WhatsUp Gold. If you are using additional pollers with WhatsUp Gold, PowerShell must be installed and any desired snap-ins must be registered identically on all poller machines for any PowerShell performance monitors, active monitors, and actions to function properly. Associated errors resulting from failed monitors will appear in the WhatsUp Gold Status Center. Errors resulting from failed actions will display in the WhatsUp Gold Event Viewer.
Remote Connection Requirements
Ensure the following are in place for enabling the WhatsUp Gold machine to connect using PowerShell to the destination (polled) device.
- Windows Credentials. Credentials must be used explicitly using the methods and properties provided by the Context object. HTTPS must be used as transport or polled device must be in TrustedHosts list of the machine where WhatsUp Gold is running.
- Domain and hostname. If you use user's default credentials. To use IP address alone, you will need to specify credentials at PowerShell/WinRM login. (For more info see this WinRM troubleshooting help.)
- Enable-PSRemoting. Enable PowerShell remoting on destination (polled) device. For more information see link to MSDN documentation provided.