Converse agora com nosso suporte
Chat com o suporte

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

What types of mailboxes are excluded?

The Exchange Configuration and the Exchange Mailbox Content Summary data source collections do not include the following types of mailboxes:

•
Arbitration Mailbox
•
Mailbox Plan
•
Discovery Mailbox
•
Public Folder Mailbox
•
Monitoring Mailbox
•
Audit Log Mailbox
•
Mailboxes with a name that starts with "SystemMailbox{"
•
Mailboxes with a name that starts with "CAS_{"
 

Can I enter the Domain Users group as the target for the data collection?

When you specify target users for data collections, you can use distribution or security groups. However, UC Analytics does not support the group Domain Users as a target group. Domain Users is a special Microsoft group that does not contain a membership setting so UC Analytics cannot resolve it. UC Analytics supports all the groups with membership information. You can check a group's membership setting using the ADSI Edit tool or ADAC (Active Directory Administrative Center).

For Exchange configuration, the data collection gathers the configuration for mailboxes, not for users. For this reason, it is not recommended that you use a group such as Domain Users that contains users without mailboxes, mail contacts, and other types of recipients. The data collection will complete but it will be full of warnings in the job details for every “not applicable” user.

When creating a group to use as a target, it is recommended you create a static group with a specified membership or create a dynamic group. For a dynamic group, select the check boxes for users with Exchange mailboxes. That will cover all the Exchange mailboxes in the organization. For static groups, use only groups that have members with Exchange mailboxes and do not include any other kind of users.

Troubleshooting the Exchange configuration collection

In some situations, if you are collecting mailbox properties from an Exchange server without using TLS/SSL, you might see error messages such as the following:

“Connecting to remote server failed with the following error message: The WinRM client cannot process the request. Unencrypted traffic is currently disabled in the client configuration. Change the client configuration and try the request again. For more information, see the about_Remote_Troubleshooting Help topic.”

You must enable unencrypted traffic for the WinRM client. You can use the Local Group Policy Editor to modify the WinRM client settings.

To enable unencrypted traffic
1
Click Start, type gpedit.msc in the Start Search box and press ENTER to open the Local Group Policy Editor.
2
In the tree view, navigate to Local Computer Policy | Computer Configuration | Administrative Templates | Windows Components | Windows Remote Management (WinRM) | WinRM Client.
3
Enable the following settings:
•
Allow unencrypted traffic
•
Trusted Hosts
4
Select the Trusted Hosts setting.
5
Enter the servers to which you want to connect in the Trusted Hosts list. Wild cards are accepted.

Creating an Exchange Tracking Logs data source

Creating an Exchange Tracking Logs data source

The Exchange tracking log collection gathers email message information for all mailboxes. You must gather the Exchange message tracking logs from all Exchange hub transport servers and all Exchange mailbox servers. If you have historical tracking logs stored in a central location, you can gather from those tracking logs as well. To configure the Exchange tracking log data collection, you specify the following:

•
the scope of the mailboxes data to be collected (all or specific OUs)
•
the locations of the Exchange message tracking log shares from which you want to gather data
•
the credentials used to access the tracking logs

For information about the permissions needed, see Permissions needed for the Exchange Tracking Logs data source .

To set up an Exchange tracking log 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 Tracking Logs 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 Execute job every: and select an hourly interval.
- OR -
b
Click Execute 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.
•
DLP (Data Loss Prevention) Matches (DLP data is collected only for Exchange 2013 and later.)
•
Email Messages
•
Subject
•
Recipient Status (If you select this option, the required disk space is significantly increased.)
LDAP Connection Parameters
8
Specify credentials to be used for the LDAP connection or select the Use Data Engine service credential option.
Targets
9
Select whether you want to collect data for all Exchange mailboxes or for only the mailboxes in specified organizational units (OUs).
If you specify an OU, you must enter the OU distinguished name.such as OU=OU,DC=Sitracka,DC=COM.
Tracking Log Collection Parameters
10
Specify each folder location from which the tracking logs are to be gathered.
11
Specify the credentials that are used to gather the Exchange tracking logs.
Advanced settings (not required for most deployments)
•
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. If you 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 data.
12
Click Save.
About collecting historical tracking logs

Tracking logs from each Exchange server have the same file name format, so you must have a separate folder for each server. Do not change the tracking log file names. The naming convention for the message tracking log files is as follows:

MSGTRKyyyymmdd-nnnn.log
MSGTRKMAyyyymmdd-nnnn.log
MSGTRKMDyyyymmdd-nnnn.log
MSGTRKMSyyyymmdd-nnnn.log

When you configure the tracking log data collection, specify each folder from which you are gathering tracking logs.The data collection job goes through the files each time it is scheduled to run (every hour by default). However, the job reads only new changes (new files or files that have changed since the last time the job ran). This method allows the data collection job to collect and update the data in a timely manner without reading the log files multiple times.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação