ZENworks 2020 Update 3 Readme

1.1 Why ZENworks 2020 Update 3a

A few ZENworks customers have reported following issues while updating to ZENworks 2020 Update 3:

To address all the above-mentioned issues, ZENworks 2020 Update 3a is released.

1.2 What To Do Next

Depending on your current deployment stage, refer to the following scenarios:

8.1 ZENworks Diagnostics Center Report displays Inconsistencies for Patch Management

While running ZENworks Diagnostics on the database, the following inconsistencies will be displayed in the ZDC report:

ERROR Missing object in table 'patchsignature' 
Object type: [Index] , Object name: [uniq_patchsignature_type] 
Detail: [Name: uniq_patchsignature_type, Table: patchsignature, ColumnMap: {type=1}, isConstraint: false] 

IndexERROR Missing object in table 'patchsignature' 
Object type: [Constraint] , Object name: [uniq_patchsignature_type] 
Detail: [Name: uniq_patchsignature_type, Type: UNIQUE, Table: patchsignature, ColumnOrder {Position: 1 [ColumnName: type, DeleteCascade: false]}] 

ConstraintERROR Missing object in table 'patchsuperseded' 
Object type: [Index] , Object name: [uniq_patchsuperseded] 
Detail: [Name: uniq_patchsuperseded, Table: patchsuperseded, ColumnMap: {newpatchid=1, oldpatchid=2}, isConstraint: false] 

IndexERROR Missing object in table 'patchsuperseded' 
Object type: [Constraint] , Object name: [fk_patchsuperseded_newpatchid] 
Detail: [Name: fk_patchsuperseded_newpatchid, Type: FOREIGN KEY, Table: patchsuperseded, ColumnOrder {Position: 1 [ColumnName: newpatchid, DeleteCascade: true]}] 

ConstraintERROR Missing object in table 'patchsuperseded' 
Object type: [Constraint] , Object name: [fk_patchsuperseded_oldpatchid] 
Detail: [Name: fk_patchsuperseded_oldpatchid, Type: FOREIGN KEY, Table: patchsuperseded, ColumnOrder {Position: 1 [ColumnName: oldpatchid, DeleteCascade: true]}]

ConstraintERROR Missing object in table 'patchsuperseded' 
Object type: [Constraint] , Object name: [uniq_patchsuperseded] 
Detail: [Name: uniq_patchsuperseded, Type: UNIQUE, Table: patchsuperseded, ColumnOrder {Position: 1 [ColumnName: newpatchid, DeleteCascade: false]} {Position: 2 [ColumnName: oldpatchid, DeleteCascade: false]}]

ConstraintERROR Missing object in table 'patchdevicestatus' 
Object type: [Index] , Object name: [uniq_patchdevicestatus] 
Detail: [Name: uniq_patchdevicestatus, Table: patchdevicestatus, ColumnMap: {deviceid=1, signature_id=2}, isConstraint: false]

IndexERROR Missing object in table 'patchdevicestatus' 
Object type: [Constraint] , Object name: [uniq_patchdevicestatus] 
Detail: [Name: uniq_patchdevicestatus, Type: UNIQUE, Table: patchdevicestatus, ColumnOrder {Position: 1 [ColumnName: deviceid, DeleteCascade: false]} {Position: 2 [ColumnName: signature_id, DeleteCascade: false]}]

8.2 Unable to Upgrade to ZENworks 2020 Update 3 as the Server Certificate is missing Subject Alternative Name

If the server certificate has CN as an IP address and the Subject Alternative Names (SAN) do not include an IP address, the upgrade might fail during the prepare stage. Ensure that the value of SAN includes the IP address also.

The following exception is logged in the loader-messages.log file:

java.security.cert.CertificateException: No subject alternative names present
   at sun.security.util.HostnameChecker.matchIP(HostnameChecker.java:160)
   at sun.security.util.HostnameChecker.match(HostnameChecker.java:104)
   at sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:457)
   at sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:431)
   at sun.security.ssl.AbstractTrustManagerWrapper.checkAdditionalTrust(SSLContextImpl.java:1290)
   at sun.security.ssl.AbstractTrustManagerWrapper.checkServerTrusted(SSLContextImpl.java:1257)
   at sun.security.ssl.CertificateMessage$T12CertificateConsumer.checkServerCerts(CertificateMessage.java:638)

8.3 A registered Mac Intel device displays ARM details

In ZENworks 2020 Update 3, after migrating to the new patch feed, a registered Mac device with an Intel processor displays ARM patch information, after performing the patch maintenance.

Workaround: None

8.4 While updating ZENworks, HTTP 500 internal error might be displayed

As part of System Update deployment, during the Configure Update phase, the HTTP 500 internal error might be displayed while configuring a new port for ZENworks Control Center.

Workaround:

8.5 System Update might fail on Linux Primary Server during the Prepare stage

While deploying System Update on Linux Primary Server, the update fails during the Prepare stage, and the following error message is logged in loader-messages.log:

/opt/microfocus/zenworks/bin/run_preglobal_update:: OUT: FINE: Failed to Copy File Due to Exception : java.io.IOException: Destination '/var/opt/novell/zenworks/ZeUS/work/prepare/<system_update_guid>/webapps' directory cannot be created

Workaround: Run permission.sh and retry prepare on the server.

8.6 While updating ZENworks, the request method POST not supported error might be displayed

As part of System Update deployment, during the Configure Update phase, the following error might be displayed while configuring a new port for ZENworks Control Center:

HTTP ERROR 405 Request method POST not supported

Workaround: Ignore the error and continue with the update process.

8.7 Patch settings are hidden even after activating the Patch Management license

Some of the patch-related settings are hidden even after successfully activating the Patch Management license.

This might happen only when the administrator deactivates Patch Management and then reactivates Patch Management in the evaluation mode or by providing a key.

Workaround: After activating the license, log out and re-login to ZCC.

8.8 Patches are not populated on agents after migration to the new Patch Management system

After updating to ZENworks 2020 Update 3, and migrating to the new Patch Management system, patches are not populated on the devices, and the following exception is logged in the patch-management.log file on the server:

plr files fails to process with "patchsuperseded" violates foreign key constraint "fk_patchsuperseded_oldpatchid" exception

The device GUID on which the issue is observed can be found right after the above exception message.One of the reasons might be because the Patch Management is reset.

Workaround: On the agent, delete the scanstatus.json file available in the following location, and then run zac ps.

8.9 Content Download fails with Yum-repo using a non-SSL URL

After updating to ZENworks 2020 Update 3, when you create the Yum service for a Linux bundle, the content download fails, as a non-SSL URL is being used.

Workaround: Ensure that you use URLs with “https” instead of “http”.

8.10 Blackedout Schedule Is Not Supported for Ondemand Cached Content

In ZENworks 2020 Update 3, the Blackedout schedule for the Ondemand cached content is not supported. Content that is already cached as part of Ondemand request and when it is served to managed devices from its local cache again, in this scenario, the blackedout schedule is not supported.

Workaround: None

8.11 An exception was displayed when backing up ZENworks Primary Server

When trying to backup the ZENworks Primary Server on Windows by running the zen-backup-restore.bat mode=backup file="C:\Program Files (x86)\Micro Focus\ZENworks\backup" command, an IOException message was found in the log file.

Workaround: None. Ignore the issue.