Management console and platform services known issues

After a device is partially locked down and turned off, the device appears to be offline in the console (even though it is turned on again and back online) until an administrator unlocks the device from the console. (UES-19182)

When adding an exception based on an alert from the Alerts view, the AI recommends the incorrect facet for Target Powershell Trace conditions. (EDRCLO-1075)

Workaround

: Use the “String Block Text” facet instead.

When a device is partially locked down, and you manually unlock the device with an unlock code successfully, the device appears to be still locked in the console. (EDRCLO-1072)

After a device is partially locked down, the Alerts screen updates its online status approximately ten minutes after it comes back online instead of within seconds. (EDRCLO-1047)

When a device is fully locked down, and you manually unlock the device with an unlock code successfully, the device appears to be still locked in the console. (EDRCLO-1019)

In Settings > Tenant Settings, when you reset the tenant configuration to default settings and immediately import configuration settings, the import fails and an error message indicates that the configuration settings could not be imported.

Workaround

: After resetting the tenant configuration to default, wait a few minutes before importing configuration settings. (VENECS-2224)

If a device policy has not been changed since August 2021:

If you turn on Script Control and set PowerShell Console to Alert, you cannot save changes to the device policy.
If you turn off Script Control and PowerShell Console is set to Alert, you cannot not save any changes to the Script Control settings.

Workaround:

If Script Control is turned on, disable PowerShell Console and save the policy.
If Script Control is disabled with PowerShell Console set to Alert, make a change to the device policy outside of the Script Control settings and save the policy. You can then save any changes to the device policy.

(EPCL-2714)

When performing a search in the device name field for a device that has a double quotes (“) in its name, the device may not be found if the quotes that are in its name are included in the query. (UES-14982)

The management console unprotected devices screen (Assets > Unprotected devices) occasionally may display incorrect device OS and OS versions. For example,

On
Mac
devices, supported OS and OS versions may display as unknown and unsupported, respectively. (UES-9904)
On
Windows
devices, unsupported OS versions (for example,
Windows Server
2008 and
Windows
8) may display as supported. (UES-9903)

For information about the operating systems that each of

BlackBerry Protect Desktop

agents supports, see the Cylance Endpoint Security compatibility matrix.

The management console unprotected devices screen (Assets > Unprotected devices) incorrectly displays devices running

Windows 10

Enterprise Insider Preview as

Linux

. (UES-9897)

In

Google Chrome

version 105.0.5195.102 and later, the "Block third-party cookies" option is enabled by default for incognito mode. If you try to log in to the management console while this option is enabled, you may receive a "Sign-in failed" error. (UES-9770)

Workaround

: Change your

Chrome

privacy and security settings to allow all cookies, or in the browser settings add [*.]cylance.com as a site that can always use cookies.

The management console unprotected devices screen (Assets > Unprotected devices) does not display the device OS and OS version and results in 'insufficient information' to be displayed for the devices. (UES-9574)

Workaround

: Configure the schema to allow the required attributes to synchronize from the domain controller to the Global Catalog. For instructions, see Configure your environment to view the device OS and OS version of managed unprotected devices in the administration content.

The

BlackBerry Connectivity Node

is not compatible with OpenJDK292b10 or ZuluJDK292b10. (UES-3667)

A Java bug for this issue has been logged at https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8266279.