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

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

Registering UC Analytics with the Microsoft Azure portal

To use modern authentication (OAuth) with the Exchange Online (hybrid and native) for EWS as a method to access Exchange Online, you must register the UC Analytics application with the Microsoft Azure portal. When you configure the Target Environments admin page in UC Analytics for hybrid or native Office 365, you specify the Azure Application ID that you have registered.

The process of registering an application with the Microsoft Azure portal is also described in the Microsoft topic Register an application with the Microsoft identity platform.

Depending on the region from which you are accessing the Microsoft Azure portal site, the user interface can differ.

Data sources that connect to Exchange Online using EWS are:

Supported account types: Select Accounts in any organizational directory (Any Azure AD directory - Multi tenant)
4
Click Register.
The application is registered in the Microsoft Azure portal and the Application (client) ID is displayed. Copy this ID and use it later to set the Azure Application ID in the Target Environments page.
6
Under Advanced settings, select Yes for Allow public client flows and click Save.
8
Click Add a permission.
9
Select the APIs my organization uses tab.
10
Search for Office 365 Exchange Online and click Office 365 Exchange Online in the search result.
11
Select Delegated permissions.
12
Select EWS.AccessAsUser.All.
13
Click Add permissions.
14
Keep the default User.Read permission.
15
Click Grant admin consent for <Your Organization> and click Yes to confirm.

Installing the Exchange Online PowerShell module

To use OAuth modern authentication for data sources that connect to hybrid or native Office 365 through remote PowerShell, the Exchange Online PowerShell module (v1 or v2) must be installed on your computer.

Data sources that connect to Exchange Online using remote PowerShell are:

Perform the following steps in a browser that supports ClickOnce such as Microsoft Internet Explorer or Edge.

2
In the EAC, go to Hybrid | Setup and click the appropriate Configure button to download the Exchange Online PowerShell module for multi-factor authentication.

If you want to install the Exchange Online (v2) module, you can follow the instructions in the Microsoft article titled Install and Maintain the Exchange Online PowerShell V2 Module.

Setting up a multi-forest environment with a one-way trust

You can configure UC Analytics to support multiple forests that have a one-way trust. In the following example of a one-way trust scenario, the forests are configured as follows:

UC Analytics is installed in the resource forest (Forest R). The UC Analytics Data Engine service is running with Forest R credentials. For this scenario, you would perform the following steps to allow users from the trusted domain (Forest A) to access UC Analytics:

Once the second environment (for Forest A) is added and an authentication account from Forest A is specified for authentication, User X can log on to UC Analytics. For information about adding target environment for an additional Active Directory forest, see Adding multiple Active Directory forests .

User X can view the data in the insights based on the security permissions that were granted to the ForestA\Group in the Security settings. When you add users in the Security settings, ensure that the Forest A target environment is selected when you add the Forest A users. For information about the Security settings, see Granting users access to data .

Appendix B:Configuring the Skype for Business or Lync Server

For UC Analytics to collect statistical data from a Skype for Business or a Lync server, the Monitoring role must be installed on the Skype for Business or Lync server and Call Detail Recording (CDR) must be enabled and running.

See the following sections for the steps to configure your Lync or Skype for Business server.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级