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

Adding and configuring data sources

You can configure the data sources to create the data collections that collect information from different environments. The workflow to add data sources and set up data collection is similar for each target environment.

Active Directory data sources for Active Directory Forest/Office 365 Hybrid target environment

User, group, and contact data from Active Directory. See Creating an Domain Controller data source .

User subscription information including licenses and subscribed services such as Exchange Online, Skype for Business Online, SharePoint Online, using remote PowerShell.

See To set up an Office 365 user subscription configuration collection

Azure Active Directory data sources for native Office 365 target environment

User subscription information including licenses and subscribed services such as Exchange Online, Skype for Business Online, SharePoint Online, using remote PowerShell.

See To set up an Office 365 user subscription configuration collection

Exchange data sources for Active Directory Forest/Office 365 Hybrid target environment

Exchange configuration from the Exchange server including organization, server, DAG, mailbox, database status, database copy, mobile device configuration, personal archive and mailbox statistics. See Creating an Exchange Configuration data source .

Exchange message traffic and DLP rule matches from your Exchange message tracking logs. See Creating an Exchange Tracking Logs data source .

Exchange message data through Exchange Web Services (EWS) from your target mailboxes. See Creating an Exchange Mailbox Contents data source .

Exchange calendar data including meetings and appointments that were created by your users in Outlook. See Creating an Exchange Calendar data source .

Mobile device events and email statistics from the ActiveSync IIS log files on Exchange Client Access Services (CAS). Also can collect Outlook on the Web (OWA) logon details. See Creating an Exchange IIS Logs data source .

Statistics including size and number of items for mailbox folders such as Inbox, Deleted Items, and Junk E-Mail. See Creating an Exchange Mailbox Content Summary data source .

Statistics for legacy public folders (Exchange 2010) and for new public folders (Exchange 2013, Exchange 2016, and Exchange 2019). See Creating an Exchange Public Folders data source .

Detailed information for Exchange Online users and distribution groups in a hybrid environment. See Creating an Exchange Online Hybrid User Configuration data source .

Exchange Online mailbox statistics, permissions, and mobile device data from a hybrid (Office 365 and on-premise Exchange) environment. See Creating an Exchange Online Hybrid Mailbox Configuration data source .

Information about email traffic from Exchange Online user mailboxes using Exchange Web Services (EWS). You can collect from some or all mailboxes. See Creating an Exchange Online Mailbox Contents data source .

Statistics including size and number of items for mailbox folders for Exchange Online mailbox users. See Creating an Exchange Online Mailbox Content Summary data source .

Public folder statistics and configuration information from Office 365 using PowerShell. See Creating an Exchange Online Public Folders data source .

Exchange Online calendar data including meetings and appointments that were created by your users in Outlook. See Creating an Exchange Online Calendar data source .

Exchange Online data sources for native Office 365 target environment

Exchange Online user and group data from a native Office 365 environment using PowerShell. See Creating an Exchange Online Native User Configuration data source .

Exchange Online mailbox configuration including statistics, permissions and mobile devices from native Office 365 using remote PowerShell.

See Creating an Exchange Online Native Mailbox Configuration data source .

Information about email traffic from Exchange Online user mailboxes using Exchange Web Services (EWS). You can collect from some or all mailboxes.

See Permissions needed for Exchange Online Mailbox Contents data .

Statistics including size and number of items for mailbox folders for Exchange Online mailbox users. See Creating an Exchange Online Mailbox Content Summary data source .

Public folder statistics and configuration information from Office 365 using PowerShell. See Creating an Exchange Online Public Folders data source .

Exchange Online calendar data including meetings and appointments that were created by your users in Outlook. See Creating an Exchange Online Calendar data source .

Skype for Business/Lync data sources for on-premise Active Directory forest target environment

Server, pool, and user policy configuration data directly from the Skype for Business/Lync server. See Creating a data source for Skype for Business/Lync configuration .

Skype for Business/Lync peer-to-peer session and conference data from the CDR database. See Creating a data source for Skype for Business/Lync CDR .

Skype for Business/Lync Quality of Experience (QoE) data from the QoE database. Creating a data source for Skype for Business/Lync QoE .

Cisco data sources for on-premise Active Directory forest target environment

Cisco server and end-user data the Cisco Unified Communications Manager server and synchronized user data from Active Directory. See Creating a data source for Cisco configuration .

Cisco peer-to-peer call, ad hoc conference call, and meet-me conference call information from Cisco CDR log files. See Creating a data source for Cisco CDR logs .

2
Click Data Collection.
3
Click + beside the name of the target environment.

You must add data sources for each target environment that you have created. So if you have two Active Directory forests added as target environments, you would add the same data sources for each target environment.

For performance reasons, you can add multiple data sources of the same type to distribute the collection load or for different platform versions. For example, you would add an Exchange configuration data source for your Exchange 2010 servers and an Exchange configuration data source for your Exchange 2013/2016/2019 servers.

You can use the rename option to rename each data source so that it reflects the information that is being collected. For information about renaming data sources, see Renaming a data source .

After a data collection is created and is running on a regular basis, you can modify the collection. For example, you could select additional types of data to be collected.

For data sources that require an LDAP connection, auto-discovery is used by default to determine the domain controller that is used. However, for a large environment, you might want to explicitly specify a pool of domain controllers to be used rather than using auto-discovery.

For example, in a large environment you might configure six or more Exchange Configuration data sources, several Tracking Logs data sources, and several IIS Logs data sources. If all the data sources use auto-discovery for the LDAP connection, the data sources would tend to use the same domain controller. To avoid this situation, you can specify a pool of domain controllers to be used for certain collections to spread the gathering load.

If you decide to specify a pool of domain controllers, UC Analytics will resolve the LDAP connection to the first available domain controller. If several different data collections use the same pool with the same sequence of domain controllers, the data source collections may all resolve to the same domain controller. For this reason, you should vary the first domain controller that is specified when you specify a pool of domain controllers for a collection.

The following data sources require LDAP connections:

1
On the data source configuration page, select Show advance settings in the LDAP Connection Parameters section.
2
Under Global Catalog Domain Controller, select Use specific domain controller and click Add domain controller.

Recommendations for collecting from Office 365

Many of the data sources that collect from Office 365, including Exchange Online (hybrid or native), use remote PowerShell to collect the data from Office 365. You must specify the account is used to connect to Exchange Online when you configure the data source.

It is recommended that you specify a different account for the PowerShell credentials that are used for each Exchange Online or Office 365 data source that you configure.

When would I use the Delete Data option?

On the Data Collections page, there is a Delete Data button. Typically you only use this option if you want to delete all the data you have collected. To do this, you must first delete all the data sources that you have configured. By deleting all the data sources and then deleting all the collected data, you can essentially start over again.

If you only want to remove old data, adjust the time period for data retention.

How often do collections update the data?

By default, each data collection has a default job interval set. When you configure a data collection, you have the option of changing the schedule for that collection to a different run interval or to an explicit time every x days. For some types of data, the data is collected only once a day regardless of the set schedule so the new data will not be available in insights until the following day.

Essentially, there are two types of data source collections that you can schedule:

For each data source collection that you configure, you have the option of setting an explicit schedule (run at a specific time every x days). The main advantage of setting an explicit schedule for a data source collection is that it allows you to have jobs run separately over different time periods. This option is useful for staggering when jobs run in environments with a large number of configured data source jobs.

Some of the data collections update each time that the collection job is run. For these data collections, only the data that changed from the previous job run is gathered. The data collections that update the data that changed since the last job run are as follows:

Some data collections take a once-a-day “snapshot” of the data even if they are scheduled to run more than once a day. Data collections that gather data only once a day are follows:

Additionally, there are data collections that run in the background and update data only as needed:

For more information, see How often do the data collections actually gather data and when do they run? .

Related Documents