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

If I collect message data only from the Exchange tracking logs, is the message Send Date and delivery time available?

If I collect message data only from the Exchange tracking logs, is the message
Send Date and delivery time available?

If you are running only the Exchange Tracking Logs data collection but not the Exchange Mailbox Contents data collection, the insights will contain the Send Date and delivery time for both MAPI and SMTP submitted messages. However, in some special circumstances, there are a couple of limitations:

•
If an SMTP message is both undeliverable and has no internal Exchange server hops, the Send Date is unavailable and no delivery time is calculated.
•
For MAPI and SMTP messages with at least one recipient in a moderated distribution group, the displayed Send Date can be the date when the message was approved by the moderator (and delivery was resumed to the group recipients) instead of the date when the message was originally sent. The delivery time is calculated from the time the message resumed its transit. When this occurs, for any recipients who had the message delivered directly to their mailbox before the moderator approved it, a received time can display that is before the Send Date.

If you are also running Exchange Mailbox Contents data collection, the Send Date is always obtained from the Date field of the message.

What are the differences between the ExchangeMailbox Contents and Exchange Tracking Logs data sources?

What are the differences between the Exchange
Mailbox Contents and Exchange Tracking Logs data sources?

Both the Exchange Mailbox contents and the Exchange Tracking Logs data sources can be configured to collect Exchange messages. What are the differences in the information that the two data collections gather?

Answer

The following table shows the differences in email message statistics between the two data sources that collect Exchange email message information:

•
Exchange Mailbox Content (EWS) data source
•
Exchange Tracking Log data source
 
Table 42. How Exchange message data is collected by different UC Analytics data sources.
What gets collected
Exchange Mailbox Content (EWS)
data source
Exchange Tracking Log
data source

Exchange user messages from the specified data source targets

You select Exchange target mailboxes by specifying groups (distribution groups or security groups) or individual users.

Only the messages from selected mailboxes are collected.

You specify the target tracking log folders on your Exchange servers.

Only the messages that transferred through the specified servers are collected.

Message history

Collection of message history is limited by

•
data retention time
•
start date specified for the data collection.

Only the messages within the “deleted mailbox retention period” are collected.

By default, a 30 day maximum message history is set in the data collection configure file. To collect more history, you must manually update the configuration file.

Only the messages that fall within the tracking log maximum age (MessageTrackingLogMaxAge) as set in the Exchange server configuration are collected.

System messages include:

•
legacy public folder synchronization messages
•
health mailbox testing messages
•
system attendant messages
•
system monitoring messages

Are not collected.

Are collected and are marked as “system messages”.

Journaling messages

Are not collected unless the journaling mailbox is configured as a data source target. In this case, the messages are not marked as journaling messages.

Are collected and are marked as Journaling messages.

SMTP messages

Are collected if they are sent to one of the target mailboxes.

Are not collected if they are sent to non-target mailboxes or to external recipients.

Are collected, but the “message sent time” for inbound messages is approximate. Delivery time is set only after the Exchange Calculation job has run.

Messages from outside organizations

Will be collected if they are sent to one of the configured target mailboxes.

Will be collected, but the “message sent time” inbound messages is approximate. Delivery time is set only after the Exchange Calculation job has run.

Messages sent to outside organizations

Are collected if they are sent from one of the target mailboxes. The “message receive time” and “message delivery time” are not set.

Are collected. The “message receive time” and “message delivery time” are not set.

Missing message properties

None

Importance

Sensitivity

Encryption

Conversation

Body

Response Time

Missing message participant properties

None

NOTE: If a message is collected through EWS and the message was sent from a mailbox user to a distribution group to which the user belongs, the user is counted only as a sender, not a recipient. If the tracking log collection was also run, that user is also counted as a recipient.

Sender On Behalf Of

To, CC,BCC (shows message recipients but not whether the To, CC, or BCC box was used)

Sent Time Of Day

Was Sent After Hours

Was Received After Hour

In Reply To

Message size

Message size in mailbox. The size in sender’s mailbox takes precedence.

Message size in transport. The earliest transport size takes precedence.

Why do I get an error when collecting Exchangeconfiguration from multiple Exchange versions?

Why do I get an error when collecting Exchange
configuration from multiple Exchange versions?

I am collecting from Exchange 2010, and Exchange 2016 and Office 365 hybrid. For the Exchange configuration data source collection, I get the following message with job type Exchange Configuration for the mailboxes that are stored in Office 365:

“Unable to detect the Exchange Mailbox version or Exchange configuration data source does not support the target mailbox version.”

I’ve verified that Impersonation is granted in Office 365, and I checked the PowerShell connection parameters. Why I am getting this message?

Answer

You must create separate Exchange configuration data collections for Exchange 2010 on-premise and for Exchange 2016/ Office 365 hybrid.

If you only added an Exchange configuration data source for Exchange 2016, you will see that the Exchange 2010/2013 option is greyed out so it is not being used. Create another Exchange configuration data collection for Exchange 2016 and that will collect the mailboxes from Exchange 2016 and Office 365 hybrid as well.

Also in the Exchange 2010 Exchange configuration data source, remove the server name that you added under Exchange 2016.

After you have configured multiple Exchange configuration data sources, you can use the Rename option to uniquely identify each data collection. For information about how rename a data source, see Renaming a data source .

Why do I have to specify domain name when doing a multi-forest collection?

Why do I have to specify domain name when doing a multi-forest collection?

During a multi-forest collection for the Exchange configuration data source, the Common Name or Email Address would not work when specifying the Target Mailboxes for the collection. We had to put in DomainName\User or DomainName\Group

The domain name is the netbios name of the other forest from which I was collecting.

Answer

The key to making the multi-forest configurations work is you cannot use the “Automatically discover domain controller” for data sources in the secondary forests. This setting is selected by default and is hidden. To access the setting, you must click the Show Advanced Settings link in the LDAP Connection Parameters section. Specify a specific domain controller.

 

Related Documents