Unified Communications Diagnostics 8.6.3

Table of Contents

Quest® Unified Communications Diagnostics 8.6.3 About Unified Communications Diagnostics 8.6.3 New features Resolved issues Known issues

If you are upgrading from a previous version System requirements

Product licensing Getting started with UC Diagnostics 8.6.3 Globalization About us

Known issues

The following is a list of issues, including those attributed to third-party products, known to exist at the time of release.

Table 2. General known issues
Known issue	Issue ID
Security Patch 2023 update for 2016 Server edition conflicts with the normal functioning of the application. Workaround User are advised to not install the 2023 security patch updates and stay with 2019 patch updates.	419043
MSOL commands are going to be deprecated and will be replaced with MSGraph commands. However, MSGraph currently does not have all properties similar to that of MSOL. A ticket has been raised with Microsoft Support team to enable MSGraph commands to have these properties.	416940
Do not install UC Diagnostics on the same machine as Spotlight on Active Directory or as MessageStats.	NA

Table 3. Management console known issues

Known issue

Issue ID

When running the Exchange External Message Delivery Health Test against Exchange 2013 in which the CAS server is behind a load balancer, the test did not complete and it failed with the error “Failed to open the default message store”.

Workaround

Remove the Exchange External Message Delivery Health Test and run the Exchange Modern Message Delivery Health Test instead.

452686

If you are upgrading from 8.2, some health tests will not run immediately for Exchange 2016. You must edit each test once and click Finish to cause the previous test to run and retrieve some of the counter values correctly. The tests that must be edited after upgrade are as follows:

•

Exchange Replication Health Test

•

Exchange Server Health Test

•

Exchange Storage Health Test

•

Exchange Queue Health Test

•

Exchange System Health Test

593819

For a Skype for Business/Lync environment, if a DNS Alias record is configured for a front-end pool or standard edition server rather than a Host A record, UC Diagnostics will fail to discover and run the synthetic transaction health tests with that pool or server. This issue is only found on 32-bit and 64-bit systems of Windows 2008. Newer operating systems do not have this issue.

325647

In Skype for Business or Lync Discovery, the display name of PstnGateway only shows the numbers/characters before the first dot. There is a problem when PstnGateway name is an IP address.

354306

Upgrading from version 8.2 or later

As of UC Diagnostics 8.3, Exchange 2000 and Exchange 2003 are not supported. If you are upgrading from UC Diagnostics 8.2, use the Force Discovery Now option to repopulate your topology view. If you are upgrading from 8.3, use this option to ensure Exchange version service pack and CU (cumulative update) information is shown for Exchange servers.

Solution

After you have upgraded to UC Diagnostics, reconnect to your messaging environment by clicking the menu option “Connect to xxx Environment/Organization”.

Click Force Discovery Now from the menu.

All objects in the treeview and topology and the health tests are now displayed. The service pack and CU information is also displayed for Exchange servers

599577

662418

If the BlackBerry Server Health Test runs on a standby BlackBerry server in a high availability configuration, the test results show errors for BlackBerry services that are not running. However, these services are not required to run in the standby server and no error exists.

Workaround: Perform the BlackBerry server health test on the primary BlackBerry server only, or run a separate BlackBerry server health test on the standby BlackBerry server with the affected service counters set to 'informational'.

161453

If you are installing Exchange 2013 and have upgraded to the newest version of MAPI & CDO (version 8.3.0.8353.000) to support RPC over HTTP) in a mixed environment, some health tests may not run properly. ESM and MAPI & CDO might not work together.

Workaround: Uninstall ESM. Reinstall the new MAPI & CDO for Exchange:
(https://www.microsoft.com/en-us/download/details.aspx?id=42040).

274631

Table 4. Diagnostic console known issues

Known issue

Issue ID

UC Diagnostics 8.4.1 was rebranded to the Quest company name and the installation path is now Quest. After you upgrade from 8.2, 8.3 or 8.4 to the current version, the Save As Template and Save As (Drilldown/AlarmLog) dialogs might still point to the previous installation path since Windows saved the path in the registry.

Workaround

You must manually redirect and save to the new default Quest path such as "%current_user%\AppData\Roaming\Quest\Shared\Templates".

687018

On a Windows Server 2016, when you launch the Diagnostics Console for the first time, you can see the following error: “There is no default printer currently selected.”

Workaround

Open the Devices and Printer page by selecting either:

•

Control Panel | All Control Panel Items | Devices and Printers

-OR-

•

Control Panel | Hardware | Devices and Printers

All subsequent launches of the Diagnostic Console will be successful.

652667

If there is no Reverse Lookup Pointer (PTR) created for the target Lync 2013 Server in a different domain and users connect the server with its NetBIOS name, the Lync 2013 plug-in of the diagnostic console is unable to get values for some components.

Solution

Add a Reverse Lookup Pointer (PTR) for the Lync 2013 Serve in the “Reverse Lookup Zones” of DNS.

369446

In Data Recorder Mode, if you connect to a Lync 2013 or Skype for Business 2015 Server with the NetBIOS name (such as wm-skp-st), the home page does not display properly. Some components are greyed out in the Diagnostics Console Play Back Mode.

Workaround

Use the server FQDN instead of the NetBIOS name when you connect in Data Recorder Mode.

453310

Table 5. Web reports known issues

Known issue

Issue ID

On Windows Server 2016, when you opened Web Reports, the web site would fail if Internet Explorer was not set as the default browser.

Workaround

Set Internet Explorer as the default browser on the computer that is running Windows Server 2016.

652943

Even though the SMTP Server and SMTP From Address were not configured for a subscription, when the user ran the subscription, the result showed Success.

Always ensure that you have configured the SMTP server and SMTP From Address before you run a report subscription.

652729

On Windows Server 2016, if the account that is running Web Reports is not a domain administrator, the following issues can occur:

•

User is unable to open Subscriptions | Configure Subscriptions.

•

After a user created a Web Reports custom report/graft/folder/subscription in the Microsoft Management Console (MMC), when the same user account accessed the Web Reports web site using Internet Explorer, the user cannot see the items that were created using MMC.

•

Sometimes Web Reports cannot be opened in Internet Explorer and the following error is displayed: "Unable to create copy template files to [My Reports] folders."

•

Subscription emails cannot be sent correctly.

•

On the Subscriptions page, the checkbox "Show Subscriptions for all users" is not shown in Internet Explorer but can be viewed in MMC.

Workaround

Disable UAC by changing the registry key "EnableLUA" to value "0"

Restart the operating system.

Web Reports will work without error.

651422

652856

On Windows Server 2016, when you are creating a custom report in Web Reports, the Preview option does not work correctly for data for a large number groups.

Workaround

•

Do not preview the custom report in the wizard. Click Finish. Then click Preview on the toolbar.

-OR-

•

Select Organization, Server Name or Date field to group the data in the report instead of the counter name or counter value.

651425

Web Reports fail to open from the Management Console (MMC snap-in) if Web Reports is using another web site rather than the default web site with 80 port.

Solution

•

Click the Web Reports menu in MMC. Click the Select Web Reports Server option and enter the correct server name: http://<WebReportServerName>[:portnumber]

The Web Reports can now be launched successfully.

386971

When UAC is enabled, Web Report pops up an error to say that it has no enough permission to read Web Report related folders, such as, C:\Inetpub\wwwroot\UCDiagnostics\Reports.

Solution

Disable UAC by changing the registry key "EnableLUA" to value "0"

Restart the operating system.

The Web Report will work without error.

385509

If you are upgrading from a previous version

You can perform a direct upgrade from 8.2 and later. If you are upgrading from 8.1 or earlier, you must first upgrade to 8.4 and then upgrade from 8.4 to 8.6.3.

If you are upgrading from a previous version, IIS services will stop while upgrading the Web Reports components. IIS services will automatically restart once upgrading is complete.

If you are upgrading from version 8.2 or later, you must use the Force Rediscovery option to repopulate the topology view or show service pack information for Exchange. For more information, see Upgrading from version 8.2 or later.

CAUTION: For existing UCD (Unified Communications Diagnostics) users having Windows Exchange Server 2016, it is MANDATORY to perform the steps in following order:

Upgrade to the latest version of UCD.

Turn off the TLS 1.0 and TLS 1.1 through the Registry Editor.

Finally, turn on the TLS 1.2.

Failure to do so may result in permanent loss of existing profile data or configuration settings of UCD.


	IMPORTANT: For new users of Unified Communications Diagnostics using Windows Server 2016, it is recommended to turn off TLS 1.0 and TLS 1.1, and then turn on TLS 1.2 from Registry Editor to avoid any future deprecation related complications.

Upgrading a manually installed database

If you manually installed the database, you must manually upgrade the database. For more information, see the Unified Communications Diagnostics Deployment Guide.

System requirements

Before installing UC Diagnostics 8.6.3, ensure that your system meets the following minimum hardware and software requirements.

Hardware requirements

Table 6. Hardware requirements
Requirement	Details
Processor	Processor x86 or x64, running at a minimum speed of 2 GHz
Memory	8 GB
Hard disk space	300 MB on system drive for application. Historical reporting database requires additional space. For more information, see the Unified Communications Diagnostics Deployment Guide.

Software requirements

Local Windows Administrator privileges are required on the computer where the product is installed. For more detailed permissions for operating UC Diagnostics, see the Unified Communications Diagnostics Deployment Guide.

Table 7. Management console requirements

Component

Requirement

Operating system

One of the following:

•

Microsoft Windows 8 (32 bit or 64 bit)

•

Microsoft Windows 8.1 (32 bit or 64 bit)

•

Microsoft Windows Server 2012 (64 bit)

•

Microsoft Windows Server 2012 R2 (64 bit)

•

Microsoft Windows 8.1 with update (32 bit or 64 bit)

•

Microsoft Windows Server 2012 R2 with update (64 bit)

•

Microsoft Windows Server 2016 (64 bit)

•

Microsoft Windows Server 2019 (64 bit)

•

Microsoft Windows Server 2022 (64 bit)

NOTE: To run health tests against Office 365, UC Diagnostics must be installed on a 64-bit operating system.

Database

One of the following:

•

Microsoft SQL Server 2012 SP 4

•

Microsoft SQL Server 2012 Express Edition SP 4

•

Microsoft SQL Server 2014 SP 2

•

Microsoft SQL Server 2014 Express Edition SP 2

•

Microsoft SQL Server 2016 SP 1

•

Microsoft SQL Server 2016 Express Edition SP 1

•

Microsoft SQL Server 2017

•

Microsoft SQL Server 2017 Express Edition

•

Microsoft SQL Server 2022

NOTE: If you are installing the database on a remote computer, ensure remote connections are enabled on the SQL server and you have sufficient permissions to create/modify the database.

NOTE: If you are using SQL Server Always On, you must have configured an availability group listener that connects to the primary replica. For SQL Server 2017, only availability groups that deploy on a Windows Server Failover Cluster (WSFC) are supported.

Diagnostic Services (Health Tests) for all environments

The following software is required for diagnostic services (health tests) to run on any environment:

•

Microsoft .NET Framework 4.5.1 or later

•

Microsoft Data Access Components (MDAC) 2.8

NOTE: MDAC 2.8 comes with your operating system. If MDAC is uninstalled, UC Diagnostics will not run.

Diagnostic Services (Health Tests) for Exchange 2007

•

Exchange Management Console (EMC) 2007 SP 1 and Update Rollup 1 or later

If your organization is mixed and contains Exchange 2007 servers, you must install EMC 2007 SP 2 or later.

The Exchange Management Tools version installed on your UC Diagnostics computer must match the Exchange version installed on your Exchange server. For example, if you have Exchange 2007 SP 2 installed on your Exchange server, Exchange Management Console 2007 SP 2 must be installed on your UC Diagnostics computer.

•

Exchange Server MAPI Client and Collaborative Data Objects (MAPI & CDO) 1.2.1 (Build 8.3.0.8353.000 or later)

Microsoft Outlook should not be installed on the same computer on which MAPI & CDO is installed.

Diagnostic Services (Health Tests) for Exchange 2010

•

Microsoft PowerShell 2.0 or later

•

MAPI Client and Collaborative Data Objects (MAPI & CDO) 1.2.1 (version 8.3.0.8353.000.or later).

Diagnostic Services (Health Tests) for Exchange 2013

•

Microsoft PowerShell 2.0 or later

•

MAPI Client and Collaborative Data Objects (MAPI & CDO) 1.2.1 (version 8.3.0.8353.000. or later)

Diagnostic Services (Health Tests) for Exchange 2016

•

Microsoft PowerShell 2.0 or later

Diagnostic Services (Health Tests) for BlackBerry

•

MAPI Client and Collaborative Data Objects (MAPI & CDO) 1.2.1 (version8.3.0.8353.000 or later)

Diagnostic Services (Health Tests) for Lync

•

Microsoft PowerShell 2.0 or later

Diagnostic Services (Health Tests) for Skype for Business

•

Microsoft PowerShell 2.0 or later

Diagnostic Services (Health Tests) for Office 365 (Exchange Online and Skype for Business Online)

•

Windows PowerShell 5.0 or later

•

Microsoft Online Service Sign-in Assistant

•

Windows Azure Active Directory for Windows PowerShell

•

Microsoft Exchange Online PowerShell Module

You can download Microsoft MAPI & CDO from the Microsoft web site here: https://www.microsoft.com/en-us/download/details.aspx?id=42040.

To install the Microsoft Exchange Online PowerShell module, you can use the following procedure:

To install the Exchange Online PowerShell module

Perform the following steps in a browser that supports ClickOnce such as Microsoft Internet Explorer or Edge.

Open the Exchange admin center (EAC) for your Exchange Online organization.

In the EAC, go to Hybrid | Setup and click the appropriate Configure button to download the Exchange Online PowerShell module for multi-factor authentication.

In the Application Install window, click Install.

Table 8. Diagnostic console requirements

Component

Requirement

Diagnostic Console for all Environments

•

Microsoft .NET Framework 4.5.1 or later

Diagnostic Console for Exchange 2007

•

EMC 2007 SP 1 or later

Diagnostic Console for Exchange 2010

•