This document provides troubleshooting guidelines for common problems related to ZENworks System Update. If, after completing the troubleshooting steps, the problem is not resolved, you should contact Technical Support for additional help.
Symptoms: Bundles don’t show up, policies aren’t applying, Remote Management won’t start, the ZENworks icon isn’t displaying, or the user can’t log in to ZENworks.
If the workstation updated completed but there were errors, reapply the system update to the workstation.
Is the system update assigned to the workstation? To check in ZENworks Control Center, go to the workstation’s Summary page. Is the update listed in the Assigned System Updates panel.
If the update is not assigned, click Configuration > System Updates. In the Available System Updates panel, select the check box next to the update, then click Action > Deploy Update to Devices.
If the update is assigned to the workstation, check its schedule.
Has the device refreshed after the system update was assigned to it. To refresh the device, right-click the ZENworks icon > click Refresh.
Check to see if the workstation can connect to the Primary Server or Satellite Server from which it receives content:
In ZENworks Control Center, go to the workstation’s Summary page. Check the last contact and last full refresh times to see if the device has been able to check in and perform a full refresh recently. If not, continue with the next step.
At a command prompt on the device, run zac zc -l to see which server is functioning as the workstation’s content server.
Can the workstation contact its content server? Ping the DNS name and IP address of the content server to verify.
At a command prompt on the workstation, run zac retr to reestablish trust with the Management Zone.
Verify that the Primary Server or Satellite Server has the System Update content:
Windows: \zenworks\work\content-repo\systemupdate\<UpdateGUID>
Linux: /var/opt/novell/zenworks/content-repo/systemupdate/<UpdateGUID>
To see the <UpdateGUID>, click the update (on the System Update page).
If the workstation is a Satellite Server, run zac retr at the command prompt to reestablish trust with the Management Zone.
If the workstation is an 11.3 or newer version of ZENworks, use the standalone updater on it. For information, see Standalone Agent Updater in the ZENworks System Updates Reference.
If the workstation version is 11.2.x and the workstation rebooted before the update completed, run this command on device to relaunch update:
%zenworks_home%/bin/zenupdater -v -c zenupdater.exe -v -c "c:\Program Files\novell\zenworks\logs\system-update\<UpdateGUID>\update_commands.xml"
This command works only if a previous application of the system update was interrupted by a reboot.
If the issue is still not resolved, contact Support.
Check all the items in Unable to apply a system update to a workstation.
Did you get an error about rebuilding deployment packages? This only happens after the server is successfully updated. It affects the server’s ability to deploy updates to workstations. To fix the problem:
At the server’s command prompt, run zman surp <UpdateGUID> to relaunch the package rebuild. To see the <UpdateGUID>, launch ZENworks Control Center, click Configuration > System Update, then click the update.
After about 20 minutes, verify that the packages are being rebuilt by looking in the servers’s %zenworks_home%/install/downloads/setup/_all directory. If some or all of the dates are current, then the packages are being updated. If the dates are not current, contact Support.
If the system update isn’t showing up in ZENworks Control Center after using the zman sui <update.zip> command:
Check the server’s free disk space. It needs free disk space equal to 3x the size of the <update.zip> file.
On Linux servers, try placing the <update.zip> file in the /tmp directory or the /var/opt/novell directory.
Set the permissions for the <update.zip> file, then run the zman sui <update.zip> command.
On a Windows server, launch the command prompt as Administrator (Start menu > right-click Command Prompt > Run As).
On a Linux server, run /opt/novell/zenworks/bin/permissions.sh and /opt/novell/zenworks/bin/core-permissions.sh. This sets the ownership of the ZENworks directories to ZENworks if necessary.
If you are using an MSSQL server for the ZENworks database, make sure there are no database size issues:
Check that the database isn’t full.
Check the transaction.log size. Shrink the file if it is large. DO NOT delete the file.
If the ZENworks server has an old system update content reference, then the update fails while preparing the system update.
Workaround: Contact Micro Focus Customer Center.
For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government rights, patent policy, and FIPS compliance, see https://www.microfocus.com/en-us/legal.
© Copyright 2008 - 2024 Open Text.
The only warranties for products and services of Micro Focus and its affiliates and licensors (“Open Text”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.