Chat now with support
Chat mit Support

Unified Communications Analytics 8.8.3 - 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

How often do collections update the data?

By default, each data collection has a default job interval set. When you configure a data collection, you have the option of changing the schedule for that collection to a different run interval or to an explicit time every x days. For some types of data, the data is collected only once a day regardless of the set schedule so the new data will not be available in insights until the following day.

Essentially, there are two types of data source collections that you can schedule:

•
Data source jobs that collect and update data every time the data collection job is run.
•
Data source jobs that collect a “snapshot” of data once a day, regardless of how often the data collection job is run.

For each data source collection that you configure, you have the option of setting an explicit schedule (run at a specific time every x days). The main advantage of setting an explicit schedule for a data source collection is that it allows you to have jobs run separately over different time periods. This option is useful for staggering when jobs run in environments with a large number of configured data source jobs.

Collects and updates each time job is run

Some of the data collections update each time that the collection job is run. For these data collections, only the data that changed from the previous job run is gathered. The data collections that update the data that changed since the last job run are as follows:

•
Exchange Tracking Logs (message traffic, DLP matches) using PowerShell and LDAP.
•
Exchange Mailbox Contents (message information) using LDAP and EWS.
•
Exchange ActiveSync IIS Logs (mobile device event and email statistics, OWA logons) using PowerShell and LDAP.
•
Exchange Online Mailbox Contents (message information) using EWS and remote PowerShell.
•
Skype for Business/Lync CDR Database (peer-to-peer session and conference information)
•
Skype for Business/Lync QoE Database (Quality of Experience data)
•
Cisco CDR Logs (peer-to-peer calls, ad hoc conference calls, and meet-me conference calls)
Collects a once-a-day data “snapshot”

Some data collections take a once-a-day “snapshot” of the data even if they are scheduled to run more than once a day. Data collections that gather data only once a day are follows:

•
Domain Controller (user information from Active Directory) through LDAP.
•
Exchange Configuration (Exchange server, database, mailbox, mobile device configuration, and statistics) using LDAP and PowerShell.
•
Exchange Mailbox Content Summary (mailbox folder statistics for Exchange user mailboxes) using LDAP and EWS.
•
Exchange Public Folders (statistics for legacy Exchange 2010 and new Exchange 2013/2016/2019 public folders using remote PowerShell.
•
Exchange Online Hybrid Mailbox Configuration (mailbox information) using LDAP and PowerShell.
•
Exchange Online Hybrid User Configuration (users and distribution groups) in hybrid environments using LDAP and remote PowerShell.
•
Exchange Online Native Mailbox Configuration (mailbox information) using remote PowerShell.
•
Exchange Online Native User Configuration (user information) using remote PowerShell.
•
Office 365 User Subscription Configuration (subscription configuration) using remote PowerShell.
•
Exchange Online Mailbox Content Summary (mailbox folder statistics) for Exchange Online user mailboxes using EWS.
•
Exchange Online Public Folders (public folder statistics and configuration) using remote PowerShell.
•
Skype for Business/Lync Configuration (server, pool, and user policy configuration) using LDAP and PowerShell.
•
Cisco Configuration (LDAP for Active Directory and Cisco Unified Communications Manager)
Data sources that run in background as needed

Additionally, there are data collections that run in the background and update data only as needed:

•
Database Consistency (used to ensure messages received before and after UTC midnight are inserted in the database only once).
•
Exchange Calculation (recipient response times, message delivery times)
•
Cisco Calculation (duration times for ad hoc conferences)
•
Data Query Availability (used to make the data available for queries. Data collected between runs of the Data Query Availability job are not available until the job runs)

For more information, see How often do the data collections actually gather data and when do they run? .

Viewing the collection job status

Viewing the collection job status

After the data collection start date, specified on the Data Collection page, the UC Analytics data collections begin to gather information. To view the progress of the collection jobs and to see if there are any errors during the collections, click View Data Collection Status at the top right of the Data Collections page.

Figure 2. Viewing data source collection job status.

By default, UC Analytics only shows the status from the last job run for each data source (Most recent / running). If a collection job shows errors or warnings, you can view the details in the Details pane at the bottom. Use the Show errors only check box and the Show warnings only check box to select whether you want to only errors, only warnings, or both errors and warnings.

Using the filter options, you can filter for a specific data source or job status to determine if a data collection has been running correctly. You can also narrow the returned results by specifying a custom date range.

Filtering job status results by state or type

You can filter the job status results to view only jobs that succeeded, jobs that failed, jobs that are currently running, or jobs that completed with warnings. You can also filter for a specific data source (job type).

•
To filter by job status, click in status field and select a status of running, succeeded, failed, or warning.
•
To fitter by the data collection, click in the job type field and select the data source for which you want to see all data collection job status information.

To search for a specific data source, enter part or all of the data source name in the search field.

For information about how often data collections gather data, see How often do collections update the data? .

Filtering job status results by date range

The UC Analytics keeps 30 days of job status records by default but the job status page can only display 15,000 records. If there are more than 15,000 records in the database, you can filter the results by date range.

By default, the job status page shows the most recent result for each data source collection.

To filter by date range
1
Click the beside Most recent only in the date range field
2
Select the time period that you want:

Today

Yesterday

Last 7 days

Last 14 days

Custom

3
If you select Custom, specify the start date and the end date for the time period:
a
Enter or select the start date in the left field.
b
Enter or select the end date in the right field.
The job status page displays only the job status records that fall within the specified date range.
Downloading the job status file for a specific data collection job

You can download a file that contains the collection job details by clicking the icon at the end of the status row. The download option allows you to save the .log text file to a specific location. This feature is useful for troubleshooting a specific data collection job.

Copying the job details information

If you want to copy the contents of the job details, double-click on the row that contains the details you want. The Details Copy option displays and you can copy the details and paste the text into a separate document.

Forcing a data source collection to run now

After you have created and scheduled your data source collections, you may want to have a collection run immediately. For example, you might have added new targets for a data source collection and want get updated data before the next scheduled collection.

To run a data source collection immediately
1
On the Admin Settings | Data Collections page, hover your cursor over the data source that you want to run.
Several icons display on the options menu on the right side of the data source tile.
Figure 3. Displaying the data source options menu.
2
Select the Run now icon.
A new data collection job is started for the data source.

If you use the Run now option for a data source that only takes a once-a-day “snapshot” of the data, no new data is collected unless you have added a new target. For information about how often data collections gather new data, see How often do collections update the data? .

Renaming a data source

You can create more than one data collection for the same data source. By adding multiple data source collections, you can distribute the load of collecting resource-intensive data.

For example, you can collect mailbox permissions and Active Directory extended permissions through the Exchange configuration data source. Collecting the permissions data can be very time-consuming. You can add and configure multiple Exchange configuration data sources to collect different subsets of the target mailboxes to collect this information.

Once you have added more than one Exchange configuration data source, you can rename each data source to more clearly identify what data is collected from each data source.

To rename a data source
1
On the Data Collection page, hover over the right corner of the data source tile and click .
2
Select Rename.
3
Enter a descriptive name for the data source and click Save.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen