Chat now with support
Chat with Support

Unified Communications Analytics 8.6.1 - Release Notes


The following is a list of enhancements implemented in UC Analytics 8.6.1.

If you have a configuration file with custom settings that is backed up to the Backup Config Files\Data Engine folder, when you upgrade UC Analytics automatically updates the affected configuration files with the customized values. For more information, see About custom settings in configuration files .


You can now create a support bundle that includes more than 30 log files for each job from UC Analytics Support\DataSourceLogs. In the Deployment Manager.exe utility, the Create Support Package option has been modified to allow you to specify the number of logs to be included in the support package. You can set the number of:


To handle a situation in which a new data source must collect Exchange tracking logs or IIS logs that were previously collected, a new option called initialDataCollectionDays is added to the UC.Analytics.Insights.DataEngine.DataCollector.dll.config file to allow you to specify the number of initial collection days. For more information, see the UC Analytics Deployment Guide chapter titled “Making changes to your deployment”.


The Exchange Tracking Logs data source can now collect recipient-status for each message recipient. In the Exchange Tracking Logs data source, you can select a new type of data to collect, Recipient Status, under Email Messages. If you decide to collect Recipient Status, the required disk space is significantly increased.

If you collect this data, you can add a Recipient Status column and filter using Recipient Status in insights such as insights such as Email - Details. For example, you could add the column using the following steps:

Click Manage field columns and select Show advanced fields.
Search for Status and select Recipients | Recipient Status.


The Exchange Configuration, the Exchange Online Native/Hybrid User Configuration, and the Exchange Online Native/Hybrid Mailbox Configuration data sources now collect the ForwardingSmtpAddress attribute for mailboxes.

You can add the Forwarding SMTP Address column to insights such as Mailboxes - Inventory or Mailboxes - Activity Summary or filter insights by Forwarding SMTP Address.

For example, to add the column to the Mailboxes - Activity Summary insight, you would do the following steps:

Click Manage field columns and select Show advanced fields.
Search for SMTP and select Exchange Mailbox | Forwarding SMTP Address.


Significant performance improvements have been made to the Exchange Calculation data source collection. The Exchange Calculation job runs in the background and calculates recipient response times and message delivery times


New parameters are added to the UC.Analytics.Insights.DataEngine.DataCollector.dll.config file to allow you to modify the EWS Timeout property. By default, the Microsoft Exchange EWS API sets the default value to 100000 ms (100 seconds). New default values are set separately for Exchange and Exchange Online EWS data collections to reduce data source collection timeouts for Office 365:

The default value "ewsTimoutSeconds = 100" is added for on-premises EWS job settings:

The default value “ewsTimoutSeconds= 1800" is added for online EWS job settings:

The data sources affected by the new timeout default values are:


The Email - Activity insight is updated to include information to show the average number of message recipients for internal messages, inbound messages, and outbound messages. The new information appears in the Message Summary and Internal vs External Messages views by default.

You can add the information to the Messages by Internal Senders and Messages by Internal Recipients tables using the Customize option. Click the Customize icon on the top right of the table, click Show/hide calculation columns, and select the Average columns that you want to add.


A new option is added to the User Profile (Click YourName | Edit Profile) that allows you to exclude today’s data when you are displaying an insight and showing a relative date range such as 7 days or 28 days. The Exclude Today option is useful when the collection jobs for today have not completed which might result in incomplete data appearing in insights.


You can now add a column for Recipient Type Details Type (msExchRecipientTypeDetails) to identify mail-enabled users in insights such as Users - Inventory and Groups - Inventory. After you have added the column, you can filter for specific values in this field.

For a mail-enabled user, the values that appear for Recipient Type Details Type correspond to the values for the Exchange msExchRecipientTypeDetails attribute. For a non-mail-enabled user, the column will be empty.

For example, to add the column to the Users - Inventory insight, you would do the following steps:

Click Manage field columns and select Show advanced fields.
Search for Details and select Active Directory Object | Recipient Type Details Type.



Resolved issues

In large customer environments, possible data corruption could occur when:

Now, when the Query Engine is restarted, uncommitted segments are deleted only after a specific timeout period (24 hours by default).


Progress logging for the Exchange Calculation job (which calculates recipient response times and message delivery times) is improved to provide more detailed information that can be used in troubleshooting.


The Exchange Calculation job processes messages in order of oldest day to the most recent day. If there was a bad shard, the job encountered an error and would exit on the first day with a bad shard. Subsequent runs would also error out on that day. Consequently, no response times or delivery times were populated for any day after day with the bad shard. Now the Exchange Calculation job continues to the next shard after encountering a day with a bad shard.


Improved the performance of the Exchange Calculation data source job in processing message response times by implementing a better algorithm to query reply messages from the Query Engine.


The Exchange (Online) Mailbox Content Summary ongoing data collection could not collect from mailboxes where, in the previous collection, the message statistics gathering part of the data collection had failed.


When the PowerShell exception "An error caused a change in the current set of domain controllers" occurred in the following data collections, UC Analytics would wait for 300 seconds before retrying. Now it will create a new session and retry immediately (by default).

Now, if you want to customize the PowerShell wait time, you can edit the value for each data the UC.Analytics.Insights.DataEngine.DataCollector.dll.config file:











For details, see the Making Changes to your Deployment chapter in the UC Analytics Deployment Guide.


On the Exchange Mailbox Contents and Exchange Online Mailbox Contents data sources, the Data to Collect option labeled Localize send / receipt time is changed to Localized send / receipt time (to time zone of working hours) and working hours. Also, the errors that are logged for mailboxes that do not have working hours set in the calendar are aggregated to a single log to reduce volume of error messages.


The Sender filters did not work for send-as messages. For example, if individual user A sent a message from the shared mailbox Support, and you ran the Exchange Tracking Logs data collection, user A was showing up as the sender in the Email - Details insight. If you set a filter of Sender | Email Address | Messaging Address = Support, the message from user A still appeared.


New parameters are added to the UC.Analytics.Insights.DataEngine.InsightLogic.dll.config file that allow you to disable the inclusion of a header for insights that are exported to formatted (localized) or formatted (UTC) .csv or .tsv files. The new parameters are in the section titled <insightRenderingConfiguration> and are as follows:

For more information, see chapter 10 in the UC Analytics Deployment Guide.


Known issues

It is not recommended that you use the built-in domain Administrator account for installing or for accessing UC Analytics. If you have a child domain in your environment, or if you have two root level domains, you will be unable to install the product.


Typically, when you uninstall the product, the Storage directory is removed. If the specified directory cannot be removed (for example, if the directory is on a network drive) an error message appears. You can work around the error by clicking “Ignore”. You can manually remove the directory after the uninstallation process is complete.


After installing the Storage Engine on a separate computer with multiple network cards, the customer is unable to access the web site (“Application failed to start.”) and nothing seems to work. In this case, an incorrect IP address may have been registered for the Storage Engine.

NOTE: If you are installing multiple Storage Engines on a separate computers that have multiple network cards, the installation may not complete.


On servers that have more than one IPv4 address, the UC Analytics installer selects one of the IPv4 addresses and registers that as the IP address for the UC Analytics component on that computer. The selected IP address may not be the IP address you want for the UC Analytics Storage Engine.


Disable the network cards that have undesired IP addresses, run the UC Analytics installer for the Storage Engine, and re-enable the disabled network cards. If you need to disable a network card that is used for Remote Desktop access to the server, you must install UC Analytics using the physical console instead of Remote Desktop.


In the Autorun.exe, the Download buttons for the software prerequisites may appear to be not working. An error is displayed about a script error on the page.


On some computers, an iexplore.exe process lingers for about 30 seconds after Internet Explorer is closed. Until the iexplore.exe process exits, the Javascript call for the Download buttons fails to launch a new Internet Explorer window.


Launch the Task Manager and wait until the iexplore.exe process has exited. The Download buttons work correctly.


In a deployment with multiple Data Engine collector roles installed, if you modify your deployment configuration properties using the Deployment Manager, and you clear the Data Engine configuration and reset it, an issue can occur in which the Primary Data Collector cannot be identified. The following error is displayed “You must have one collector role for the Data Engine designated as the primary collector.”


In the Deployment Manager, select Manage Deployment | Modify Deployment.
Click Edit Deployment and click Data Engine Advanced.
Select the Primary Data Collector check box for the server that hosts collector that should be the primary collector.


If an Office 365 account is added as a product administrator in the Deployment Manager, the account is not granted full access to the Admin Settings.


In the UC Analytics web site, in Admin Settings | Security, add the Office 365 user account under the Access to Tenant Configuration heading to grant full access to Admin Settings. You must have already added an Office 365 target environment.


On the Admin Settings - Data Collection page, under Data Sources, you cannot remove data sources if you are viewing the page using iPad or other mobile platforms.


In the Classifications | Threshold Classification page, you can set thresholds for Skype for Business and Lync QoE quality metrics. The page has the recommended thresholds set for Skype for Business 2015 and Lync 2013 by default. Most of these thresholds also apply to Lync 2010.

However, if you add a threshold classification that is specific to Lync 2010 only, and you have a mixed environment, the threshold will also be applied to Lync 2013 and later even though the threshold may not be applicable to those versions.


When setting security access to insight data in the Admin Settings | Security page, if you add an Active Directory (AD) user in email address format when the user does not have an associated mailbox, the security access is not set. For example, if you granted unrestricted access to that user, the user would see the error "You do not have the required access rights to view the insight” when attempting to view an insight such as the Mailboxes - Inactive insight.


You can add the user and grant data access if you enter the user SAM account name.


In the Exchange Online (hybrid and native) data source collections, if the same PowerShell credentials are used for more than one data source, there can be overlapping Azure AD plug-in credential incompatibility. You might notice authentication errors with Azure AD PowerShell cmdlets such as the following:

Though UC Analytics recovers from these errors, it is recommended that each Exchange Online data source be configured with its own set of PowerShell credentials.


Previously, UC Analytics might collect incorrect data for mobile devices if a mailbox display name contained a / (forward slash) or a \ (backslash). For example, if there were two mailboxes, /AB and AB, and if mobile device #1 connected to mailbox /AB, and mobile device #2 connected to mailbox AB, UC Analytics would incorrectly match both mobile devices #1 and #2 to mailbox AB. This issue existed only for mailboxes that were migrated from on-premise Exchange to Exchange Online. Though this issue was corrected in version 8.4.2, incorrect mobile device data that was collected previously and stored in the database is not changed. All new collected data will be correct.


UC Analytics does not distinguish between discovery mailboxes and system mailboxes. Discovery mailboxes are collected and recorded as system mailboxes. In insights, there is no indication that a mailbox is a discovery mailbox. You cannot filter on discovery mailboxes.


There can be partial ActiveSync data on the day that a user first starts using a mobile device. For example, ActiveSync activity is shown but not associated with a user in the Exchange ActiveSync / Users / Email Activity / Summary insight. This situation occurred when a user started using an ActiveSync device for the first time after the Exchange Configuration collection had successfully run for that day. ActiveSync activity for subsequent days will be correctly associated with the user.


If you have configured the Exchange Configuration data source for a resource forest implementation, if you later add an LDAP connection for more account forests, the data collection does not automatically run to update the data. You must wait until the next day’s data collection run to see the new information from the account forest.


In a hybrid environment (Exchange Online and Exchange on-premise), Azure AD Connect (formerly Azure AD Sync) synchronizes on-premises users with Office 365 cloud services for single identities. If the synchronization process is stopped, UC Analytics can double-count users. When the Azure AD Connect synchronization resumes, all new data collections will show the correct user count.


In the Exchange DLP Matches - Details insight, the text in the Justification for Override (insertable) column will appear incomplete if the justification text that was entered by the user contained a semicolon (:) or a single instance of single (‘) or double (“) quotation marks.



The Exchange IIS Logs data collection cannot associate ActiveSync events to a user for some ActiveSync clients with users that have spaces in their Windows logon name (such as MYDOMAIN\N Wong). This issue affects ActiveSync events from the ActiveSync client in Windows Mail. It does not affect the ActiveSync clients in iOS or in Android.


When collecting Exchange data from an Exchange resource forest deployment, there are certain limitations when an active (master) user account has more than one Exchange mailbox, or has more than one archive mailbox, in more than one forest.

The master account of the linked mailboxes and of the linked archive mailboxes is correctly recorded. However, only one of the mailboxes that belong to the master account will be reported as its mailbox. Similarly, only one archive mailbox that belongs to the master account will be reported as its archive mailbox.


For any back-end ActiveSync events that have an Exchange server as the authenticated user, the Exchange IIS data collector cannot associate the event to a device and user. The ActiveSync events are gathered but are shown in the insights without a device or a user.


To collect data for personal archive mailboxes (using the Exchange Configuration, Exchange Online Hybrid Mailbox Configuration, or Exchange Online Native Configuration data sources), you select the following two options:

If you do not select both options for the same data source collection, the Storage Limit Status column is not populated in the Personal Archive Mailboxes - Inventory and Personal Archive Mailboxes - Summary insights.


In the Exchange Online data sources, during target expansion, batch size configuration is implemented to improve gathering performance. To ensure that the complete membership of dynamic distribution groups is collected, the batch size values set in the Data Engine collector configuration cannot be less than 1000, and must be greater than or equal to 1000.

The batch size settings for the Exchange Online data source configuration are located in the UC.Analytics.Insights.DataEngine.DataCollector.dll.config file, on the computer that hosts the Data Engine (Collector):

Do not change these values except under guidance from Quest Support. If you reduce these values to a number less than 1000, some members of the target dynamic distribution groups will not be included in the Exchange Online data collections.


When entering an organizational unit (OU) when configuring certain data sources, if the user enters an OU in the correct format but with an invalid value, the data collection jobs do not issue a warning or error but resolve 0 targets for the invalid OU. Data will be missing from the insights. Data sources in which you can specify an OU as a target are as follows:


When you export an insight that shows a date range for the displayed data at the top of the insight, the date range time zone does not appear in the exported file.


In Exchange 2010, if the Microsoft OWA light version is used, the Outlook on the Web (OWA) insights will display the browser as "Unknown” for Internet Explorer 11, Edge, FireFox, Chrome, and Opera. The issue does not exist in other versions of Exchange or if Safari is the browser.


If the time zone offset is negative (such as -5), and you apply smoothing to a graph, and the beginning of your date range is before the date when data collection initially started, the total for the smoothed graph is less than the total for the unsmoothed graph.


Ensure that the date range does not include the days before data was collected.


In the Mobile Device insights, the Device IMEI column shows <none> for iOS devices. UC Analytics uses the cmdlet Get-MobileDeviceStatistics (for Exchange 2013/2016/2019) and Get-ActiveSyncDeviceStatistics (for Exchange 2010) to get the device IMEI. Due to how the iOS device built-in mail app works, the information is not stored in the internal mobile device logs and is not available to PowerShell, and by extension, to UC Analytics.


In the insight view, If the date range is set to a single day, any trend graph will change to a vertical bar chart but if you export the same insight, the trend graph does not display a bar chart but displays a trend line with a single point.


On the home page, you cannot enlarge or shrink the insight tiles on iPad and other mobile platforms.


After installing Quest UC Analytics and attempting to open the Analytics web site (http://<server>/Analytics), the user sees the following error: “The application failed to initialize.”

This issue may be caused by a bug in IIS 7.0 in handling extensionless URLs. See the following link for details:

Install the Microsoft patch to fix this issue.


If the Date format that is set in your UC Analytics user profile is in a different order than the Date and time format that is set in regional settings on your local computer, and you export an insight to .csv or .tsv format, when you open the exported file in Excel, Excel will incorrectly convert the date.


Set the order for day/month/year for the user profile Date format to be the same as in the local Date and time format that is set in your computer’s regional settings.

For example, if the Data and time format on your computer is set to be mm/dd/yyyy, set the Date format in the user profile to also be mm/dd/yyyy.

For more information about setting the date format in UC Analytics, see the Unified Communications Analytics User Guide.


When you export an insight to either .pdf or to Word (.docx) format, there might be discrepancies in how information is displayed:


In the details browser, the Exchange server details are not shown in the Exchange ActiveSync / Servers / Server Sync Times insight.

This scenario can occur if you collect ActiveSync data for a time period from before you installed the product. The insight is populated with the historical ActiveSync data collected from the IIS logs (Exchange IIS Logs data source). However, the server detailed data is populated from the once-a-day “snapshots” collected from Active Directory (Exchange Configuration data source).

Since you had not run the Exchange Configuration data collection during that time period, there is no Exchange server detailed information in the database. This issue decreases over time as the server data is accumulated through daily Exchange Configuration data collections.


In the Mailboxes - Folders Inventory insight, if there is a mailbox owner with many folders that span more than one displayed insight page, when you click a heading (such as Size) to sort the fields, sorting does not work.


The total number or size of messages (Unique Messages, Total Volume) will not always equal the sum of sent and received messages. The reason is that the total includes messages that were “sent on behalf of” and messages that were “sent as”, while the total of sent messages does not include these types of message. For example, when user A sent a message on behalf of user B, the insight would show the total number of messages of user B is 1, while the number of sent messages is 0.

The following insights are affected:


When configuring UC Analytics for subscriptions (Admin Settings | Subscriptions) you have the option to require authentication to the SMTP server that is used for email subscriptions.

UC Analytics cannot send subscription emails through Exchange receive connectors that meet all the following conditions:


Subscriptions might not send long emails, such as insights with large tables, in MHTML or HTML format. Depending on message size limit set on the specified SMTP server for email subscriptions, a subscription in MHTML or HTML format with a long body might be blocked.


If a user does not receive an email subscription in MHTML or HTML format, switch the subscription format to either .pdf or .docx format in which the size of the message is much smaller.


For Insight Visibility and Security (data access settings), UC Analytics does not support a configuration in which specified users are in a separate forest from the forest in which UC Analytics is installed. For on-premise target environments that are configured for Authentication-enabled, all users that are entered for Insight Visibility and Security must be in the same target environment as UC Analytics.


Time Zone Offsets: When you create a subscription, the current time zone offset (such as UTC -04:00) is captured and is used for the future subscription schedule. This captured time zone offset does not change with Daylight Saving Time (DST). You must manually change the existing subscription schedule when DST begins and ends.

Using a time zone offset override

Each time you log in, your user profile’s time zone offset is updated to the time zone of the client computer. The offset is used for executing queries and affects the display of data, including scheduled insights.

If you want your data queries to always run using a particular time zone offset regardless of your current location or whether DST is active, you can set an override in your user profile page. To access your user profile, click your user name in the top right corner of the Analytics web site and select Edit Profile.

If you travel to a different time zone, or when the time changes due to daylight saving, the scheduled subscription emails still use the old time settings until you log in to UC Analytics in the new time zone or after the time switch.


The UC Analytics Storage Engine service cannot start due to a failure to read a file descriptor in one of the commit logs. The Storage Engine tries to restart and fails because of a commit log replay issue, resulting in an error in the Cassandra.log file such as the following:

By default the log file is located in the following path:

C:\Program Files\Quest\UC Analytics\Storage Engine\bin\Cassandra.log


Delete the corrupted commitlog file that is specified in the error message and restart the Storage Engine service.


All the files in the Storage Engine directories must be available for reading and writing at all times. If you have any automated processes running on the Storage Engine directories that lock files, you might encounter problems. The Storage Engine, when it encounters one of its files that cannot be written to or deleted, stops running. You must restart the service to get the Storage Engine working again.


The Data Engine does not communicate with the Query Engine when a proxy is enabled on the Data Engine server.


Disable the proxy or ensure that the proxy allows direct communication to the Query Engine server (which can be the same server as the Data Engine).


System requirements

If you are installing UC Analytics, the computer must meet the following minimum requirements:


Minimum: Quad core 64-bit computer.


Minimum: 24 GB.


X GB where X is the required disk space for collected data

For estimates regarding the required disk space for the collected data for different numbers of users for all the platforms, see the UC Analytics Deployment Sizing.xlsx spreadsheet which can be found under Documentation in the autorun.exe.

Operating system

One of the following:

Any server on which a UC Analytics service or service role is installed must have a static IP address defined.

For a distributed deployment, the Remote Registry Service must be running.

Generally, using a NAS/SAN device for the Storage Engine is not supported. UC Analytics might support specific NAS/SAN devices but Quest would require full testing with the devices, or device simulators, to support them. Since each NAS/SAN device, depending on manufacturer, is unique, Quest will work with NAS/SAN vendors to certify or qualify a device but the NAS/SAN vendor must be willing to assist. To engage a NAS/SAN vendor and initiate the qualification process, you would send an email to your NAS/SAN vendor and contact Quest Support.

To install and run UC Analytics, the following software requirements must be met on the computers that host these specific UC Analytic services:

Web site

IIS (Internet Information Services) 7.0 or later

For the required configuration for IIS logging, see Appendix C in the Quest UC Analytics Deployment Guide.

Data Engine service

Also, since the Microsoft Azure AD cmdlets use the proxy settings for Internet Explorer, ensure that the Internet Explorer proxy settings for the service account are set correctly.

Query Engine service

64-bit Java Runtime Environment (JRE) 8

- OR -

Zulu OpenJDK 8 (Zulu Java 8 JRE for Windows, x86 64-bit in .MSI form)

For information and downloads, see

Storage Engine service

64-bit Java Runtime Environment (JRE) 8

- OR -

Zulu OpenJDK 8 (Zulu Java 8 JRE for Windows, x86 64-bit in .MSI form)

For information and downloads, see

For information about the rights and permissions needed to configure UC Analytics and by the credentials used to gather information, see the Quest UC Analytics Deployment Guide.

Gathering environment

The following is a list of the minimum environments that are supported for data collection:

Supported browsers

To access the UC Analytics web site, use one of the following browsers:

For users with large amounts of data, it is recommended that you ensure your browser is in 64-bit mode.

For more information about setting Internet Explorer to 64-bit mode, see the section titled “Using a browser in 64-bit mode” in the UC Analytics User Guide.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating