Chatee ahora con Soporte
Chat con el soporte

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

Changing the interval time before job status is purged

By default, UC Analytics purges the job status summary information for a data collection job 30 days after the job has run. UC Analytics purges the job status details information after 7 days. Depending on the size and number of your data collections, you might want to modify the time periods that UC Analytics will keep job status summary and details. You can configure UC Analytics to clean out job status details records separately from job status summary records.

For example, you might decide to keep job status summary records for longer than the job status details records since the details records will occupy much more space.

To change the time period for which UC Analytics will retain job run status summary and details records, you edit the UC.Analytics.Insights.DataEngine.DataCollector.dll.config file.The configuration file is located in the data engine directory on the server that hosts a data storage engine.

To change the retention period for the job status details records, change the 30 beside retentionPeriodInDays= to the number of days that you want retain the job status details data.

Configuring remote PowerShell to use the required proxy settings

For the Exchange Online data sources, if your environment requires explicit proxy settings to access the internet, you must configure the Exchange Online data sources to use the required proxy settings.

Locate the following text in four locations in the UC.Analytics.Insights.DataEngine.DataCollector.dll.config file:

These settings affect all Exchange Online data sources that use a remote PowerShell connection.

For more information about the Microsoft PowerShell proxy settings, search for New-PSSessionOption in the Microsoft PowerShell documentation web site.

Overriding PowerShell credential winnowing

In the Exchange Online Hybrid Mailbox Configuration and the Exchange Online Native Mailbox Configuration data sources, you can specify multiple credentials that are used to connect to Exchange Online using remote PowerShell. Sometimes, an invalid credential might be specified such as an incorrect password.

When UC Analytics connects to Exchange Online through PowerShell, if a credential cannot connect, it assumes the credential is invalid and removes the credential from the list of credentials that is being used to connect. This process of removing invalid credentials is called “winnowing”. However, in some cases the credential may be valid and inability to connect is caused by Microsoft throttling of the PowerShell connections.

If you are sure all the PowerShell credentials you have specified are valid, you can edit a configuration file to override the winnowing process.


Registry settings that affect service shutdown and startup

The UC Analytics servers may be rebooted for different reasons, such as Windows Update installations. Sometimes, for computers that are heavily loaded, a reboot may cause issues if services are not allowed enough time to shut down or to start.

As of release 8.5.1, two sections in the Windows registry are updated during installation to mitigate the effects of shutting services down too quickly or not allowing services enough time to start.

Some users experienced an issue where the monthly Windows Update installation and computer reboot caused a corrupted Commit log (size is 0 kilobytes) which stopped the Storage Engine service from restarting. The computer would reboot and the Storage engine service would restart but then quickly shut down.

The issue can occur when the Storage Engine is shut down too quickly, either by Windows Update or by an administrator. A registry value controls how many milliseconds Windows will wait for services to clean up and save data before closing. The default value is 5000 milliseconds (5 seconds) for most operating systems which may not be enough time if a computer is heavily loaded.

As of release 8.5.1, the WaitToKillServiceTimeout registry setting has been updated to allow the UC Analytics Storage Engine enough time to properly shut down.

The registry key is at the following location:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control > WaitToKillServiceTimeout

After installation, the new value is set to 900000 (milliseconds).

As of release 8.5.1, another Windows registry setting was updated to allow UC Analytics services enough time to restart. Some customers would experience system timeouts when the Data Engine service was restarting.

The timeout value for the service startup in the Windows registry has been changed. In the following registry location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control, a new DWORD Value, was created for ServicesPipeTimeout.

The value of ServicesPipeTimeout is set to 60000 (milliseconds).​

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación