Diagnosing Problems Within BES, Exchange Environments
On the infrastructure side, Zenprise provides invaluable assistance in diagnosing problems within or between the BES and Exchange environments. Zenprise can detect problems like hung threads, MAPI errors or high disk usage that could bottleneck mail delivery. The service monitor also helped quickly identify big problems, within a minute notifying administrators when I killed a BES process or disabled the network adapter on the Exchange server. Zenprise offers outstanding reporting capabilities and the ability to create highly customized performance charts for the BES and Exchange environments. Among the cascade of available reports, I could generate usage trending reports, root cause analyses and system configurations, or I could examine the mean time to resolutions to evaluate performance against a service-level agreement.However, administrators should know that Zenprise could have a management and reporting issue at the largest scale. Each Zenprise server is managed separately via its own iteration of the Zenprise Console, and the back-end Zenprise databases will likewise be distinct. While global companies could isolate Zenprise server instances and management responsibilities according to region, I'd like to see Zenprise develop a manager of managers console to aggregate Zenprise management and reporting for the largest companies that want to keep ultimate control under one roof.
For performance charts, I could examine CPU, disk or RAM performance across a selection of servers (over an hour, day, week or month), or I could drill down into a vast array of application-specific metrics, anything from message latency through the BES system to the recent performance of the OWA Web mail interface.
eWEEK Labs Senior Technical Analyst Andrew Garcia can be reached at firstname.lastname@example.org.