Chat now with support
Chat with Support

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

Creating an Exchange Mailbox Contents data source

The Exchange mailbox contents data collection gathers email message information from user mailboxes using Exchange Web Services (EWS). When you configure a mailbox contents data collection, you must specify the target mailboxes and the Client Access Server (CAS) URL that is used to connect to the mailbox server. For Exchange 2016/2019, you specify the URL for the Client Access Services on the mailbox server.

When you specify target mailboxes, you can set all mailboxes, mailboxes for a specific mailbox server, mailboxes that belong to a specific organizational unit (OU), or specific mailboxes as targets.

If you have an Exchange hybrid environment, you can configure an Exchange Online Mailbox Contents data source to collect Office 365 mailboxes. For more information, see Permissions needed for Exchange Mailbox Contents, Exchange Mailbox Content Summary, or Exchange Calendar data sources and Permissions needed for Exchange Online Mailbox Contents data .

In addition to message traffic, you can configure the mailbox contents collection to gather the following message information from the target mailboxes:

For information about how times are calculated on insights when you use the “response time” or “after hours” filters, see the section titled How the Filters Work in the UC Analytics User Guide.

2
Click Data Collection.
3
Click + beside the name of the target environment.
4
Select the Exchange Mailbox Contents check box.
a
Click Minimum amount of time between job runs: and select an hourly interval.
b
Click Run job at: and select the specific job run time, the number of days between each job run, and a start date.
Recommendation
If you select Body or Internet Message Headers, it is recommended that you limit the number of mailboxes to a key group of user mailboxes for this specific data collection.
Select the Use Data Engine service credential option.
If you want to specify one or more explicit domain controllers instead of automatically discovering the domain controller, click Show Advanced Settings in the LDAP Collection Parameters section. For more information, see Specifying explicit domain controllers for LDAP connections . The domain controller must be a global catalog server.
14
Click Save.

Tips for better performance for mailbox contents collection

You can specify more than one set of Exchange gathering credentials and you can specify more than one CAS server for EWS data collection.

If you specify multiple EWS credentials and multiple CAS servers, it allows the EWS gathering to collect data from more mailboxes in parallel. This will reduce the time that is needed to collect the data.

For information about the types of data collections and the rate at which message data is collected, see Determining where to install services .

You could also increase the Exchange throttling quota for the accounts used to collect the message data.

IMPORTANT:  

If you configure a mailbox content data gathering to collect the message body, storage requirements can be doubled. It is strongly recommended that if you collect the message body, you specify only a limited number of target mailboxes for this data collection.

By increasing the number of CAS URLs and the number of credentials that are used for collection of the Exchange data, you can shorten the time that it takes EWS to collect the message data.

Assuming that Exchange throttling is set to the default value for the gathering credentials, the estimated collection times are as follows:

Do I need both Exchange Tracking Logs and Exchange Mailbox Contents collections?

Though the mailbox contents data collection and the Exchange tracking log data collection both gather message information, there are some differences.

The Exchange tracking log collection gathers message information for all mailboxes.

The mailbox contents collection gathers message information for only the specified target mailboxes.

The Exchange tracking log collection gathers both message data and DLP rule matches.

The mailbox contents collection (EWS) gathers only message data but includes specific data not found in tracking logs such as

The mailbox contents data collection can also include message body text if configured.

The Exchange tracking log collection is much faster than the mailbox contents collection.

The mailbox contents collection is much slower than the Exchange tracking log collection.

You run the Exchange tracking log collection against both Exchange mailbox servers and hub transport servers.

The mailbox contents collection accesses the Exchange CAS (Client Access Servers) to gather data.

For more detailed information, see What are the differences between the Exchange Mailbox Contents and Exchange Tracking Logs data sources? .

Creating an Exchange IIS Logs data source

You configure an Exchange IIS logs data source to collect mobile device activities such as messages sent, messages received, and device information from the IIS log files. You can also configure the Exchange IIS Logs data source to collect Outlook on the Web (OWA) logon information.

You must collect the logs of the IIS sites for both on your front-end Exchange Client Access Server (CAS) and on your back-end Exchange Mailbox servers. The back-end IIS logs are required for information about the number of messages that are downloaded and uploaded using ActiveSync.

2
Click Data Collection.
3
Click + beside the name of the target environment.
4
Select the Exchange IIS Logs check box.
a
Click Run job every: and select an hourly interval.
b
Click Run job at: and select the specific job run time, the number of days between each job run, and a start date.
If you want to specify one or more explicit domain controllers instead of automatically discovering the domain controller, click Show Advanced Settings in the LDAP Collection Parameters section. For more information, see Specifying explicit domain controllers for LDAP connections . The domain controller must be a global catalog server.

If you leave the default setting to automatically discover domain controller, the data collector selects a domain controller from the forest that hosts the Data Engine, not a domain controller from the forest from which you are collecting the data.

12
Click Save.

The Exchange ActiveSync IIS log files are located either in user-created file shares or in the IIS log directories of your Exchange Client Access Servers (CAS) and Exchange Mailbox servers.

For example, if the front-end site is site #1 and the back-end site is site #2 and both are on the same Exchange server, the default paths will be as follows:

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating