Submitting forms on the support site are temporary unavailable for schedule maintenance. If you need immediate assistance please contact technical support. We apologize for the inconvenience.
라이브 도움말 보기
등록 완료
로그인
가격 산정 요청
영업 담당자에게 문의
제품 번들을 선택했습니다. 귀하의 요청에 더 적합한 서비스를 제공해 드릴 수 있도록 개별 제품을 선택해 주십시오. *
지금은 채팅에 회신할 수 있는 기술 지원 엔지니어가 없습니다. 즉각적인 서비스를 받으려면 당사의 서비스 요청 양식을 사용하여 요청을 제출하십시오.
다음 문서의 설명에 따라 문제를 해결할 수 있습니다.
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
계열사 지원 사이트에서 Quest *제품*에 대한 온라인 지원 도움말을 볼 수 있습니다. 올바른 *제품* 지원 콘텐츠 및 지원에 연결하려면 계속을 클릭하십시오.
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을 계속 사용할 경우 당사가 제공하는 뛰어난 셀프서비스 기능 모두를 최대한으로 활용하실 수 없습니다.