Support Portal

Exchange Servers - Functionality 35

• Client Access (Exchange 2013 & 2016 only) - Procedures for manually verifying monitoring results
• Server Component States (Exchange 2013 & 2016 only) - Procedures for manually verifying monitoring results
• Queue Status - Procedures for manually verifying monitoring results
• CAS Load Distribution Status - Procedures for manually verifying monitoring results
• Managed Availability Escalations - Procedure for manually verifying monitoring results

View all 35

Exchange Servers - Network 4

• DNS Status - Procedures for manually verifying monitoring results
• Active Directory Status - Procedures for manually verifying monitoring results
• Mailscape Connectivity Status - Procedures for manually verifying monitoring results
• AD Replication Status - Procedures for manually verifying monitoring results

Exchange Servers - Disk Space 1

• Database Size & White Space Status - Procedures for manually verifying monitoring results

Exchange Servers - Services 1

• Service Status - Procedures for manually verifying monitoring results

Exchange Servers - Backup 3

• Backup - Procedures for manually verifying monitoring results
• You cannot restore an individual database by using Windows Server Backup in Exchange 2010 or in Exchange Server 2007
• Event 4356 is logged when you try to restore a database by using a backup in an Exchange Server 2013 environment

Exchange Servers - Resources 2

• Resources - Troubleshooting: The resource indicator for a specific server may not display any statistics or results.
• The memory usage of the MSExchangeRepl.exe process keeps increasing when you perform a VSS backup on Exchange Server 2010 databases

Exchange Namespaces - CAS Health 5

• Exchange Namespace Configuration (Exchange 2013 & 2016 only)
• HTTP 500 Internal Server Error when logging into Exchange 2013 Exchange Control Panel (ECP)
• Exchange 2013 Troubleshooting: Error 500 when login ECP and OWA
• Event ID 1309 and you can't access OWA and ECP after you install Exchange Server 2016 or Exchange Server 2013
• "HTTP 400 Bad Request" error when proxying HTTP requests from an Exchange Server to a previous version of Exchange Server

Exchange Namespaces - DAG Status 5

• Network Health - Procedures for manually verifying monitoring results
• Active Preference - Procedures for manually verifying monitoring results
• Database Redundancy - Procedures for manually verifying monitoring results
• DAG Network Shows Misconfigured In Exchange 2013 Server
• DAG network "Misconfigured" error in Exchange Server 2016