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

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

Creating an Exchange Mailbox Content Summary data source

The Exchange mailbox content summary data collection gathers folder statistics from user mailboxes using Exchange Web Services (EWS) and LDAP queries. You can also collect the dates for the last message sent and last message read in a mailbox which is used in the Mailboxes - Inactive (Advanced) insight.

When you configure a mailbox content summary data collection, you must specify the target mailboxes and the Client Access Server (CAS) URLs that are used to connect to the mailbox server. For Exchange 2016/2019, you specify the URL for the Client Access Services on the mailbox server.

When you specify target mailboxes, you can set all mailboxes, mailboxes for a specific mailbox server, mailboxes that belong to a specific organizational unit (OU), or specific mailboxes as targets.

 
* 
TIP: When specifying individual mailboxes as targets, it is recommended that you add the user mailboxes to a distribution group. You can then add the distribution group for the target mailboxes.

The data source collection does not include system mailboxes. For a list of the types of mailboxes that are excluded, see What types of mailboxes are excluded? .

If you have an Exchange hybrid environment, you can configure an Exchange Online Mailbox Content Summary data source to collect Office 365 mailboxes. For more information, see Creating an Exchange Online Mailbox Content Summary data source .

 
* 
TIP: For some fields you can enter multiple values separated by a semi-colon (;). For details, see Entering multiple values in a field .
About the Recoverable Items Folder

Under Data To Collect, in Mailbox Folders, you have the option to collect recoverable items which includes messages that are on litigation hold. Specifically, Exchange use the Recoverable Items folder to store messages that should be protected from deletion, either accidental or malicious, for future investigation.

The following Exchange features use the Recoverable Items folder:

•
Litigation Hold
•
Deleted item retention
•
Single item recovery
•
In-Place Hold
•
eDiscovery hold
•
Office 365 retention policies
•
Mailbox audit logging
•
Calendar logging
If you decide to collect from the Recoverable Items Folder, you can view the data in the following insight:
•
Mailboxes - Folders Inventory
The sizes of the \Recoverable Items folder and its subfolders are not counted in the Top of Information Store folder for the mailbox owner since both folders are at same level.
To set up a mailbox content summary data 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 Exchange Mailbox Content Summary check box.
5
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.
6
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
7
Specify the types of data to be collected.
•
Mailbox Folders
•
Recoverable Items Folder
For information about the Recoverable Items Folder, see About the Recoverable Items Folder .
•
Message Statistics.
•
Last Message Sent Date
•
Last Message Read Date
When specifying parameters to collect message statistics
8
If you select the option to collect Message Statistics, you can set a date range and collection scope:
a
Enter the number of days back that message statistics should be collected. By default, 180 days is set.
b
Select whether you want to collect statistics for the entire mailbox or only the default folders (Sent Items and Inbox).
Specifying the LDAP connection parameters
9
Specify the Windows credentials for the LDAP connection
- OR -
Select the Use Data Engine service credential option.
Specifying the target mailboxes
10
You have different options for specifying the target mailboxes to be included:
•
Select all mailboxes.
•
Specify the mailbox server for the mailboxes.
•
Specify the organizational unit (OU) to which the mailboxes belong.
•
Specify certain mailboxes that you want collected.
When specifying certain mailboxes you can enter the common name or email address of a mailbox, a group. or a dynamic distribution group. For more information about using a dynamic distribution group for target mailboxes, see Using dynamic distribution groups to select target mailboxes .
Specifying data collection parameters for EWS connection
11
Select the versions of Exchange from which you want to collect data:
•
Collect from mailboxes on all supported Exchange versions
•
Specify a specific Exchange version from which you want to collect data.
12
Specify the credential used to collect the mailbox data. For more information see Permissions needed for Exchange Mailbox Contents, Exchange Mailbox Content Summary, or Exchange Calendar data sources .
13
Specify the URLs for the CAS (Client Access Servers or Client Access Services) to be used by Exchange Web Services (EWS).
•
Use Exchange auto-discovery for each mailbox
•
Specify the specific Exchange Web Services URLs
* 
TIP: In many Exchange environments, Exchange auto-discovery does not always work so it is recommended that you specify individual Exchange Web Services URLs.
When you specify the CAS for the gathering, you must enter the URL for the server. For example, the URL might be:
https://MyCASServer/ews/Exchange.asmx
You can specify multiple CAS URLs to be used for the EWS gathering. If you specify multiple CAS URLs, data collection is faster. If you do not specify one or more CAS URLs, the Exchange Autodiscover service is used to find the CAS servers for the target mailboxes.
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.
If the Data Engine is in a different forest from the data to be collected, you must specify the domain controller you want to use for data collection. If you leave the default setting to automatically discover domain controller, the data collector selects a domain controller from the forest that hosts the Data Engine, not a domain controller from the forest from which you are collecting the data.
14
Click Save.

Creating an Exchange Calendar data source

Creating an Exchange Calendar data source

The Exchange calendar data source collects information about the Exchange meetings and appointments that users have created in Outlook. The data source retrieves the information from the targeted mailboxes using Exchange Web Services (EWS) and LDAP queries.

An appointment is a calendar item that users create for themselves that have no attendees other than the organizer. A meeting is a calendar item for which there are attendees in addition to the organizer. By default, insights that show Exchange meeting data have a preset filter that shows only meetings.

 
* 
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 Exchange calendar data 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 Exchange Calendar check box.
5
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 four 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.
6
Set the schedule for the data collection:
a
Click Minimum amount of time between job runs: 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
7
Specify the types of data to be collected.
By default, Exchange Meeting / Appointment Subject is selected.
Specifying the LDAP connection parameters
8
Specify the Windows credentials for the LDAP connection
- OR -
Select the Use Data Engine service credential option.
Specifying the target mailboxes
9
You have different options for specifying the target mailboxes to be included:
•
Select all mailboxes.
•
Specify the mailbox server for the mailboxes.
•
Specify the organizational unit (OU) to which the mailboxes belong.
•
Specify certain mailboxes that you want collected.
When specifying certain mailboxes you can enter the common name or email address of a mailbox, a group. or a dynamic distribution group. For more information about using a dynamic distribution group for target mailboxes, see Using dynamic distribution groups to select target mailboxes .
Specifying data collection parameters for EWS connection
10
Select the versions of Exchange from which you want to collect data:
•
Collect from mailboxes on all supported Exchange versions
•
Specify a specific Exchange version from which you want to collect data.
11
Specify the credential used to collect the Exchange calendar data. For more information see Permissions needed for Exchange Mailbox Contents, Exchange Mailbox Content Summary, or Exchange Calendar data sources .
12
Specify the URLs for the CAS (Client Access Servers or Client Access Services) to be used by Exchange Web Services (EWS).
•
Use Exchange auto-discovery for each mailbox
•
Specify the specific Exchange Web Services URLs
* 
TIP: In many Exchange environments, Exchange auto-discovery does not always work so it is recommended that you specify individual Exchange Web Services URLs.
When you specify the CAS for the gathering, you must enter the URL for the server. For example, the URL might be:
https://MyCASServer/ews/Exchange.asmx
You can specify multiple CAS URLs to be used for the EWS gathering. If you specify multiple CAS URLs, data collection is faster. If you do not specify one or more CAS URLs, the Exchange Autodiscover service is used to find the CAS servers for the target mailboxes.
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.
13
Click Save.

Creating an Exchange Public Folders data source

By configuring an Exchange public folders data source, you can collect statistics for your legacy public folders (Exchange 2010) and for your new public folders (Exchange 2013/2016/2019). You can use the public folder insights to track your migration from legacy to new public folders.

For information about what permissions are required by the credentials for the data collection, see Permissions needed for the Exchange Public Folders data source .

 
* 
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 Exchange public folders 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 Exchange Public Folders check box.
5
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 hour, 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.
6
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
7
Select the types of data that you want to collect. In addition to statistics, you have the option to collect empty public folder mailbox data and public folder permissions.
•
By default, UC Analytics collects only public folder mailboxes that contain public folders. If a public folder mailbox is empty, UC Analytics skips that mailbox. If you want to collect information about empty public folder mailboxes, select the Empty Public Folder Mailboxes check box.
•
Collecting public folder permissions can be resource intensive. It is recommended that you create a separate instance of the Exchange Public Folders data source to collect permissions and select User permissions (Client permissions).
Selecting targets
8
Under Targets, select All Public Folders or enter the folder paths for specific public folders.
9
Specify the type of public folders that you are collecting.
•
If you are collecting Exchange 2010 (legacy) public folders, click Exchange 2010.
a
If Exchange 2010 is the highest Exchange legacy version, enter the Exchange CAS server and specify the credential to be used to create the remote PowerShell connection.
•
If you are collecting Exchange 2013/2016/2019 public folders (new), click Exchange 2013/2016/2019.
a
Enter the Exchange CAS server and specify the credential to be used to create the remote PowerShell connection.
Advanced settings (not required for most deployments)
•
To use HTTPS instead of HTTP to connect to the Exchange CAS server, click Show Advanced Settings in the Credential section. This option requires that TLS/SSL is enabled for remote PowerShell on the Exchange CAS server.
The Advanced Settings also provide options if you have a customized PowerShell virtual folder, or if you want specify either an implicit credential or the Data Engine credential be used to make the PowerShell connection.
10
Click Save.

Adding Exchange Online hybrid data sources for hybrid Office 365

If you have a hybrid Exchange Online (on-premise and Exchange Online) environment, there are four data sources that you configure to collect from your hybrid Office 365 environment.

•
Exchange Online Hybrid User Configurations which retrieves user and distribution group data using LDAP and remote PowerShell. See Creating an Exchange Online Hybrid User Configuration data source .
•
Exchange Online Hybrid Mailbox Configuration which retrieves Exchange Online mailbox configuration including statistics, permissions and mobile devices. See Creating an Exchange Online Hybrid Mailbox Configuration data source .
•
Exchange Online Mailbox Contents which retrieves information about email traffic from Exchange Online user mailboxes using Exchange Web Services (EWS) and remote PowerShell. You can collect from some or all mailboxes. See Creating an Exchange Online Mailbox Contents data source .
•
Exchange Online Mailbox Content Summary which retrieves statistics about mailbox folders from Exchange Online user mailboxes using Exchange Web Services (EWS). See Creating an Exchange Online Mailbox Content Summary data source .
•
Exchange Online Calendar which retrieves information about appointments and meetings that your users have created in Outlook Online. See Creating an Exchange Online Calendar data source .
•
Exchange Online Public Folders which collect statistics and configuration information for your Exchange Online public folders using PowerShell. See Creating an Exchange Online Public Folders data source .
 
* 
NOTE: The Exchange Online Mailbox Contents, the Exchange Online Mailbox Content Summary, and the Exchange Online Public Folders data sources can be added to an Active Directory Forest / Office 365 (hybrid) target environment to collect from hybrid Exchange Online or added to a native Office 365 target environment to collect from native Exchange Online.
Must I add an Office 365 (native) target to collect native objects in an Exchange hybrid environment?

My hybrid environment contains mailboxes and groups that were migrated from on-premise Exchange and mailboxes and groups that were created directly in Office 365. Do I need to configure Office 365 native data sources to collect native objects?

Answer

Only one target, an Active Directory Forest / Office 365 (hybrid) target, is needed for hybrid environments.

The hybrid Exchange Online data sources collect all hybrid objects, both the objects created on-premise and migrated to Office 365 and the objects created in Office 365 (Office 365 native objects). For example, when collecting groups, the Exchange Online Hybrid User Configuration data source collects both

•
hybrid groups (created on-premise and migrated to Office 365)
•
Office 365 native groups (created in Office 365).

If you were to add an Office 365 (native) target and run the Exchange Online native data source collections, the hybrid objects would be duplicated.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级