Converse agora com nosso suporte
Chat com o suporte

Unified Communications Analytics 8.8.2 - Deployment Guide

Prerequisites for your installation Installing UC Analytics Configuring UC Analytics Adding data sources for Active Directory or Azure Active Directory Adding data sources, chargeback costs, and thresholds for Exchange and Exchange Online
Permissions needed to collect Exchange on-premises or hybrid data Permissions needed to collect from native Exchange Online Creating an Exchange Configuration data source Creating an Exchange Tracking Logs data source Creating an Exchange Mailbox Contents data source Do I need both Exchange Tracking Logs and Exchange Mailbox Contents collections? Creating an Exchange IIS Logs data source Creating an Exchange Mailbox Content Summary data source Creating an Exchange Calendar data source Creating an Exchange Public Folders data source Adding Exchange Online hybrid data sources for hybrid Office 365 Adding Exchange Online data sources for native Office 365 Setting chargeback costs for Exchange Setting thresholds for Exchange metrics Omitting words when filtering by subject or body
Adding data sources, chargeback costs, and thresholds for Skype for Business/Lync Adding data sources, chargeback, and thresholds for Cisco Managing which insights can seen by users Configuring and managing subscriptions Making changes to your deployment Appendix A:Configuring Exchange and Office 365 Appendix B:Configuring the Skype for Business or Lync Server Appendix C:Configuring IIS Log Files to capture ActiveSync or OWA events Appendix D:PowerShell cmdlets used by data sources Appendix E:Backup and recovery options Appendix F:Custom configurations Appendix G: Questions and answers about UC Analytics

Firewall configuration: ports for data collection

When you configure your firewall, UC Analytics requires access to the following TCP and UDP ports for Exchange 2010 and later:

 
Table 10. Ports required for data collection.
Protocol and Port
Destination
Usage

TCP/UDP 135-139
•
Domain Controllers
•
Exchange Servers

Microsoft file sharing SMB (Server Message Block)

TCP/UDP 445
•
Domain Controllers
•
Exchange Servers

Direct-hosted SMB traffic and user authentication

TCP/UDP 88
•
Domain Controllers
•
Exchange Servers

Kerberos authentication

TCP/389 (DC) or TCP/3268 (GC)
•
Domain Controllers
•
Exchange Servers

LDAP (Lightweight Directory Access Protocol) connection

TCP/636 (DC) or TCP/3269 (GC)
•
Domain Controllers
•
Exchange Servers

LDAP (Lightweight Directory Access Protocol) connection over SSL

TCP/UDP 53
•
Domain Controllers (DNS role)

DNS (Domain Name System)

TCP/UDP 137
•
Domain Controllers
•
Exchange Servers

WINS (Windows Internet Name Service)

TCP Port 80
•
Exchange Servers

Remote PowerShell for Exchange (also required access to the IIS PowerShell virtual directory on your Exchange servers)

TCP Port 443
•
Skype for Business / Lync
•
Office 365

Remote PowerShell for Skype for Business / Lync (also required access to the IIS OcsPowerShell virtual directory on your Skype for Business / Lync Servers)

TCP 5985 (HTTP) and 5986 (HTTPS)
•
Exchange Servers
•
Skype for Business / Lync Servers
•
Office 365

WinRM (Windows Remote Management) service

If you have implemented an intelligent firewall, you can configure the firewall to allow the specific types of network access (SMB, LDAP, and so on) that UC Analytics requires instead of access to specific ports.

Ports used for service-to-service communication in a distributed installation

In a distributed installation where you have a multiple UC Analytics servers deployed and there are firewalls between the UC Analytics servers, certain ports are required for service-to-service communication.

•
For the Storage Engine and the Query Engine, open the following TCP ports: 1223, 7100, 7101, 7299, 9042, 9260, and 10099.
•
For the Data Engine, open the following TCP ports: 1336 and 1337.

Planning for deployment

When you are planning your deployment, you must determine the number of servers across which you are deploying UC Analytics. You also must determine how much storage is required for the number of mailboxes from which you are collecting data.

For additional information see the UC Analytics Deployment Sizing.xlsx spreadsheet which can be found under Documentation in the autorun.exe.

Determining where to install services

It is not recommended that you install any UC Analytics services on the same server where core MessageStats or UC Diagnostics is installed.

If you are installing the UC Analytics services on several computers, consider the following information:

•
Data collection performance is better if the Data Engine service is located near to the Exchange server and to the Skype/Lync CDR database server.
•
Ideally, you would install UC Analytics on a computer that is in the same forest as the Exchange servers from which you are collecting data. However, you can install in a forest that is separate from the forest that contains your Exchange servers. For information about configuring multi-forest environments, see Adding multiple Active Directory forests .
•
You can install UC Analytics on a virtual machine (VM) but, to obtain optimal performance for a production installation, it is recommended that you install on a physical machine.
•
The Storage Engine service nodes automatically synchronize with each other. If you install two Storage Engine services, it is better to have them collocated when possible for performance reasons.
•
It is best to have all the UC Analytics services located as close as possible. At a minimum they should all be within the same site.
•
For security considerations, all services are recommended to be installed within the intranet. For information about configuring the web site for https, see Setting up the web site for HTTPS .
•
For small to mid-size installations. UC Analytics can be installed on a single computer.
•
For large installations, use one of the recommended deployments provided in the installer. For additional information see the UC Analytics Deployment Sizing.xlsx spreadsheet which can be found under Documentation in the autorun.exe.

What files need to communicate through software firewalls?

Software firewalls, such as Windows Firewall, can prevent the code in the UC Analytics processes from performing necessary network input and output. Such firewalls must be configured to allow the UC Analytics Data Engine to communicate with the Query Engine and to communicate with your Exchange, Active Directory, Cisco, and Skype for Business resources.

The files that can be affected by a software firewall are as follows:

•
C:\Program Files\Quest\UC Analytics\Storage Engine\bin\prunsrv.exe
•
C:\Program Files\Quest\UC Analytics\Query Engine\bin\prunsrv.exe
•
C:\Program Files\Quest\UC Analytics\Data Engine\UC.Analytics.Insights.DataEngine.Service.exe
•
C:\Program Files\Quest\UC Analytics\Data Engine\UC.Analytics.Insights.DataEngine.BulkDataExport.exe
•
C:\Program Files\Quest\UC Analytics\DeploymentManager.exe
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação