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

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

Configuring UC Analytics for resource forests

Configuring UC Analytics for resource forests

If you have resource forests, typically your active (enabled) user accounts are in one forest and the Exchange / Skype for Business (Lync) resources (such as mailboxes) are in a different forest. In other cases, there might be a mix of user accounts and resources in a single forest.

You must configure UC Analytics to collect the Active Directory information from the account and resource forests and to collect the Exchange and Skype for Business (Lync) information from the resource forests.

Adding target environments

For each forest that contains Active Directory accounts and/or Exchange / Skype for Business (Lync) resources, you must:

•
add a target environment for each forest that hosts Exchange (pure resource forest).
•
add a target environment for each forest that hosts Skype for Business or Lync (pure resource forest).
•
add a target environment for each forest that hosts the Active Directory accounts that access Exchange and/or Skype for Business (pure account forest).
•
add a target environment for each forest that hosts the Exchange resources, Skype for Business resources, and any Active Directory accounts used to access Exchange and Skype for Business (blended forest).
Configuring data sources

For each forest target environment, you must add a Domain Controller data source.

For each forest target environment that hosts Exchange resources (both pure resource forests and blended forests), you must add the Exchange data sources (such as the Exchange Configuration and IIS Log Files data sources).

For each forest target environment that hosts Skype for Business / Lync resources (both pure resource forests and blended forests), you must add Skype for Business / Lync data sources (such as the Skype for Business / Lync Configuration and the Skype for Business / Lync CDR Database data sources).

Resource forest configuration process

In the Admin Settings, the configuration process is as follows:

1
In Target Environments, add a target environment for each forest that:
•
hosts the Active Directory users that are used to access Exchange or Skype for Business (Lync)
•
hosts Exchange resources.
•
hosts Skype for Business (Lync) resources.
2
In Data Collection, add a Domain Controller data source in each of the target environments.
The data source collects the Active Directory objects of each forest. The Domain Controller data source is also needed in a resource forest to collect the security groups and distribution groups.
For Exchange resource forest configuration
3
In Data Collection, add an Exchange Configuration data source in each target environment of a forest that hosts Exchange resources. Configure as usual with the following extra steps:
a
In each Exchange Configuration data source, select the Search additional forests for master accounts of linked mailboxes check box.
The additional Account Forest LDAP Connection Parameters are displayed.
b
Specify whether the domain controller for the account forest should be automatically discovered or enter a specific domain controller.
c
Enter the additional LDAP connection parameters to the account forest that contains the master accounts for the Exchange-linked mailboxes.
The additional LDAP credentials are needed to resolve the master account SID of linked mailboxes to the distinguished name of the master account in the account forest.
For Skype for Business (Lync) resource forest configuration
4
In Data Collection, add a Skype for Business / Lync Configuration data source in each target environment of a forest that hosts the Skype for Business (Lync) resources. Configure as usual with the following extra steps:
a
In each Skype for Business / Lync Configuration data source, select the Search additional forests for user accounts for the linked Skype for Business / Lync services check box.
The additional Account Forest LDAP Connection Parameters are displayed.
b
Specify whether the domain controller for the account forest should be automatically discovered or enter a specific domain controller.
c
Enter the additional LDAP connection parameters to the account forest that contains the primary Skype for Business (Lync) user accounts.
The additional LDAP credentials are needed to resolve the Skype for Business (Lync) originator SID of the resource (disabled) accounts to the distinguished name of the primary account in the account forest.
Resource forest: collecting from active and disabled user accounts

In a resource forest configuration, both the active (master or primary) user account and the disabled (stand-in) user account can have values specified for the user properties. UC Analytics collects these properties as follows:

•
If a property is multi-valued, such as email addresses, UC Analytics collects the values from both the master and stand-in accounts.
•
If the property is single-valued, such as department, UC Analytics collects the values from both the master and stand-in accounts. When the value is present in both accounts, the stand-in account value is used with the following exceptions which are always collected from the master account:
•
Name
•
First Name
•
Initials
•
Last Name
•
SAM Account Name
•
OU
•
Object GUID
•
Object Type
 
* 
NOTE: If a master mailbox (Exchange) or primary user (Skype for Business) is associated with more than one stand-in (linked mailbox or disabled account) in more than one resource forest, single- valued properties can be populated from any one of the stand-ins.

Adding a target environment for native Office 365

If you have a native Office 365 environment, without on-premise Exchange or Active Directory, you can add a Office 365 target environment to connect directly to your native Office 365 environment.

To add a target environment for native Office 365
1
Click the gear icon on the home page side bar.
2
Click Target Environments and click + beside Target Environments.
3
Select Office 365 (native).
4
Under Name, click Office 365 (native).
5
Enter a descriptive name for the environment and click Apply.
Authentication
6
To use this environment for authenticating users, select the check box beside Allow users from this target environment to log in to UC Analytics.
This setting only controls whether the users from this target environment can log in to UC Analytics. You control the types of data that users can view in the insights through the Admin Settings | Security section. For information, see Granting users access to data .
7
Click Set credential and enter the Office 365 credential to be used to resolve user security settings for users that log in with Office 365 credentials.
8
Click Set.
Office 365 Native 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 .
9
Click Set Azure application ID and enter the Azure application (client) ID that was registered for UC Analytics with the Microsoft Azure portal.
10
Select Use specific connection URLs under Office 365 Native Connections.
11
Click Set URLs.
12
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
13
Click Set and click Save.

Setting the time period for retaining data

On the Data Collection page, you can set the amount of time that data is retained by the UC Analytics Storage Engine. This feature allows you to automatically age data from the Storage Engine database to manage the amount of storage required.

The data aging job runs automatically at midnight (local time).

If you have the data retention period set for a longer period such as 365 days and you reduce the number of days for retention, you cannot later recollect the older data that was not retained. If you increase the number of days, the change only affects new message or session activity.

To set the data retention time period
1
Click Data Collection.
2
Enter the number of days that you want data to be retained in the Data Retention Length (days) field.

Setting the start date for data collection

On the Data Collection page, you set the date that you want data collection to start. By default, the initial data collection is set to start 30 days back for on-premise data sources and one day for Office 365 (Exchange Online) data sources.

For on-premise data sources, if you have stored data that goes more than 30 days back, you might want to change the start date for data collection. For example, typically Exchange tracking logs are retained for 30 days. If you normally archive your Exchange tracking logs and have logs that go back beyond 30 days, you could set the data collection start date to reflect the actual dates for the data that you have stored.

To set the data collection start date
1
Click Data Collection.
2
Enter the start date for which data is to be collected in the Data Collection Start Date field.

You can only change the start date if you have not added any data sources yet.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택