IT Operations Management (ITOM)

Improve performance with Microsoft Exchange 2013 monitoring with SiteScope 11.24

Improve performance with Microsoft Exchange 2013 monitoring with SiteScope 11.24


Guest post by Katerina Galustyan, Software Engineer. SiteScope CPE & Content Team R&D.


The Microsoft Exchange Base Monitor is a new monitor in SiteScope 11.24 that enables you to monitor the statistics of Microsoft Exchange Server 2010 and 2013. This application monitoring provides improved performance over the existing Microsoft Exchange Monitor, and includes an extended set of performance metrics (over 70 counters).

A faster monitor run is achieved by maintaining the connection to the Exchange Server using a PowerShell pool that reuses the PowerShell process that was created on the first monitor run.


Statistics for this monitor are gathered through “Exchange Management Shell”, a command-line interface (built on Microsoft Windows PowerShell technology) that is used for managing and testing Microsoft Exchange servers and objects.


The Microsoft Exchange Base monitor runs command-lets (cmdlets) to provide health information. You can see cmdlet results in the Dashboard tab for the current monitor.


Learn how you can download HP SiteScope here and improve your agentless monitoring.


SiteScope 11.24 also includes two Microsoft Exchange 2013 Solution Templates for monitoring Client Access and Mailbox server roles:




  • Microsoft Exchange Base monitor enables you to monitor statistics of Microsoft Exchange Server on Windows platforms only.
  • Microsoft Exchange Base monitor requires the Microsoft Exchange solution template to enable it in the SiteScope interface.

Let’s see how we get counters for an Exchange server

Create a new Microsoft Exchange Base Monitor with the following counters:



Enable debug logging for this monitor (in “Logging Settings” of the current monitor):



Run the monitor. After getting the run results, click “View Log” in “Logging Settings ”.

Let’s see how this monitor works.

At first it gets the PowerShell process, which is connected to the current Exchange server. After that, it runs cmdlets, receives their output, parses it and gets processed counters.

Let’s see how counters are obtained for some of the cmdlets:


Counters of other cmdlets are obtained in the same or similar way.


For more details on monitoring Microsoft Exchange Server, see the SiteScope documentation here.

  • infrastructure management
0 Kudos
About the Author


This account is for guest bloggers. The blog post will identify the blogger.