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

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

Adding data sources for Active Directory / Office 365 (hybrid)

If you have an Active Directory on-premise or hybrid environment, there are two data sources that you can configure:

•
Domain Controller which collects information about users, groups, and mail contacts from Active Directory using LDAP. See Creating an Domain Controller data source .
•
Office 365 User Subscription Configuration which retrieves Office 365 user subscription information including licenses and services provisioning status. See Creating a data source for Office 365 user subscription configuration .

Creating an Domain Controller data source

When you create a data collection for Active Directory, you configure the Domain Controller data source. The data collection collects information about users, groups, and mail contacts from Active Directory using LDAP.

If you have created more than one Active Directory forest target environment, remember to add a Domain Controller data source for each environment.

By default, the Domain Controller data source collects only direct members of groups. For example, if a distribution group contained 10 users and 14 distribution groups, the number of direct members would be counted as 24.

If you want to collect the effective members (direct and indirect) for a group you can use the Advanced settings in the Collect Effective (Direct and Indirect) Members for Groups section. For example, if you collect from a distribution group that has 10 user members and one distribution group member (that has 20 members), the number of direct members is 11 but the number of effective members is 30.

You can also restrict the data collection to collect from specific organizational units (OUs).

 
* 
TIP: For some fields you can enter multiple values separated by a semi-colon (;). For details, see Entering multiple values in a field .
To set up an Active Directory collection
1
Click the gear icon on the home page side bar.
2
Click Data Collection.
3
Click + beside the name of the target environment.
4
Select the Domain Controller check box.
5
Click the Domain Controller tile to open the configuration page.
6
Enable the data collection for the data source.
 
* 
NOTE: If you have installed more than one Data Engine (Collector), you have the option to select a different computer that hosts a data collector.,
Modifying the collection schedule
By default the data collection is set to run every 6 hours, aligned to midnight UTC. You can modify the run interval or you can set the collection to run at a specific time on specific days.
7
Set the schedule for the data collection:
a
Click Run job every: and select an hourly interval.
- OR -
b
Click Run job at: and select the specific job run time, the number of days between each job run, and a start date.
Selecting data to collect
8
Select the types of data that you want to collect.
•
Users
•
Distribution Groups (static distribution groups and security groups
•
Mail Contacts
•
Dynamic Distribution Groups
•
Direct Members
By default, the data source collection gathers direct members of standard distribution and security groups. If you want to also collect direct members for dynamic distribution groups, select the Direct Members check box under the selected Dynamic Distribution Groups check box.
Setting the LDAP connection parameters
9
Specify the credentials to be used by LDAP to collect from Active Directory.
If the Data Engine service credentials have read permissions on the Active Directory user objects, you can use Data Engine service account to collect from Active Directory.
Targets
10
Select the targets of the data collection:
•
All Active Directory objects
- OR-
•
Active Directory objects within specific organizational units (OUs).
Advanced settings (not required for most deployments)
•
If you want to specify one or more explicit domain controllers instead of automatically discovering the domain controller, click Show Advanced Settings in the LDAP Collection Parameters section. For more information, see Specifying explicit domain controllers for LDAP connections . The domain controller must be a global catalog server.
•
By default, the Domain Controller data source collects direct members of groups. If you want to collect effective members (direct and indirect) for groups, click Show Advanced Settings in the Collect Effective (Direct and Indirect) Members for Groups section. You can select to collect effective members for specified groups or for all groups.
If you select Effective members for specific groups and click Add group, you have the option to add each group individually or you can enter a list of groups, each entry separated by a semi-colon (;).
 
* 
IMPORTANT: If you collect effective membership for many groups, it can have significant impact on performance and storage requirements.
11
Click Save.

For information about creating Domain Controller data sources for a resource forest configuration, see Configuring UC Analytics for resource forests .

Creating a data source for Office 365 user subscription configuration

The Office 365 user subscription configuration data source is used to gather Office 365 user subscription information including licenses and service provisioning status using remote PowerShell. You can create the data source for both native and hybrid Office 365.

•
For a hybrid Office 365 implementation, you add the Office 365 user subscription configuration data source in an Active Directory Forest / Office 365 (hybrid) target environment.
•
For a native Office 365 implementation, you add the Office 365 user subscription configuration data source in an Office 365 (native) target environment.
* 
NOTE: Office 365 data sources are not displayed in the Data Collection page until you have added Office 365 as a target environment. For more information, see Adding a target environment for native Office 365 .

For more information about credential prerequisites, see Permissions needed for the Office 365 user subscription configuration data source .

To set up an Office 365 user subscription configuration collection
1
Click the gear icon on the home page side bar.
2
Click Data Collection.
3
Click + beside the name of either an Active Directory / Office 365 (hybrid) target environment or an Office 365 (native) target environment.
4
Select the Office 365 User Subscription Configuration check box.
5
Click the Office 365 User Subscription Configuration tile to open the configuration page.
6
Enable the data collection for this data source.
 
* 
NOTE: If you have installed more than one Data Engine (Collector), you have the option to select a different computer that hosts a data collector.,
Modifying the collection schedule
By default the data collection is set to run every 6 hours, aligned to midnight UTC. You can modify the run interval or you can set the collection to run at a specific time on specific days.
7
Set the schedule for the data collection:
a
Click Run job every: and select an hourly interval.
- OR -
b
Click Run job at: and select the specific job run time, the number of days between each job run, and a start date.
Selecting data to collect
8
Select the data that you want to collect.
9
Specify the Office 365 credential used to collect the user configuration data through PowerShell.
10
Click Save.

Adding data sources for native Office 365

Adding data sources for native Office 365

If you have a native Office 365 environment, there are one data source that you can configure to collect from Azure Active Directory using remote PowerShell:

•
Office 365 User Subscription Configuration which retrieves Office 365 user subscription information including licenses and services provisioning status.
For information about how to configure the Office 365 User Subscription Configuration data source, see Creating a data source for Office 365 user subscription configuration .
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택