This ZenPack is developed and supported by Zenoss Inc. Commercial ZenPacks are available to Zenoss commercial customers only. Contact Zenoss to request more information regarding this or any other ZenPacks. Click here to view all available Zenoss Commercial ZenPacks.
Monitoring for Microsoft Exchange Server Devices.
This ZenPack provides support for monitoring Microsoft Exchange Server. Monitoring is performed using the Windows Remote Management (WinRM) to collect Perfmon data.
The features added by this ZenPack can be summarized as follows. They are each detailed further below.
The following components will be automatically discovered through the Windows server address, username and password you provide. The properties and relationships will be periodically updated by modeling.
Attributes: Name, Version, Is Client Access Role, Is Mailbox Role, Is Hub Transport Role
Attributes: Name, Is Mailbox Database, Is Public Folder Database
Performance counters are collected using the PowerShell Get-Counter Cmdlet within a remote shell (WinRS). The following metrics will be collected every 5 minutes by default. Any other Windows Perfmon counters can also be collected by adding them to the appropriate monitoring template.
There are thresholds associated with several of the collected counters in the above templates.
activesync_current_requests - Between 50 and 100
oab_download_tasks_queued - Less than 0
calendar_attendant_requests_failed - Less than 0
mailbox_average_document_indexing_time - Less than 30000
active_mailbox_delivery_queue_length - Less than 250
active_remote_delivery_queue_length - Less than 250
To use the ZenPack, add the zenoss.winrm.WinExchange modeler plugin to an existing Windows device and run the modeler. For a new device, follow the directions for adding a new device using the Microsoft Windows ZenPack
Note: The monitoring user must be a domain user.
Note: If monitoring Exchange with a non-administrator user, the user must be a member of the Active Directory group "View Only Organization Management" for 2010 and later installations.
The first step in troubleshooting any monitoring issues is to scan the zenpython log for errors. Most issues can be solved by troubleshooting the Windows ZenPack.
There are currently no logon servers available to service the logon request
If you see this error during modeling, check the NETBIOS name against the users domain name. If they are not the same then use the zExchangeUser/zExchangePassword configuration options.
The WinRM client received an HTTP status code of 403 from the remote WS-Management service
If you use WinHTTP proxy on your exchange server and see this error during modeling, check zExchangeNoProxy property and set it to true.
This ZenPack provides additional support for Zenoss Analytics. Perform the following steps to install extra reporting resources into Zenoss Analytics after installing the ZenPack.
You can now navigate back to the Microsoft Exchange ZenPack folder in the repository to see the following resources added by the bundle.
: Microsoft Exchange Domain
Domains can be used to create Ad Hoc views using the following steps.
When combined with the Zenoss Service Dynamics product, this ZenPack adds built-in service impact capability for services running on Microsoft Windows. The following service impact relationships are automatically added. These will be included in any services that contain one or more of the explicitly mentioned entities.
The Windows server is impacted by the Exchange Server.
Installing this ZenPack will add the following items to your Zenoss system.
ClientAccessRole (in /Server/Microsoft)