立即与支持人员聊天
与支持团队交流

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

Why are my OWA insights not showing any data?

I already have configured the required data sources (Domain Controller, Exchange Configuration, and Exchange IIS Logs) but I do not see any data in the OWA insights. Why?

Answer

The option to collect OWA data is not selected by default. To populate the OWA insights, you must have an Exchange IIS Logs data source configured with the Logons for Outlook on the Web (OWA) option selected. For more information, see Creating an Exchange IIS Logs data source .

You must also have configured IIS logging on the front-end Exchange Client Access Server (CAS) and on the back-end Exchange Mailbox servers to include the required data. For more information, see Appendix C: Configuring IIS Log Files to capture ActiveSync or OWA events .

To see the required data sources for an insight, click INFO at the top of the insight.

Why did an insight show no data for a 30-day range though I initially set the data source to collect 30 days back?

Why did an insight show no data for a 30-day range though I initially set the data
source to collect 30 days back?

I have just installed UC Analytics. Why does the Lync Organizational Summary User Activity insight show no data when I use a custom date filter for 4 Jan 2018 - 10 Jan 2018? I set my initial data source collection to go back 30 days and I started it on January 30.

Answer

There are two data source collections that provide information for the Lync Organizational Summary User Activity insight:

•
Domain Controller (AD)
•
Lync Configuration

When you started your Domain Controller data collection on Jan 30, the initial data collection period was set to 30 days (default). The Domain Controller data source collects information from AD and retroactively creates AD user “snapshots” in the database for each user. This ensures that there is a user object to link to historical data from data sources that collect historical information such as the Exchange Tracking Logs, Lync Users, and so on.

The Lync Configuration data source collection, however, collects data using PowerShell and only creates objects for the current day. The data only covers the date on which the Lync Configuration data collection accessed PowerShell to gather the data.

Therefore, on Jan 30, after the data source collections had finished, you had 30 days of AD user data and but only one day of Lync configuration data (Jan 30). The AD user snapshots from Jan 30 are linked to the Lync information, but user snapshots from Jan 29, 28, and earlier are not linked since Lync configuration data does not exist in the database for those dates.

The Lync Organizational Summary User Activity insight queries the AD users that are Lync-enabled (users that have a link to collected Lync data). When you specify “today”, the time range that the query looks for is “from midnight today until midnight tomorrow”.

When you specify an explicit date range such as Jan 1 - Jan 10, the query looks for the AD user snapshots that have links to Lync data from Jan 1 until end of Jan 10 (midnight of Jan 11) and takes the latest snapshot from this period, which is the Jan 10 snapshot. If you apply the rule about how UC Analytics collects historical data to the specified date range - the only linked AD-Lync data exists for Jan 30, not for Jan 10. For this reason, the insight shows no data.

After you have had UC Analytics running for a few months, you will have a few months of Lync configuration data accumulated and can use filters to view historical data in the Lync Organizational Summary User Activity insight.

This same scenario applies to other insights that use either the Lync Configuration or the Exchange Configuration data source collection to provide information such as:

•
Lync User Adoption
•
Lync Archiving Policies - Inventory
•
Mailboxes - Inventory
•
Mailboxes - Permissions inventory
•
Mailboxes – Inactive

Since the Lync Configuration or the Exchange Configuration data source collections only gather data for the current day, even though the Domain Controller (AD) data source collection initially contained 30 days of historical user data, there would be only one day of data for the linked AD user - Lync/Exchange configuration data.

Over time, as you run the Lync Configuration and the Exchange Configuration data source collections on an ongoing basis, you would gradually have more days available of linked user Lync/Exchange configuration data. You can then use custom date range filters on the insights.

If I collect both Exchange Tracking Logs andExchange Mailbox Contents, are there duplicate items?

If I collect both Exchange Tracking Logs and
Exchange Mailbox Contents, are there duplicate items?

I have configured both of the following data source collections:

•
Exchange Tracking Logs
•
Exchange Mailbox Contents (all mailboxes)

You can see information for the same mailboxes in the Exchange Tracking Logs data collection and in the Exchange Mailbox Contents data collection. If you run both data source collections, are there duplicate items in the UC Analytics Exchange insights?

Answer

No. The Tracking Log and Mailbox Contents data collections both collect email messages from Exchange mailboxes. However, if you collect the same messages using both types of data collections the message objects are not duplicated.

Determining which data collections you want to run is dependent on the information that you want to get from the messages. If you want a faster data collection, or if you need DLP / journaling messages, set up an Exchange Tracking Logs data collection. If you want information about response time or email attachments, and are willing to wait longer for the data collection, set up the Exchange Mailbox Contents data collection.

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.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级