Converse agora com nosso suporte
Chat com o suporte

Unified Communications Diagnostics 8.6.3 - User Guide

About Unified Communications Diagnostics Getting Started Using the Management Console Introducing Management Console health tests Health tests available from the Exchange organization node
About the Exchange-based health tests Exchange Server Health Test Prerequisites for Exchange Delivery Health Tests Exchange Internal Server Delivery Health Test Exchange Internal Mailbox Delivery Health Test Exchange External Message Delivery Health Test Exchange Modern Message Delivery Health Test Exchange Storage Health Test Exchange Queue Health Test Internal Outlook Web Access (OWA) Availability Health Test External Outlook Web Access (OWA) Availability Health Test Exchange Replication Health Test Exchange System Health Test Active Directory Account Lockout Health Test Exchange Online Connectivity Health Test Exchange Online Mailbox Logon Health Test Exchange Online Message Delivery Health Test Office 365 Subscription Health Test BlackBerry Server Health Test BlackBerry Message Delivery Health Test Creating test mailboxes for Exchange Adding health sets for Exchange System health tests Configuring Exchange impersonation for the Modern Message Delivery health test Registering UC Diagnostics with the Microsoft Azure portal
Health tests available from the Lync/Skype for Business Environment Resolving Problems with Native Tools Launching the Diagnostic Console from the Management Console Launching UC Analytics from the Management Console Diagnosing Problems using the Diagnostic Console UC Diagnostics: Exchange 2007 Diagnostic Console (Plug In) UC Diagnostics: Exchange 2010 Diagnostic Console (Plug In) UC Diagnostics: Exchange 2013 Diagnostic Console (Plug In) UC Diagnostics: Exchange 2016 Diagnostic Console (Plug In) UC Diagnostics: BlackBerry Diagnostic Console (Plug In) UC Diagnostics: OCS Diagnostic Console (Plug In) UC Diagnostics: Lync 2013 or Skype for Business 2015 Diagnostic Console (Plug In) Reporting Using Web Reports Counters with Non-Zero Alarm Values

Server Roles Panel

The components of the Server Roles panel shows the Exchange 2016 roles that are installed. This information includes:

 
Table 2. Exchange 2016 server roles panel.
Component
Description

MBX

Shows whether the Mailbox role is installed on this Exchange 2016 server. Mailbox servers contain following components:

•
Mailbox databases that process, display, and store the mailbox data.
•
Client access services that handle all the client connections to the Exchange server.
•
Transport services that are used to transfer and route the email messages.
•
Unified Messaging (UM) services that deliver voice mail and related telephony services to mailboxes

Mailbox servers can be organized into back-end clusters that use database availability groups (DAGs).

EDG

Shows whether the Edge Transport role is installed on this Exchange 2016 server. Edge Transport servers handle the following functions:

•
Provide the rules that control mail flow and protect against spam as mail enters and leaves the organization.
•
Process all the external mail flow for the Exchange organization.

Clients Panel

The Clients panel groups components that represent current client connections to this Exchange 2016 server. This information includes:

 
Table 3. Exchange 2016 clients panel.
Component
Description

Outlook

Shows the number of users currently connected to this Exchange 2016 server through RPC over HTTP. In Microsoft Exchange Server 2016, the Outlook Anywhere feature, formerly known as RPC over HTTP, lets clients that use Microsoft Office Outlook to connect to their Exchange servers from outside the corporate network or over the Internet using the RPC over HTTP Windows networking component.

ActiveSync

Shows the number of current secure HTTP connections (HTTPS) that are established from Windows Mobile-based or Exchange ActiveSync-enabled mobile devices to this Exchange 2016 server. ActiveSync is a push-orientated protocol. Data such as user messages, schedules, contact information, and tasks are synchronized over the HTTPS connection.

Web Service

Shows the current number of connections with the World Wide Web Publishing Service (W3SVC) for this Exchange 2016 server. This information can help you determine if your server can handle the current user load.

IMAP4

Shows the number of IMAP4 connections to this Exchange 2016 server. The Client Access services provide IMAP4 access to mailbox data for clients that rely on this protocol.

IMAP4 is an Internet messaging protocol that allows you to access mail on a server or download it to your computer. IMAP4 is designed for an environment where you can log on to the server from a variety of different workstations or across slow links.

The IMAP4 protocol is disabled by default on Exchange 2016 server. If this Exchange server needs to support IMAP4 clients, start the IMAP4 service. Otherwise, leave it disabled for security reasons.

POP3

Shows the number of POP3 connections to this Exchange 2016 server.

POP3 is an Internet messaging protocol that supports simple offline mail processing. POP3 allows you to download e-mail messages from the server and store them locally on a client computer.

By default, POP3 is not enabled. If POP3 is required, start the service. If this Exchange server does not need to support POP3 clients, leave it disabled for security reasons.

UM Clients

Shows the number of voice mail calls that are currently connected to the Unified Messaging Server since the service was started.

Client Access Services Panel

Exchange 2016 has an SMTP protocol and transport stack that does not depend on IIS. Exchange 2016 uses SMTP protocol for server-to-server message delivery within the same Active Directory site or Routing Group, between different Exchange Organizations, and when transferring mail to other email systems. This information includes:

 
Table 4. Exchange 2016 Client Access services panel.
Component
Description

Front-End Transport Service

Shows the CPU Usage for the Front-End Transport Service (in %).

The Transportation Role is split into two parts in Exchange 2016: Front-End Transport Service (part of the Client Access services) and Transport Service (part of the Backend services).

SMTP Inbound Connections

Shows the total number of inbound (recieved) SMTP connections established by other SMTP hosts to this Exchange server. The number of connections represents the sum of all SMTP inbound connections from all remote domains to SMTP Receive Connectors on this Exchange 2016 server.

If the server is an Edge server, the value comes from perfmon. If the server is not an Edge server, value comes from server properties.

Exchange 2016 uses SMTP protocol for server-to-server message delivery within the same Active Directory site or Routing Group, between different Exchange organizations, and when transferring mail to other email systems.

HTTP/Proxy Outstanding Requests

Shows the quantity of concurrent outstanding proxy requests for the Microsoft Exchange HTTP Proxy access.

Avg. Authentication Latency (ms)

Shows the average time spent in authenticating client access requests in the past 200 samples.

Avg. RPC Latency (sec)

Shows the average latency in seconds of RPC requests. Average is calculated over all RPCs since exrpc32 was loaded.

IIS Service

Shows the CPU Usage for World Wide Web Publishing Service (in %).

Exchange Server depends on the Microsoft Internet Information Services (IIS) to connect using HTTP. To keep email communication flowing, the IIS Service must be running properly. If the IIS Service (W3SVC) is down, some Exchange 2016 specific functionality such as ECP, EWS, Autodiscover, ActiveSync, and PowerShell will be affected.

SMTP Outbound Connections

Shows the current number of outbound (sent) SMTP connections to other SMTP hosts. The number of connections represents the sum of all SMTP outbound connections from SMTP Send Connectors on this Exchange 2016 server to all remote SMTP domains.

If the server is an Edge server, the value comes from perfmon. If the server is not an Edge server, value comes from server properties.

Exchange 2016 uses SMTP protocol for server-to-server message delivery within the same Active Directory site or Routing Group, between different Exchange organizations, and when transferring mail to other email systems.

Users at Max Concurrency

Shows the total quantity of the users that attain Maximum Connections Limitation.

Proxy Failure Rate

Shows the percentage of the connectivity related to the failures between the Client Access (frontend) services and the Backend services on the destination Exchange 2016 server in the past 200 samples.

LDAP Search Time (ms)

Shows the time to send an LDAP search request and receive a response (in milliseconds).

Inbound Connectors

Shows the number of SMTP Receive connectors on this Exchange 2016 server that can accept mail from other SMTP servers.

SMTP Receive Connectors provide the ability for Backend services to receive email from any other SMTP server on the Internet, from other Exchange Server 2016 Backend services, or other Exchange Server 2016 organizations. Exchange 2016 Servers can have multiple SMTP Receive connectors with different parameters for availability or performance reasons.

Outbound Connectors

Shows the number of SMTP Send connectors on this Exchange 2016 server that can send connections to other SMTP servers.

An SMTP Send connector is required for an Exchange Server 2016 to send any SMTP email to other SMTP server on the Internet or to any SMTP server within the same Exchange Server organization. More than one Exchange server can use a Send Connector for routing purposes. The Send Connector properties in the Exchange Management Console show which Exchange servers in the same site can use this Send Connector through which to route mail.

Transport Panel

The Transport panel groups components that identify the status of the various transport queues on this Exchange 2016 server. The Transportation Role is split into two parts in Exchange 2016: Mailbox Transport service and Front-End Transport service.

The Transport service runs on all Exchange 2016 Mailbox servers and consists of two separate services:

•
Mailbox Transport Delivery service receives the SMTP messages from the Transport service which is running on the local Exchange 2016 server or other Exchange 2016 servers.
•
Transport Submission service, which runs on the Exchange 2016 server, that connects to a local mailbox database using RPC to retrieve messages.

Exchange 2016 has an updated SMTP protocol and transport stack that does not depend on IIS. Exchange 2016 uses SMTP protocol for server-to-server message delivery within the same Active Directory site or Routing Group, between different Exchange Organizations, and when transferring mail to other email systems.

 
Table 5. Exchange 2016 Transport panel
Component
Description

Inbound Connections

