暂时无法在支持网站上提交享有定期维护的产品表单。 如果您需要我们立即提供帮助,请与技术支持部门联系。 对于由此给您带来的不便,我们深表歉意。
获得即时帮助
完成注册
登录
请求定价
联系销售人员
您已选择一个产品捆绑包。 您能否选择单个产品以便我们更好地满足您的请求。 *
技术支持工程师目前正忙,无法回应您的消息。 如果需要即时服务,请通过我们的服务请求表提交请求。
以下文章可根据您的描述解决您的问题。
In some large enterprises, Database and Web Servers may be managed by a central resource. In order to install MessageStats in these environments, you can distribute the components onto appropriate machines using a Custom Installation. The most common scenario is to use a separate MessageStats Server and additional Task Processor servers.
In this type of deployment, data from the remote Exchange servers is processed by the local task processor. Then the report-ready data is transferred to the MessageStats Server and stored in the database. This minimizes network traffic by eliminating the need to copy all the data from the remote servers.
The MMC Client Console is installed on a MessageStats administrator's workstation or laptop. The administrator can create tasks and view log files, but task scheduling and gathering are carried out at another location with more robust resources.
To install the Report Pack for OWA onto an existing distributed MessageStats environment, use a Custom installation and install according to the following table.
MMC Client Console
OWA MMC Client Console
Adds the OWA components to the existing MessageStats MMC client console
Scheduler Service/Task Processors
OWA Task Processors
Adds the OWA task processor to the existing MessageStats Task Execution Server
Database
OWA Database
Extends the existing MessageStats database schema in order to store OWA Statistics
Reports
OWA Reports
Adds the OWA Reports to the existing MessageStats Reports site
To configure MessageStats to gather OWA data from an Exchange server, the console must be able to enumerate the IIS virtual directories on the Exchange server. This is done by making Remote Procedure Calls (RPC) to the IIS Management API on the server.
If your OWA Exchange server is protected by firewall software from the internal network that includes the MessageStats server, you may need to perform some RPC configuration on your Exchange server. You may also need to open certain ports on your firewall to grant MessageStats access to the remote API.
This appendix provides a procedure that you can use to configure your OWA server and firewall. The procedure assumes that you are using a Microsoft ISA Server as your firewall software. If you are using another firewall solution, the concepts behind the procedure are still valid.
Be sure to back up the registry before you modify it. Ensure that you know how to restore the registry if a problem occurs. For information about how to back up, restore, and modify the registry, see the Microsoft knowledgebase..
There are two parts to the process:
In a default Windows installation, RPC is configured to randomly assign server ports to any port above 1024. It is unwise to open every port over 1024.
The recommended procedure is to configure RPC to use a specific range of ports. Microsoft recommends using ports 5000 and up since ports less than 5000 may be reserved.
Microsoft also recommends that a minimum of 100 ports be opened. Therefore this example shows how to configure RPC on the OWA server to use ports 5000 to 5100.
Ports
MULTI_SZ
5000-5100
PortsInternetAvailable
REG_SZ
Y
UseInternetPorts
您可以在附属支持站点上查找适用于戴尔*产品*的在线支持帮助。单击“继续”,转至适用于*产品*的正确支持内容和帮助。
The document was helpful.
选择评级
I easily found the information I needed.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center
Quest Software门户不再支持IE 8、9和10,建议将您的浏览器升级到最新版本的Internet Explorer或Chrome。
要升级到IE 11,请单击此处
要升级到Chrome,请单击此处
如果继续使用IE 8、9和10,您将无法充分利用我们所有出色的自助服务功能。