立即与支持人员聊天
与支持团队交流

Unified Communications Analytics 8.7 - 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

Office 365 User Subscription Configuration data source

•
Connect-MsolService
•
Get-MsolUser

Appendix E:Backup and recovery options

Appendix E:
Backup and recovery options

This section contains information about how to handle specific situations. See the following topics for instructions about how to configure UC Analytics to meet certain requirements.

Setting up a multi-forest environment with a one-way trust
Firewall configuration: ports for data collection
Backing up and restoring your data using scripts
Scheduling the backup batch file to run automatically
Performing a manual backup of the storage folder before upgrade
Moving your storage location
Recommendations for disaster recovery

Setting up a multi-forest environment with a one-way trust

You can configure UC Analytics to support multiple forests that have a one-way trust. In the following example of a one-way trust scenario, the forests are configured as follows:

•
Forest A - Admin forest contains Active Directory users
•
Forest R - Resource forest (all mailboxes are here).
•
Forest R trusts Forest A.

UC Analytics is installed in the resource forest (Forest R). The UC Analytics Data Engine service is running with Forest R credentials. For this scenario, you would perform the following steps to allow users from the trusted domain (Forest A) to access UC Analytics:

1
Add a second target environment that points to the trusted domain.
2
Specify an account from the trusted domain as the Authentication Credential that is used to authenticate a user (User X) in Forest A and allows access to UC Analytics.
•
The credential must have read rights to the Active Directory forest specified in the Forest A environment.
•
The credential must have sufficient rights to browse users and groups and to resolve group memberships for all users and groups from this environment that are specified in the Security settings.

Once the second environment (for Forest A) is added and an authentication account from Forest A is specified for authentication, User X can log on to UC Analytics. For information about adding target environment for an additional Active Directory forest, see Adding multiple Active Directory forests .

User X can view the data in the insights based on the security permissions that were granted to the ForestA\Group in the Security settings. When you add users in the Security settings, ensure that the Forest A target environment is selected when you add the Forest A users. For information about the Security settings, see Granting users access to data .

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 38. Ports required for data collection
Network access
Required ports

Microsoft file sharing SMB (Server Message Block)

TCP/UDP 135-139

Direct-hosted SMB traffic

TCP/UDP 445

Kerberos

TCP/UDP 88

LDAP (Lightweight Directory Access Protocol) connection

TCP/389 (DC) or TCP/3268 (GC)

LDAP (Lightweight Directory Access Protocol) connection over SSL

TCP/636 (DC) or TCP/3269 (GC)

DNS (Domain Name System)

TCP/UDP 53

WINS (Windows Internet Name Service)

TCP/UDP 137

Remote PowerShell for Exchange

TCP Port 80 and access to the IIS PowerShell virtual directory on your Exchange servers

Remote PowerShell for Skype for Business/Lync

TCP Port 443 and access to the IIS OcsPowerShell virtual directory on your Skype for Business/ Lync Servers

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.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级