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

Permissions needed to collect from native Exchange Online

If you have a native Office 365 target environment, you can create the following data sources to collect information from your native Exchange Online deployment. You must set up an Office 365 (native) target environment and specify the required credentials when you configure the Exchange Online data sources.

•
Exchange Online Native User Configuration: This data source collects user and distribution group data using remote PowerShell. For information about the required permissions, see Permissions needed for Exchange Online Native User Configuration data source .
•
Exchange Online Native Mailbox Configuration: This data source collects Exchange Online native mailbox statistics such as mailbox size, permissions, and mobile devices. For information about the required permissions, see Permissions needed for Exchange Online Native Mailbox Configuration data source . For a hybrid Office 365 implementation, use the Exchange Online Hybrid Mailbox Configuration data source.
•
Exchange Online Mailbox Contents: This data source can collect mailbox content information from either hybrid or native Office 365 using Exchange Web Services (EWS) and remote PowerShell. For information about the required permissions, see Permissions needed for Exchange Online Mailbox Contents data .
•
Exchange Online Mailbox Content Summary: This data source can collect mailbox content information from either hybrid or native Office 365 using Exchange Web Services (EWS). For information about the required permissions, see Permissions needed for Exchange Online Mailbox Content Summary and Exchange Online Calendar data ,
•
Exchange Online Calendar: This data source collects information about the Exchange calendar items created in Outlook (including organizer, attendees, duration, location, and size) rom hybrid or native Office 365 using Exchange Web Services (EWS) for specific or all mailboxes. For information about the required permissions, see Permissions needed for Exchange Online Mailbox Content Summary and Exchange Online Calendar data .
•
Exchange Online Public Folders: This data source can collect public folder statistics and configuration information from either hybrid or native Office 365 using PowerShell. For information about the required permissions, see Permissions needed for the Exchange Online Public Folders data source .
Permissions needed for Exchange Online Native User Configuration data source

The Exchange Online Native User Configuration data source collects user and distribution group data using remote PowerShell.

To use OAuth modern authentication when accessing Exchange Online with remote PowerShell you must have the Exchange Online PowerShell module (v1 or v2) installed. For more information, see Installing the Exchange Online PowerShell module .

The credentials that you specify are used to collect user configuration data using remote PowerShell from native Office 365. The credentials must:

•
Be a member of the Exchange View-Only Organization Management role in the Exchange Online tenant.
•
Have PowerShell access enabled.
Permissions needed for Exchange Online Native Mailbox Configuration data source

To use OAuth modern authentication when accessing Exchange Online with remote PowerShell you must have the Exchange Online PowerShell module (v1 or v2) installed. For more information, see Installing the Exchange Online PowerShell module .

The credentials that you specify to collect Exchange Online native mailbox configuration data (including statistics, permissions, and mobile devices) using remote PowerShell must:

•
Be a member of the Exchange View-Only Organization Management role in the Exchange Online tenant.
•
Have PowerShell access enabled.

To collect mailbox recipient “send as” permissions, the credentials must also:

•
Be a member of the Recipient Management role group in the Exchange Online tenant.

Creating an Exchange Configuration data source

Creating an Exchange Configuration data source

The Exchange configuration data collection gathers information about the Exchange hierarchy such as organizations, servers, DAGs, database status, database copies, and mailbox properties through PowerShell and LDAP queries to Active Directory.

When you configure an Exchange configuration collection, you specify the LDAP connection credentials, target mailboxes, the Exchange server from which you want to collect, and remote PowerShell connection details.

 
* 
TIP: For some fields you can enter multiple values separated by a semi-colon (;). For details, see Entering multiple values in a field .
Why should I specify target mailboxes?

If you specify target mailboxes, mailbox statistical and configuration information is also collected for those mailboxes including:

•
Mailbox configuration (quotas, home database)
•
Mailbox statistics (size, Item counts, deleted Item counts, storage status, and last logon time)
•
Mobile devices associated with the mailbox (device model, device type, first sync time, last sync time, policy update time)
•
Mailbox permissions and Active Directory extended permissions
•
Archive mailbox (personal archive) statistics

This information is not collected for mailboxes that are not set as 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 target mailboxes.

To set up an Exchange configuration collection
1
Click the gear icon on the home page side bar.
2
Click Data Collection.
3
Click + beside the name of the target environment.
4
Select the Exchange Configuration check box.
5
Enable the data collection for this data source.
 
* 
NOTE: If you have installed more than one Data Engine (Collector), you have the option to select a different computer that hosts a data collector.,
Modifying the collection schedule
By default the data collection is set to run every 6 hours, aligned to midnight UTC. You can modify the run interval or you can set the collection to run at a specific time on specific days.
6
Set the schedule for the data collection:
a
Click Run job every: and select an hourly interval.
- OR -
b
Click Run job at: and select the specific job run time, the number of days between each job run, and a start date.
Selecting data to collect
7
Select the types of data that you want to collect.
 
* 
NOTE: Collecting mailbox permissions data can be resource intensive. It is recommended that you create a separate instance of the Exchange Configuration data source to collect permissions.,
Specifying LDAP connection parameters
8
Specify credentials to be used for the LDAP connection or select the Use Data Engine service credential option. See Permissions needed for the Exchange Configuration data source .
If you have an Exchange resource forest deployment
If you have an Exchange resource forest deployment, you must configure the options in the Account Forest LDAP Connection Parameters section. This option is required only for linked mailboxes that have the master accounts in a different forest.
a
Select the Search additional forests for user accounts check box.
The options under Show advanced settings are expanded.
b
Select the appropriate option for the Account Forest Domain Controller:
•
Automatically discover domain controller in specific domain
•
Use specific domain controller
c
Specify the credentials that are used to access the domain controller using LDAP.
Click Add connection for each account forest that contains master accounts. This adds another section of Account Forest LDAP Connection Parameters. Specify the domain controller information and credentials for each forest.
Specifying target mailboxes
9
You have different options for specifying the target mailboxes to be included:
•
Select all mailboxes.
•
Specify the mailbox server for the mailboxes.
•
Specify the organizational unit (OU) to which the mailboxes belong.
•
Specify certain mailboxes that you want collected.
When specifying certain mailboxes you can enter the common name or email address of a mailbox, a group. or a dynamic distribution group. For more information about using a dynamic distribution group to specify target mailboxes, see Using dynamic distribution groups to select target mailboxes .
Specifying PowerShell connection parameters
10
Specify the Exchange version from which you are collecting data. For a mixed environment, select the latest version of Exchange that is installed.
For a mixed organization containing Exchange 2010 and Exchange 2013 and Exchange 2016 servers, select Exchange 2013/2016/2019 to get the most comprehensive configuration data.
To collect from Exchange 2010 and higher, you must
•
Click Add server and enter the Client Access Services (CAS) server name (and port number if applicable).
11
Specify the explicit credentials to be used to make the PowerShell connection.
Advanced settings (not required for most deployments)
•
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.
 
* 
NOTE: If the Data Engine is in a different forest from the data to be collected, specify the domain controller you want to use for data collection. 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.
•
To use HTTPS instead of HTTP to connect to the Exchange 2010/2013/2016/2019 CAS server, click Show Advanced Settings in the PowerShell Connection Parameters section. This option requires that TLS/SSL is enabled for remote PowerShell on the Exchange CAS server.
The Advanced Settings also provide options if you have a customized PowerShell virtual folder, or if you want specify either an implicit credential or the Data Engine credential be used to make the PowerShell connection.
12
Click Save.

For more information about credential prerequisites, see Permissions needed for the Exchange Configuration data source .

For information about creating Exchange Configuration data sources for a resource forest configuration, see Configuring UC Analytics for resource forests .

Best practices for gathering performance

To obtain the best performance from the Exchange configuration data collection, you can add several Exchange configuration data sources to collect the data. Each data source would specify a different group of target users.

It is recommended that you group the target users according to the geographic location of the mailboxes. You can add a separate data source to collect from each geographical area. Select the server hosting Client Access Services (CAS) that is nearest to the mailbox server for each data source you configure.

In another example of distributing the data collection, you might want configure a separate Exchange configuration data source to collect mailbox permissions data. You could configure one Exchange configuration data source to collect mailbox permissions from a select number of target mailboxes. You could add another data source to collect the rest of the data for the same mailboxes.

Once you have added multiple data sources for Exchange configuration data, you can name each data source to reflect the information that is being collected. For information about renaming a data source, see Renaming a data source .

Using dynamic distribution groups to select target mailboxes

A dynamic distribution group includes any recipient in Active Directory with attributes that match the filter and conditions that you have defined.

To group target users by geographic location, you can create multiple dynamic distribution groups. All the mailboxes in each group would belong to same geographic location.

Suppose you have several data center locations within a global domain such as LON01, NYC01, and TKY01. You would create multiple data sources, one for each location.

For example, the data source for LON01 site would use the dynamic distribution group that contains only mailboxes from LON01 and would use a CAS server from LON01.

 
* 
TIP: To create dynamic distribution group for mailboxes from a single location, you could use a filter based on a mailbox custom attribute.
1
Run a PowerShell script to get all the mailbox databases.
2
Get the CAS server for each mailbox database.
3
Set the corresponding CAS server name to be one of the Custom Attributes for each mailbox.
4
After the attribute is set, use that Custom Attribute as a filter when you create dynamic distribution groups.
Specifying recipient types for a dynamic distribution group

When you create a dynamic distribution group, you set the filters you determine which mailboxes and users will be included. If you want the data collection to gather all user mailboxes, shared mailboxes, and resource mailboxes you would select All recipient types.

You could select specific filters to include only certain types of users and mailboxes such as:

•
Users with Exchange mailboxes
•
Users with external email addresses
•
Resource mailboxes
•
Contacts with external email addresses
•
Mail-enabled groups
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating