You are here
Windows 2008 WMI - Base Opspack
Windows Server is a brand name for a group of server operating systems released by Microsoft. Windows Server also includes the popular series of server software hosting a range of software and services such as Microsoft IIS, Exchange and Hyper-V.
What Can You Monitor
Opsview Monitor’s Microsoft Windows Server Opspack gives you the power to monitor the status of your server checking all common metrics such as: * Windows Checks: Allows you to monitor features such as CPU, Disk Queue, Paging File, Physical Memory, Windows Events, Windows Drive * Event Logs: Monitoring of Security, Application, and System Events * WMI Agentless: Monitoring of DNS, IIS, Exchange, Terminal Services and more.
|C Drive||Check C Drive without agent using WMI|
|CPU||Check CPU without agent using WMI|
|CPU Queue length||Check CPU queue length without agent using WMI|
|CPU info per process||Check details of a process per cpu usage|
|CPU usage per process||CPU usage per process using WMI|
|File size||Check a files size without agent using WMI|
|I/O counters||Check server IO counters without agent using WMI|
|LAN status||Check Network without agent using WMI|
|Memory usage||Check memory usage without agent using WMI|
|Memory usage per process||Check memory used by a process using WMI|
|Network info||Check basic net info using WMI|
|OS and SP Info||Check OS and Service Pack info using WMI|
|Process status||Check status of a process using WMI|
|Service status||Check a service is running using WMI|
|Uptime||Check system uptime without agent using WMI|
|Users Folder size||Check a folder size without agent using WMI|
|Users Status OK||Check users without agent using WMI|
Windows WMI - Base Agentless Opspack
Windows WMI Agentless Opspacks allow you to monitor the status and various performance metrics for a range of Microsoft services such as DNS, Exchange, IIS, Terminal Services and more, without the need of installing an agent on your remote host.
What Can You Monitor
This Opspack allows you to monitor the status of your windows machines, with service checks that cover CPU, Disk, Memory and Network as well as the status of processes and services.
|C Drive||Check status of the C Drive|
|CPU||Check CPU usage|
|CPU Queue length||Check CPU queue length|
|CPU info per process||Check details of a process|
|CPU usage per process||Check CPU usage of a process|
|File size||Check a files size|
|I/O counters||Check server IO counters|
|LAN status||Check Network status|
|Memory usage||Check memory usage|
|Memory usage per process||Check memory used by a process|
|Network info||Check basic network details|
|OS and SP Info||Check OS and Service Pack details|
|Process status||Check status of a process|
|Service status||Check status of a service|
|Uptime||Check system uptime|
|Users Folder size||Check folder size|
|Users Status OK||Check users status|
Setup and Configuration
To configure and utilize this Opspack, you simply need to add the 'OS - Windows Server 2008 WMI - Base' Opspack to the host, and specify the variables WINCREDENTIALS and WINPROCESS.
Step 1: Add the host template
Step 2: Add and configure the WINCREDENTIALS and WINPROCESS variables
Step 3: Reload and view the Windows Server 2008 WMI - Base statistics
- To use Windows WMI Agentless Opspacks, the remote windows host must first be configured to allow WMI queries to be run. See: Monitoring Services with WMI
Setup and Configuration
To configure and utilize this Opspack, you simply need to add the 'OS - Windows WMI - Base Agentless' Opspack to your Opsview Monitor system.
Step 1: Import the Opspack
Download the os-windows-wmi-base-agentless.opspack file from the Releases section of this repository. Navigate to Host Template Settings inside Opsview Monitor and select Import Opspack in the top left corner.
Then click Browse and select the os-windows-wmi-base-agentless.opspack file. Click Upload and then click Import when the file is uploaded.
Step 2: Add the host template
Step 3: Add and configure the host variables required for this host
|WINCREDENTIALS||Used for authenticating with the remote host. The value is not used and therefore can be set to anything. Override the username and password with the credentials to be used for authentication with the remote host.|
|WINPROCESS||The name of the process to monitor. The value is the name of the process to monitor. You can have multiple host variables to check the status of each process individually.|
|WINSERVICE||The name of the service to monitor. The value is the name of the service to monitor. You can have multiple host variables to check the status of each service individually.|
|WMI_NETWORK_INTERFACE||The name of the network interface to monitor. The default is set to '.' which provides metrics for all network interfaces. Override this if you would like to monitor a network interface individually.|
Step 4: Reload and the system will now be monitored
ODI-604 Release Opspacks to GitHub
Initial upload of existing Opspacks to GitHub
ODI-2070 Rename Microsoft Opspacks
With the aim of maintaining consistency across Opsview Monitor, this Microsoft® monitoring-related Opspack and related Host Template and Service Checks have been renamed.
|Original Host Template Name||New Host Template Name|
|OS - Windows Server 2008 WMI - Base||OS - Windows WMI - Base Agentless|
This won't have any negative impact on your system when you manually install this opspack or are upgrading to Opsview Monitor 6.0 (November 2018 release). You will see both sets of Host Templates in the system. Nevertheless, to avoid confusion, we recommend removing the templates carried over from a previous Opsview Monitor version.
ODI-1154 Release Opspacks for Opsview Monitor 6.0
Initial release of Opspack to work with Opsview Monitor 6.0