Shows the total number of inbound SMTP connections established by other SMTP hosts to this Exchange server. The number of connections represents the sum of all SMTP inbound connections from all remote domains to SMTP Receive Connectors on this Exchange 2016 server.

SMTP is the standard protocol for Internet Mail. Exchange 2016 has an updated SMTP protocol and transport stack that does not depend on IIS. Exchange 2016 uses SMTP protocol for server-to-server message delivery within the same Active Directory site or Routing Group, between different Exchange Organizations, and when transferring mail to other email systems.

Outbound Connections

Shows the current number of outbound SMTP connections to other SMTP hosts. The number of connections represents the sum of all SMTP outbound connections from SMTP Send Connectors on this Exchange 2016 server to all remote SMTP domains.

SMTP is the standard protocol for Internet Mail. Exchange 2016 has an updated SMTP protocol and transport stack that does not depend on IIS. Exchange 2016 uses SMTP protocol for server-to-server message delivery within the same Active Directory site or Routing Group, between different Exchange Organizations, and when transferring mail to other email systems.

EWS Response Time

Shows the average response time for the Exchange Web Services (EWS) which is running on the Exchange 2016 Mailbox Server.

The Exchange Web Services (EWS) provides the functionality to enable Client Applications to communicate with the Exchange 2016 servers. It also provides the access to much of the same data, which is made available through the Microsoft Office Outlook.

Transport Service

Shows the CPU usage for the Exchange Transport Service (in %).

The Transport service runs on all Exchange 2016 Mailbox servers and is similar to the Hub Transport server role in previous Exchange versions. This service handles all the inside and outside SMTP mail flow for the entire Exchange 2016 organization. Each SMTP message must be categorized and content-inspected in the Transport service before it can be routed and delivered. After the messages are categorized, they are put in a delivery queue to await delivery to the destination.

Unlike Exchange 2010 or earlier, the Transport service does not communicate with mailbox databases directly. That task is handled by the Mailbox Transport service. The Transport service routes SMTP messages between the Front-End Transport service, the Transport service, and the Mailbox Transport service

Transport Delivery Service

This shows the CPU usage for the Exchange Mailbox Transport Delivery service (in %).

The Exchange Mailbox Transport Delivery service runs on all Exchange 2016 Mailbox servers. It is a separate service from the Mailbox Transport service.

The Mailbox Transport Delivery service receives the SMTP messages from the Transport service on the local Exchange 2016 Mailbox servers or on the other Exchange 2016 Mailbox servers. The service uses an Exchange remote procedure call (RPC) to connect to a local mailbox database to deliver the messages. The Mailbox Transport Delivery service does not queue messages locally.

ActiveSync Pending

Shows the number of pending Sync commands on the Exchange 2016 Mailbox Server currently.

ActiveSync Request Time

Shows the average request time for the ActiveSync on this Exchange 2016 Mailbox Server.

This Average Request Time is the average time that elapsed, in milliseconds, waiting for a request to be completed in this Mailbox Server.

Transport Submission Service

Shows the CPU usage for the Exchange Mailbox Transport Submission Service (in %).

The Exchange Mailbox Transport Submission service runs on all Exchange 2016 Mailbox servers. It is a separate service from the Mailbox Transport service.

The Mailbox Transport Submission service uses an Exchange remote procedure call (RPC) to connect to a local mailbox database to retrieve messages. The service submits the messages over SMTP to the Transport service that is running on the local Exchange 2016 Mailbox server or on the other Exchange 2016 Mailbox servers. The service has access to the same routing topology information as the Transport service. The Mailbox Transport Submission service does not queue messages locally.

Unreachable Queue

Shows the number of messages in the transport unreachable queue on this Exchange 2016 server. The Unreachable Queue contains any messages that cannot be routed to their final destination.

Poison Queue

Shows the number of potentially harmful messages on this Exchange 2016 server. Messages that contain content that might be damaging to the Exchange Server system are by default delivered to this Poison Queue and suspended. If messages in this queue are deemed not harmful, message delivery can be resumed, and the message enters the Submission Queue.

Delivery Queue

Shows the number of items in the Transport Mailbox Delivery Queue on this Exchange server. The Mailbox Delivery Queue holds messages that are being delivered to mailbox recipients whose mailbox data is stored on a Mailbox Server Role located in the same site as this Transport server. The next hop for a message in this queue is the distinguished name of the destination mailbox store.

A different mailbox delivery queue exists for each Mailbox server destination. Mailbox delivery queues are created as needed and automatically removed.

Submission Queue

Shows the number of items in the Submission queue. The Submission queue holds messages before they are consumed by the Categorizer which determines what to do with the messages based on information about the intended recipients. After the Submission queue, the Categorizer routes the message to a Mailbox server in a different AD site, a mailbox on an Exchange server, or the Unreachable queue.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação