|
|
|
Zenprise Connector for Operations Manager 2007, extends Microsoft System Center Operations Manager 2007 with advanced diagnostic and troubleshooting capabilities.
» Automated Troubleshooting
» Detailed Resolution Plans
» Alert Reduction
» BlackBerry Coverage
» Troubleshooting Examples
|
|
|
|
|
|
|
Many IT organizations document specific troubleshooting procedures to run based on alerts received. These documents ensure that the most common types of problems are quickly resolved without escalation to more senior level experts. Zenprise has taken 5,000+ of these troubleshooting procedures for Microsoft Exchange & BlackBerry and automated them. Whenever alerts are received in Operations Manager 2007, Zenprise automatically executes these embedded troubleshooting procedures to isolate the true cause of the alerts. For more details, » click here
[back to top]
|
|
|
|
|
|
Detailed resolution instructions are embedded directly in the Operations Manager 2007 console. This can allow the level 1 or 2 technical support teams to resolve key issues without escalating to the Exchange or BlackBerry systems administrators. The end result is fewer escalations at inopportune times (e.g., while administrators are sleeping, on vacation, etc.), as well as faster mean time to repairs.
[back to top]
|
|
|
|
|
|
Zenprise can reduce the volume of Operations Manager 2007 alerts by up to 95%. Numerous alerts generated by the same underlying cause are grouped together (a process known as correlation), and a single root cause is identified in the Operations Manager console.
[back to top]
|
|
|
|
|
|
Customers can leverage their investment in the Operations Manager 2007 framework to monitor and troubleshoot their BlackBerry environment. The Zenprise Connector for Operations Manager will identify the root cause to numerous problems, including: cannot send/receive email, cannot schedule meetings, cannot accept meetings, device activation failures, calendar & email reconciliation issues, etc.
[back to top]
|
|
|
|
|
|
This troubleshooting examples list is representative and is far from comprehensive
- Automated Exchange troubleshooting procedures will check for: corrupted or damaged databases, missing or corrupted DLLs, deleted or renamed checkpoint files, corrupt transaction log files, damaged email in mailboxes, mailbox size exceeding limits, SMTP working on cluster, SMTP virtual servers using non-existent or conflicting IP addresses, etc.
- Automated DNS troubleshooting procedures will check for: complete copy of DNS zone on DNS server, missing DSA CNAME for a DC, unresolvable MX records, MX records pointing to CNAMEs, unusually high DNS dynamic update queue lengths, Kerberos records in the wrong domain, missing A records, stale records, abnormally high caching memory, abnormally high number of TCP/UDP requests, etc.
- Automated Active Directory troubleshooting procedures will check for: Recipient Update Service (RUS) stamping attributes incorrectly, missing or damaged RUS, incorrect or missing Exchange servers in RUS, missing A records for Global Catalogue (GC) SRV records, missing PDC SRV records, missing computer accounts for GC servers with SRV records, unavailable domain controller, missing GC in Exchange domain, GCs which cannot perform LDAP queries, missing msExchResponsibleMTAServer attribute, permissions issues, etc.
[back to top]
|
|
|
