Chatta subito con l'assistenza
Chat con il supporto

Unified Communications Analytics 8.8.1 - 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

Recommendations for disaster recovery

For disaster recovery planning, there are two options that you can consider.

•
Use redundant storage such as a RAID array when you install UC Analytics.
•
Back up your configuration and data storage.
To back up the UC Analytics configuration and data
1
Stop all the UC Analytics services:
•
UC Analytics Data Engine
•
UC Analytics Query Engine
•
UC Analytics Storage Engine
2
On each computer on which the Storage Engine is installed, back up your storage folder. By default, the storage directory is located in the following path:
C:\Program Files\Quest\UC Analytics\Storage
3
Start all the UC Analytics services.
To restore the UC Analytics configuration and data
1
Stop all the UC Analytics services:
•
UC Analytics Data Engine
•
UC Analytics Query Engine
•
UC Analytics Storage Engine
2
On each computer on which the Storage Engine is installed, restore your storage folder. By default, the storage directory is located in the following path:
C:\Program Files\Quest\UC Analytics\Storage
3
Start all the UC Analytics services.

 

Appendix F:Custom configurations

Appendix F:
Custom configurations

This section contains information about how to configure and customize your deployment to meet specific requirements. See the following topics for instructions for the following customizations.

Setting LDAP connections to use LDAPS (LDAP over SSL)
Modifying the Data Query Availability job run
Modifying collection days for data collections from log files
Changing initial collection days for Exchange (Online) Mailbox Contents data sources
Changing default values for formatted .csv or .tsv file exports
Excluding insight date range and filters from subscription emails
Changing the PowerShell wait time after transient errors
Changing the PowerShell reconnect interval for Exchange Online Mailbox Configuration jobs
Modifying timeout values for EWS collection jobs
Setting a custom title page for exported or subscription insights
Changing the interval time before job status is purged
Configuring remote PowerShell to use the required proxy settings
Overriding PowerShell credential winnowing
Registry settings that affect service shutdown and startup

Setting LDAP connections to use LDAPS (LDAP over SSL)

By default the data sources that use LDAP (Lightweight Directory Access Protocol) to collect data use standard LDAP to connect.

You can modify the UC.Analytics.Insights.DataEngine.Service.exe.config file to use LDAPS for an LDAP over SSL connection. LDAPS is the non-standardized “LDAP over SSL” protocol that only allows communication over a secure port such as 636. For information about ports used by UC Analytics, see Firewall configuration: ports for data collection .

To modify LDAP connections to use LDAPS
1
Using a text editor, open the UC.Analytics.Insights.DataEngine.Service.exe.config file.
By default, the file is located in C:\Program Files\Quest\UC Analytics\Data Engine.
2
Locate the following section and parameter:
<appSettings>
<add key="enableLdaps" value="false" />
3
Change the "false" value to "true" and save the file.
4
Restart the UC Analytics Data Engine service.

Modifying the Data Query Availability job run

The Data Query Availability job (which runs in the background) is split into two parts: one part for the most recent shards and one part for more distant shards. How often each part is run can be configured separately to reduce the number of times the job runs and to create an interim version of a shard while gatherings are still collecting and writing the data for the shard.

By default, both the “most recent” shards (within the last 3 days) and the “more distant” shards (older than 3 days) are still committed every hour.

Using a text editor, you can modify the values for each Data Query Availability job type under the commitJobSettings section in the UC.Analytics.Insights.DataEngine.DataCollector.dll.config file.

The file is located in C:\Program Files\Quest\UC Analytics\Data Engine.

In the commitJobSettings section:

runFrequencyForRecentShardsInMinutes="60"
runFrequencyForDistantShardsInMinutes="60"
numberOfShardsBetweenNearEnd="3"
numberOfShardsBetweenFarEnd="-1"

You can modify the job run frequency for each part separately. For example, you might set recent shards to run every 3 hours and more distant shards every 12 hours.

runFrequencyForRecentShardsInMinutes is the number of minutes between the Data Query Availability job runs to merge "recent shards".
runFrequencyForDistantShardsInMinutes is the number of minutes between the Data Query Availability job runs to merge "distant shards".
numberOfShardsBetweenNearEnd sets number of shards considered to be "recent shards." A setting of 3 means "recent shards" are the three shards for the most recent three days.
numberOfShardsBetweenFarEnd sets the last shard included in "distant shards." Leave setting at -1 to include all remaining shards not included in "recent shards".

When you view data collection status on the Data Collection Status page, you will see two Data Query Availability jobs which are responsible for committing both recent shards and distant shards.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione