All the Primary Servers should be updated before you update the agents and the Satellite Servers in the zone. To ensure the proper functioning of ZENworks, it is recommended that all Primary Servers are updated in as short a time as possible - ideally, immediately after the first Primary Server is updated.
The administrator can always choose to update one of the Primary Servers and then the remaining Primary Servers. The Primary Server that is chosen to be updated first should be the server with the embedded database.
NOTE:
The ZENworks Updater Service should be running to initiate an update on Primary Servers and Windows Agents.
The ZENworks Agent Service should be running to initiate an update on Linux Agents.
If the zone contains an embedded database, the server that is running in the database should be updated first.
Before updating the ZENworks Agent on managed devices, ensure that any reboots required from applying a policy are completed.
If the zone contains one or more SLES 12 or SLES 15 non-appliance primary servers, for the ZENworks 2020 Update 3 system update, ensure that the ‘libseccomp2’ package is at 2.4.1-11.3.2 or later version.
Windows 10 Prerequisite:
When updating the ZENworks Agent to ZENworks 2017 Update 1 on a Windows 10 device, you need to disable Client Self Defense and reboot the device before running the update. Self Defense can be re-enabled after the update. This prerequisite is not applicable when updating the ZENworks Agent from ZENworks 2017 Update 1 to a later version. For information about the Self Defense setting, see Configuring the Agent Security
in the ZENworks Discovery, Deployment, and Retirement Reference.
Full Disk Encryption Agent prerequisites: For information about Full Disk Encryption update prerequisites and other considerations for doing a system update on managed devices using Full Disk Encryption, see the ZENworks 2020 Update 3- Full Disk Encryption Update Reference.
IMPORTANT:If you have enabled the ZENworks Patch Management in your zone, then ensure that you perform the following steps before updating to ZENworks 2020 Update 3:
Run the following query to identify the Patch policies that have DaysToRebuild set to 0:
SELECT * FROM zbundle WHERE zuid IN ( SELECT zuid FROM zzenobject WHERE path LIKE '%ZPM/Policy%' AND primarytype = 'Bundle' AND subtype LIKE '%Patch Bundle%' AND serversidedata LIKE '%xmlns:ns2="http://novell.com/zenworks/datamodel/objects/settings">DaysToRebuild</ns2:Name><ns2:Value xmlns="http://novell.com/zenworks/datamodel/objects/settings" xmlns:ns2="http://novell.com/zenworks/datamodel/objects/settings">0</ns2:Value></Variables><Variables><ns2:Name xmlns="http://novell.com/zenworks/datamodel/objects/settings"%' )
Run the following update query to set the DaysToRebuild from 0 to the desired value:
UPDATE zbundle SET serversidedata = replace(serversidedata, 'xmlns:ns2="http://novell.com/zenworks/datamodel/objects/settings">DaysToRebuild</ns2:Name><ns2:Value xmlns="http://novell.com/zenworks/datamodel/objects/settings" xmlns:ns2="http://novell.com/zenworks/datamodel/objects/settings">0</ns2:Value></Variables><Variables><ns2:Name xmlns="http://novell.com/zenworks/datamodel/objects/settings"', 'xmlns:ns2="http://novell.com/zenworks/datamodel/objects/settings">DaysToRebuild</ns2:Name><ns2:Value xmlns="http://novell.com/zenworks/datamodel/objects/settings" xmlns:ns2="http://novell.com/zenworks/datamodel/objects/settings">120</ns2:Value></Variables><Variables><ns2:Name xmlns="http://novell.com/zenworks/datamodel/objects/settings"')
WHERE zuid IN (
SELECT zuid
FROM zzenobject
WHERE path LIKE '%ZPM/Policy%'
AND primarytype = 'Bundle'
AND subtype LIKE '%Patch Bundle%'
AND serversidedata LIKE '%xmlns:ns2="http://novell.com/zenworks/datamodel/objects/settings">DaysToRebuild</ns2:Name><ns2:Value xmlns="http://novell.com/zenworks/datamodel/objects/settings" xmlns:ns2="http://novell.com/zenworks/datamodel/objects/settings">0</ns2:Value></Variables><Variables><ns2:Name xmlns="http://novell.com/zenworks/datamodel/objects/settings"%'
)
NOTE:In the above query, as an example 120 is used. However, the number can be increased if you do not want the Patch Policy to be rebuilt soon. The number 120 represents the days to rebuild the patch policy.
For additional information, see Troubleshooting System Updates.