暂时无法在支持网站上提交享有定期维护的产品表单。 如果您需要我们立即提供帮助，请与技术支持部门联系。 对于由此给您带来的不便，我们深表歉意。
获得即时帮助
完成注册
登录
请求定价
联系销售人员
您已选择一个产品捆绑包。 您能否选择单个产品以便我们更好地满足您的请求。 *
技术支持工程师目前正忙，无法回应您的消息。 如果需要即时服务，请通过我们的服务请求表提交请求。
以下文章可根据您的描述解决您的问题。
The CAS panel groups components that represent current connections on the CAS server on this Exchange 2013 server. This information includes SMTP connection information. SMTP is the standard protocol for Internet Mail.
Exchange 2013 has an updated SMTP protocol and transport stack that does not depend on IIS. Exchange 2013 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:
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 2013: Front-End Transport Service (located in the Client Access Server) and Transport Service (located in the Mailbox Server).
SMTP 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 2013 server.
SMTP is the standard protocol for Internet Mail. Exchange 2013 has an updated SMTP protocol and transport stack that does not depend on IIS. Exchange 2013 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 CAS 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) in order 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 2013 specific functionality such as ECP, EWS, Autodiscover, ActiveSync, OWA, and PowerShell will be affected.
SMTP 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 2013 server to all remote SMTP domains.
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 CAS servers and MBX servers 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 2013 server that can accept mail from other SMTP servers.
SMTP Receive Connectors provide the ability for a Mailbox role to receive email from any other SMTP server on the Internet, other Exchange Server 2013 Mailbox server roles, or other Exchange Server 2013 organizations. Exchange 2013 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 2013 server that can send connections to other SMTP servers.
An SMTP Send connector is required for an Exchange Server 2013 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 Mailbox server can use a Send Connector for routing purposes. The Send Connector properties in the Exchange Management Console show which Exchange Mailbox Servers in the same site can use this Send Connector through which to route mail.
The Mailbox Server (MBX) Transport panel groups components that identify the status of the various transport queues on the mailbox server on this Exchange 2013 server. The Transportation Role is split into two parts in Exchange 2013: Mailbox Transport service and Front-End Transport service.
The Mailbox Transport service runs on all Exchange 2013 Mailbox servers and consists of two separate services:
Exchange 2013 has an updated SMTP protocol and transport stack that does not depend on IIS. Exchange 2013 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.
Inbound Connections
Outbound Connections
EWS Response Time
Shows the average response time for the Exchange Web Services (EWS) which is running on the Exchange 2013 Mailbox Server.
The Exchange Web Services (EWS) provides the functionality to enable Client Applications to communicate with the Exchange 2013 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 2013 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 2013 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 which runs on all CAS servers, 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 2013 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 2013 Mailbox servers or on the other Exchange 2013 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 2013 Mailbox Server currently.
ActiveSync Request Time
Shows the average request time for the ActiveSync on this Exchange 2013 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 2013 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 2013 Mailbox server or on the other Exchange 2013 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 2013 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 2013 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 then routes the message to either a CAS Server role, another Mailbox server in a different AD Site, a mailbox on an Exchange server, or the Unreachable queue.
The Mailbox Server (MBX) Information Store Panel displays key operational metrics for the information store on this Exchange 2013 server. This information includes:
Public Folder
Shows the number of the public folder which are located in the Exchange 2013 Mailbox Server.
In order to take advantage of the high availability and the storage technologies of the mailbox database, Microsoft Exchange 2013 Public Folders have been modernized. The specially designed mailboxes have been used to store both the public folder content and the hierarchy in the Public Folder architecture. There's no a public folder database any more.
In Exchange 2013, the Public Folder replication uses continuous replication model.
The content mailboxes and the high availability for the hierarchy are provided by database availability group (DAG).
Public Folder Mailbox
Shows the number of the public folder mailboxes which are located on the Exchange 2013 Mailbox Server.
The Exchange 2013 Public folder mailboxes contain the information about the hierarchy for a public folder, and the actual content is contained in the Exchange 2013 public folder. When you create a public folder, the first public folder mailbox will become the master hierarchy mailbox. Public folder hierarchy mailbox subsequently created will become a secondary mailbox.
DAG
Shows the name of the Database Availability Group to which this Exchange 2013 server belongs. This is shown for informational purposes only. View the Mailbox Databases drilldown to see more information about the mailbox databases installed on this server.
Replication Service
Shows the Exchange 2013 Replication Service Status.
Store Worker Process
Shows the CPU Utilization of the Microsoft.Exchange.Store.Worker Service in Exchange 2013 Mailbox Server.
In Exchange 2013, the information store is now called Managed Store, which has two processes:
Each database is running under its own process, which isolates the stores issues to a single database. Working with the Microsoft Exchange Replication service, Managed Store manages the mailbox databases and uses the Extensible Storage Engine (ESE) as the database engine. This architectural changes enable faster database failover and better physical disk failure handling.
Mailbox Counts
Shows the total number of mailboxes that reside in all mailbox stores. This is shown for informational purposes only.
Store Service Process
Shows the CPU Utilization of the Microsoft.Exchange.Store.Service Service in Exchange 2013 Mailbox Server.
In Exchange 2013, the information store is now called Managed Store, which has two processes as below:
Mailbox Databases
Shows the percentage of disk space consumed by the mailbox stores on this server. This also shows how much of the server disk consumption is caused by mailbox store consumption versus other data.
Transaction Logs
Shows the total percentage of disk space consumed by the transaction logs on this server. It can be used to quickly assess how much server disk is consumed by transaction log data versus other data on the Exchange server.
The Subsystem panel displays components that represent the health of important subsystem features. This information includes:
CPU Usage
Shows the amount of CPU used on this Exchange 2013 server.
System Disk
Shows the percentage of disk usage for the Windows system disk on this Exchange 2013 server.
System Memory
Shows the amount of physical memory (RAM) Windows is using. Physical memory usage can normally remain close to the total amount of physical memory installed on the system unless the amount of physical memory exceeds the amount of virtual memory that Windows is using. Windows normally keeps some physical memory available for immediate use.
Ping Time
Shows the ping time (in milliseconds) from the client (UC Diagnostics) to the Exchange 2013 server.
Top CPU Consumer
Identifies the process that is consuming the most CPU on this Exchange 2013 server.
Top Memory Consumer
Identifies the process that is consuming the most memory on this Exchange 2013 server.
您可以在附属支持站点上查找适用于戴尔*产品*的在线支持帮助。单击“继续”，转至适用于*产品*的正确支持内容和帮助。
The document was helpful.
选择评级
I easily found the information I needed.
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center
Quest Software门户不再支持IE 8、9和10，建议将您的浏览器升级到最新版本的Internet Explorer或Chrome。
要升级到IE 11，请单击此处
要升级到Chrome，请单击此处
如果继续使用IE 8、9和10，您将无法充分利用我们所有出色的自助服务功能。
