All posts written by Tomas Andersson

How to load HP CIM providers in VMware

VMware ESXi 5.0 already comes with many standard CIM providers that makes it possible to start monitoring several counters right away. To enable all vendor specific counters, you will need to load the proper CIM providers. Here we will show how to install HP’s CIM providers on VMware ESXi 5.0.

First, you need to download the “HP ESXi Offline Bundle for VMware for VMware ESXi 5.0” zip file from Then you need to upload the file to a datastore on your host. If you have many VMware hosts to configure, make sure you you upload the file to a datastore that is shared by all your hosts.


Continue Reading…

Monitor almost any hardware platform with the new CIM monitor

With the new CIM monitor, Kaseya Network Monitor has the ability to monitor hardware operational and health states on almost any hardware platform for servers and storage (and even some desktops). You can monitor counters like CPU, Memory, Fans, RAID, PSU and many more using the CIM monitor. Below is a an example list of systems supporting CIM as a method for retrieving operational states.

  • VMWare
  • HP Eva
  • IBM System Storage (DS series)
  • IBM AIX systems
  • NetApp
  • Oracle
  • EMC
  • Fujitsu
  • LSI
  • Symantec
  • Quantum
  • and many more…

CIM (Common Information Model) is an open standard that defines managed elements and the relationships between a common set of objects. This allows consistent management of these elements, regardless of the manufacturer or provider.

CIM is the base of most other DMTF standards (WBEM, SBLIM and SMASH for example) and is also the base for the SMI-S standard for storage management.

Continue Reading…

Monitoring printers with Kaseya Network Monitor

Most printers equipped with a network interface will also have the possibility to enable SNMP for monitoring, and setting traps. With Kaseya Network Monitor, you can utilize both those features, but here we will just cover the monitoring.

We have created a script that takes the values for supply levels (ink, toners, etc.) or the input levels (paper), presents each unit’s utilization in percent and lets you choose a threshold so that an alarm will be set if the utilization goes below the set threshold value.

First, let’s have a look at monitoring the supply levels. In this example, we have set the threshold to 50% meaning that this monitor will set an alarm if any supply unit will go below 50% left.


Continue Reading…

How to use Kaseya to Monitor Remote Desktop Sessions

Want to know what user or process that is using all the CPU or memory on a terminal server? Kaseya Network Monitor can monitor session processes and set an alarm if a user/process hits the set threshold value for CPU or memory. You can either monitor all users and processes created by RDP sessions or monitor a specified process or user. We have created two Lua scripts that will handle this.

The first script (WMI_RDP_Session_Perf_Process.lua) lets you choose between CPU or memory and set a threshold. Optionally, you can set a process name. Important here is that you check the “No account logon” checkbox since it’s using authenticated WMI sessions to the monitored server.

The second script (WMI_RDP_Session_Perf_User.lua) will let you choose CPU/memory, set a threshold and specify an optional username that you would like to monitor. The syntax is DOMAIN\User but for non-domain connected computers, you will need to specify the local computer name (ie. COMPUTERNAME\User).

Normally you would use the default account for the object but you can specify a specific account for the monitor if needed. The credentials will be passed on to the script for authentication. The statistics will save the CPU or memory usage for RDP sessions. The uniqueness with these scripts is that they will only record RDP sessions. No other sessions like console logons or Windows services will be recorded or checked.

Both scripts will show “Test OK” if nothing hits the threshold. If an alarm is set, a message telling that the CPU or memory usage is high will be presented, along with a list of processes with their data, such as CPU/memory usage and owner (the user that created the process).

Check the KB article at for information on how to download the scripts.

Monitoring a Microsoft Failover Cluster

With the last build, we have now released a Lua script that can monitor your Microsoft server cluster. The released version will check for operational status in nodes and shared resources.

Kaseya Network Monitor v4.1 Build 7394 or higher
Microsoft Windows Server 2003/2008 Cluster

Setting up this monitor involves setting up an object that represents the cluster. Testing of individual nodes is also possible but in case the node you are testing against would go down, the script would just fail, not being able to read any values.

Continue Reading…