Prior to version 10.7.0, GSX Monitor collects SMTP statistics using remote WMI queries. Unfortunately WMI sometimes returns corrupted values (Microsoft has issued several Windows hotfixes to address this issue).
In this article, we detail why you see such a behaviour in GSX Monitor and give you more information on how to work around this problem from both Microsoft and GSX stand points.
- When analyzing consolidated or real-time Exchange SMTP statistics, the values reported are not accurate. The SMTP counters are much higher than the real traffic values.
- The Exchange Statistics view in GSX Monitor displays extremely high SMTP counters values in Hub section for Exchange 2010.
- SMTP Statistics High.
How to Solve the Issue
If you prefer patching your Microsoft server rather than upgrading GSX Monitor, please refer to the Microsoft related articles listed below.
If patching your server is not an option for you, you should upgrade GSX Monitor to version 10.7.0 or above. You can download the latest version here.
Since version 10.7.0, GSX Monitor is using remote PowerShell exsclusively to collect SMTP statistics in order to work around such remote WMI problems.
Microsoft Related articles
- The WMI service and the WMI providers stop responding when you use WMI performance classes to monitor performance on a computer that is running Windows 7 or Windows Server 2008 R2
- The WMI process stops sending events to WMI clients from a Windows 7-based or Windows Server 2008 R2-based server