Chat now with support
Chat with Support

Unified Communications Analytics 8.6 - 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 Impersonation 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:Custom configurations and backup and recovery options Appendix F: Questions and answers about configuration

Considerations before you install

The following limitations must be considered before you install UC Analytics:

About a pilot installation

In a pilot installation, all the UC Analytics services are installed on a single computer. Though pilot installations are typically used in test installations, if you have a computer with enough resources you could also use a pilot installation for a production environment.

If you have a native Office 365 environment with no on-premise users, you can install UC Analytics in a workgroup.

About a production installation

In a production installation, you can distribute the UC Analytics services across several servers. Additionally, the Data Engine service and the Query Engine service can be distributed in two separate roles, the insights role and the collector role.

In a UC Analytics installation you can distribute the following services as follows:

For example, you might install the web site and the Data Engine (insights) and Query Engine (Insights) on one server and the Data Engine (Collector) and Query Engine (Collector) on a second computer.

You can install multiple collector roles, Date Engine (Collector) and Query Engine (Collector), on different servers. However, you can only install one instance of each insights role – Date Engine (Insights) and Query Engine (Insights). By distributing the collector roles, you can distribute the data collection and data writing load for different data sources.

The Storage Engine service is used to store the data collected from various platforms. To distribute the data that is stored by the Storage Engine, you can install the Storage Engine on more than one server. It is better to have the Storage Engines collocated when possible for performance reasons.

You could install instances of the Storage Engine service on both the servers and an additional Storage Engine on a third server.

Web Site &Data Engine (Insights)

Data Engine (Collector)

Data Engine (Collector)

Query Engine (Insights)

Query Engine (Collector)

Query Engine (Collector)

Storage Engine

Storage Engine

Storage Engine

When you install more than one Data Engine (Collector), one of the collectors must be set as the Primary Data Collector. By default the Primary Data Collector is the first collector that is installed. You can manually set a collector to be the Primary Data Collector on the Add Server page when using the Advanced Deployment option.

The Primary Data Collector is used to run the data sources that run automatically in the background in addition to the data sources that you have configured. For more information, see Data sources that run in background as needed .

For information about storage requirements, see Hardware minimum requirements .

You must ensure that the computer on which UC Analytics is to be installed meets the minimum software requirements. For information about the minimum requirements, Software prerequisites .

Generally you select one of the recommended installations and specify the servers on which services are to be installed. For larger, more complex environments, you can perform a production installation and specify the location for each service or service role.

If you are performing a production installation, be aware of the following rules:

Accounts used during installation

The account that you use to install UC Analytics must be a local administrator on the computer. If you are distributing the services, the account must have local administrator rights on each computer on which you are installing.

During installation you can specify an account that is used to run the Data Engine service. This account must be a domain account and must have local Admin rights on the computer on which the Data Engine service is installed.

By default, the account that is used to install UC Analytics is set as a product administrator, which means that the account can access the Admin Settings which are used to configure the product.

If a service account has changed, you can update the account using the Change Service Account option in the Deployment Manager. This option changes the account in Windows for the UC Analytics services and in the UC Analytics configuration database. For more information, see Changing the service account .

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating