Chat now with support
Chat with Support

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

Identifying your internal domains

Identifying your internal domains

Using the Classifications page, you identify the domains which are internal to your organization. You identify your internal domains to allow insights to show internal and external email traffic, Skype for Business/Lync sessions, and other related information correctly.

To identify internal domains
1
Click the gear icon on the home page side bar.
2
Click Classifications and click Domain Classifications.
3
Click Add domain for the Internal Domains.
4
Enter any domains that are considered internal to your business and click Apply.

You can modify or add domains at any time. After you have made changes, the existing data in the insights is reclassified (internal and external) immediately.

Guidelines when specifying domains

Some messages may not come directly from a domain so remember to add subdomains or to specify * in the domain name.

For example, you could add both DomainA.com and *.DomainA.com to the Domain Classifications list to include DomainA.com and all of its sub-domains. If you entered *DomainA.com, you would get the domain and the subdomains but you would also get “AnotherDomainA.com” as well.

Entries in the Custom Domain Classifications list are not case-sensitive so it doesn’t matter if you enter the domain names as capital letters or lower case letters.

You can also add your own custom classifications. Since there will not be a default insight for your new classification, you can create a new insight and use the filters to select the new classification.

Classifying domains for message traffic

You also can assign classifications to domains that determine how messages to and from the domains are classified in the insights. For example, using the Classification page you could specify that gmail.com should be classified as a “Personal” domain. For email where the sender or the receiver is in the specified domain, the messages are tagged with the associated classification.

You can assign domains to the following categories:

•
Competitor
•
Partner
•
Customer
•
Personal
•
Social Network
 
* 
NOTE: Domains which are not added to the internal domains list are treated as external, regardless of their classification.
To set classifications for messages
1
Click the gear icon on the home page side bar.
2
Click Classifications and click Domain Classifications.
3
Click Add domain classifications.
4
Enter the domain and the classification that is used for all messages sent from and to the domain, and click Add.
5
Repeat steps 3 and 4 for each domain you want to classify in your insights.

Setting where data calculation for insights is performed

In previous versions, any data calculation that is done before displaying an insight is done on the client side (user interface web site). For large amounts of data, this can result in an insight taking a long time to display or timing out with an error. You can set insight calculation to be done primarily in the Data Engine (server-side). As of version 8.7, this option is selected by default for a new installation.

If you select the Calculate insight data on server side option on the Queries page, UC Analytics loads the insight data dynamically with paging by both web server and web client for data-intensive insights. This option is more stable and faster and is recommended, especially for large amounts of data. Table views support sorting for group columns and most metric columns, but sorting is not supported for field columns. For information about field and metric columns, see the section titled “What are the different types of columns?” in the UC Analytics User Guide.

For a list of the data-intensive insights that are optimized by this option, see What insights are affected by the “Calculate insight data on server side” option?

If you select the Calculate insight data on client side option, UC Analytics loads all data at once on the web server with web client paging. This option requires more resources, such as memory, and, for large amounts of data, a 64-bit web browser. Table views support sorting for almost all columns.

To set where data calculation is performed for insights
1
Click the gear icon on the home page side bar.
2
Click Queries.
3
Under Insight Query, select one of the following options:
•
Calculate insight data on client side
•
Calculate insight data on server side

Excluding <none> values from insights

Sometimes, due to environmental considerations, insights can include <none> values that are not relevant and that you want to exclude. You can configure the Queries page to exclude <none> values from being displayed and included in calculations for aggregated and organizational grouped views in some or all of your insights.

To exclude <none> values from some or all insights
1
Click the gear icon on the home page side bar.
2
Click Queries.
3
Select either:
•
Exclude <none> values in all the insights.
•
Exclude <none> values in the specified insights,
4
If you selected Exclude <none> values in the specified insights, click Set specified insights and select the insights that you want.
You can use the Search insights field to find the insights you want.
5
After you have selected all the check boxes for the insights that you want, click Add.
6
If you want to add more insights, click Selected x insights ... and continue to add more insights.
7
When you are finished, click Save.
What does <none> mean in an insight?

In some cases, certain information is missing and will show as <none>. For example, if a message is a system message or is sent through an SMTP address and does not have a corresponding user account in Active Directory (AD), the AD user attributes such as office, department, or sender name can display as <none> since they do not exist in Active Directory.

In another example, suppose you want to group message counts by department, but the department attribute is not set for all AD users or the AD job (Domain Controller data source) only collected partial users because an OU was specified as the target. In these instances, <none> values could occur.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating