지금 지원 담당자와 채팅
지원 담당자와 채팅

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

How do I set a user to be a product administrator?

When you install UC Analytics, you can add users as product administrators during installation. A product administrator has unrestricted access to all the configuration settings under the Admin Settings for all tenants (target environments).

After installation, to add additional administrators you can use the UC Analytics Deployment Manager from the Start menu.

To access the Deployment Manager
1
Click Start and select Programs | Quest UC Analytics | UC Analytics.
2
Select the Change Product Administrators option.
About multi-tenant environments

For implementations in which you have multiple tenants, you can add separate environments for each tenant. In this case, you could add tenant administration rights for a specific environment to an account. The account would be the tenant administrator only for the tenant environment.

For information about configuring an account with access to the admin settings for a specific environment (tenant), see Adding a tenant administrator .

Configuration process overview

If your user account is set as a product administrator or with access to Tenant Configuration (tenant administrator), you can configure UC Analytics using the Admin Settings. The following steps provide a sample workflow for an initial configuration and identify the tile (in parentheses) in which you enter the configuration.

1
Click the gear icon on the home page side bar to access Admin Settings.
2
Review the target environment used to create the initial connection. (Target Environments)
3
Add any additional target environments such as another Active Directory forest or a native Office 365 deployment. (Target Environments)
4
Add and configure the data sources used to create the data collections that gather data. (Data Collection).
For information about configuring each type of data source, see the following sections:
•
Adding data sources for Active Directory or Azure Active Directory
•
Adding data sources, chargeback costs, and thresholds for Exchange and Exchange Online
•
Adding data sources, chargeback costs, and thresholds for Skype for Business/Lync
•
Adding data sources, chargeback, and thresholds for Cisco
5
Set a data aging time period for the data you collect (Data Collection).
6
Set the initial data collection start date (Data Collection).
7
Identify the domains that are internal to your environment (Classifications | Domain Classifications).
This information is used in insights to identify internal and external message traffic and Skype for Business/Lync activities.
8
Specify classifications that map to specific domains (Classifications | Domain Classifications).
The classifications are used to group the Exchange messaging, Skype for Business/Lync session and conference data, and Cisco session and conference in the insights.
9
Set security to set the levels of access to the Exchange, Skype for Business/Lync, and Cisco data that each user has when viewing insights (Security).

Other configuration tasks can include:

•
Specifying words that should be omitted when filtering for subject keywords (Queries).
•
Entering the call classifications for the different Skype for Business/Lync or Cisco call types (Classifications | Call Classifications).
•
Entering the cost values to be used for chargeback insights (Chargeback).
•
Configuring the global settings that are used by user-created subscriptions for insights (Subscriptions).
For more information about subscriptions, see the section titled “Automatically creating and sending insights” in the UC Analytics User Guide.

Modifying the initial target environment

When you install UC Analytics, the installer creates an initial target environment. By default, the target environment is the Active Directory forest (or workgroup) in which UC Analytics is installed. The target environment is used to collect data and to provide users with access to the UC Analytics web site.

Check the initial target environment to verify that the default credentials being used for authentication have the required permissions. For more information, see About the authentication credential .

For Office 365, the initial target environment is set by default for the Microsoft global network of data centers. In addition to the global cloud, Microsoft cloud services are available in separate national clouds. National clouds are physically and logically isolated networks, located within the geographic borders of certain countries and operated locally.

Current national clouds include:

•
Azure and Office 365 operated by 21Vianet in China
•
Microsoft Cloud Germany
•
Microsoft Cloud for US Government

If you are accessing Office 365 through a Microsoft national cloud, you can set the connections used for Office 365 to use the national URLs.

To provide access for users or to collect data from outside the initial target environment, you can add a new target environment. You can add target environments to connect with other Active Directory forests or with a native Office 365 deployment:

•
If you have a hybrid Office 365 environment with users in both Office 365 and in Active Directory, you would add another Active Directory forest / Office 365 (hybrid) environment.
•
If you have a native Office 365 environment, you would add an Office 365 (native) target environment and allow your Office 365 users to be authenticated.
To review or modify the initial target environment
1
Click the gear icon on the home page side bar.
2
Click Target Environments.
By default, an environment is configured for the Active Directory forest in which you installed UC Analytics.
3
Click the tile for the forest.
4
Review the information. The Allow users from this target environment to log in to UC Analytics check box is selected. This indicates that the environment is used for authenticating users.
5
Specify an Authentication Credential, if necessary.
Office 365 Hybrid Connections
If you are using OAuth modern authentication to access Exchange Online using EWS, you must specify the Azure Application ID that is registered for UC Analytics. For information about registering an application with the Microsoft Azure portal, see Registering UC Analytics with the Microsoft Azure portal .
For remote PowerShell access to Exchange Online using OAuth modern authentication, you must install the Exchange Online PowerShell module. For more information, see Installing the Exchange Online PowerShell module
6
Click Set Azure application ID and enter the Azure application (client) ID that was registered for UC Analytics with the Microsoft Azure portal.
7
Select Use specific connection URLs under Office 365 Hybrid Connections.
8
On the Set URLs dialog, if you are connecting to Office 365 Global, the default connections can be used.
If you are connecting to one of the Microsoft National clouds, you must enter the URL that is to be used for the remote PowerShell connection and the URL to be used for the Exchange Web Services (EWS) connection. To use OAuth modern authentication, for both EWS access and remote PowerShell access, you must enter the Azure AD Authorization Endpoint URL.
For example, to connect to Office 365 operated by 21Vianet in China, you could enter:
Remote PowerShell URL:
https://partner.outlook.cn/PowerShell-LiveID
Exchange Web Services (EWS) URL:
https://partner.outlook.cn/EWS/Exchange.asmx
Azure AD Authorization Endpoint URL:
https://login.chinacloudapi.cn/common
9
Click Set and click Save.
About the authentication credential

If you have a single forest, you typically do not need to specify an Authentication Credential in the default target environment. By default, the credentials specified for the Data Engine service are used to verify user permissions.

However, in secure environments, you might need to restrict rights for the UC Analytics service account. You could install UC Analytics using a local computer account or using a domain account with restricted rights.

In this case, you specify an Authentication Credential in the default environment to allow users to access UC Analytics:

•
The credential must have read rights to the Active Directory forest specified in the target environment.
•
The credential must also have sufficient rights to browse users and groups and to resolve group memberships for all users and groups from this environment that are specified in the Security settings. For information about the Security settings, see Granting users access to data .

If you do not provide an authentication account or if the account has insufficient rights, the security settings to access data are not applied when user attempts to log in to UC Analytics. As a result, the user might be unable to log into UC Analytics or unable to access certain insights.

Adding multiple Active Directory forests

When you install UC Analytics, an initial target environment is created for the Active Directory forest in which you installed. You can add target environments for other Active Directory forests/Office 365 hybrid environments.

If you add target environments for additional Active Directory forests, there must be at two-way or a one-way trust between the forest from which you collect data and the forest in which UC Analytics is installed.

For detailed instructions about configuring target environments for a multi-forest environment with a one-way trust, see Setting up a multi-forest environment with a one-way trust .

To add an target environment for an additional Active Directory forest or Office 365 hybrid environment
1
Click the gear icon on the home page side bar.
2
Click Target Environments.
3
Click + beside Target Environments.
4
Select Active Directory Forest / Office 365 (hybrid).
5
Under Name, click Active Directory Forest / Office 365 (hybrid).
6
Enter a name to identify the forest and click Apply.
Connection
7
Under Forest Name, click the <None specified> field.
8
Enter a domain name associated with the forest
9
If necessary, enter the credential that is used to access Active Directory and resolve the forest.
10
Click Resolve Forest Name.
The name of the forest in which the domain resides is displayed.
11
Click Apply.
Authentication
12
If this environment is to be used for authenticating users, select the check box beside Allow users from this target environment to log in to UC Analytics.
13
Specify the credential if the credential is to be used for authentication and click Add.
Office 365 Hybrid Connections
If you are using OAuth modern authentication to access Exchange Online using EWS, you must specify the Azure Application ID that is registered for UC Analytics. For information about registering an application with the Microsoft Azure portal, see Registering UC Analytics with the Microsoft Azure portal .
For remote PowerShell access to Exchange Online using OAuth modern authentication, you must install the Exchange Online PowerShell module. For more information, see Installing the Exchange Online PowerShell module
14
Click Set Azure application ID and enter the Azure application (client) ID that was registered for UC Analytics with the Microsoft Azure portal.
15
Select Use specific connection URLs under Office 365 Hybrid Connections.
16
On the Set URLs dialog, if you are connecting to Office 365 Global, the default connections can be used.
If you are connecting to one of the Microsoft National clouds, you must enter the URL that is to be used for the remote PowerShell connection and the URL to be used for the Exchange Web Services (EWS) connection. To use OAuth modern authentication, for both EWS access and remote PowerShell access, you must enter the Azure AD Authorization Endpoint URL.
For example, to connect to Office 365 operated by 21Vianet in China, you could enter:
Remote PowerShell URL:
https://partner.outlook.cn/PowerShell-LiveID
Exchange Web Services (EWS) URL:
https://partner.outlook.cn/EWS/Exchange.asmx
Azure AD Authorization Endpoint URL:
https://login.chinacloudapi.cn/common
17
Click Set and click Save.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택