" />" />" />" />" />" />" />" />" />" />" />" />" />" />" />" />" />" />" />" />" />" />" />" />" />" />" />" />" />" />" />" />" />" />
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’spage. Is the update listed in the Assigned System Updates panel.
If the update is not assigned, click> . In the panel, select the check box next to the update, then click > .
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.
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’spage. 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:
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 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>, launch ZENworks Control Center, click > , then click the update.> to relaunch the package rebuild. To see the <
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 (menu > right-click > ).
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.
Support Pack releases use an ISO to upgrade the ZENworks system.
Do a checksum on the ISO file and compare it to the checksum provided on the download page.
Make sure you are mounting the ISO or have burned it to a DVD. You cannot extract the ISO.
Make sure that the operating system to which you are installing the Support Pack is supported by the release. For details, see the Processor:.
Does the system you are upgrading have an external ZENworks database? If so, and you are upgrading from a pre-11.3 version, you need to create the Audit database. For details, see Database Considerations in the ZENworks Upgrade Guide.
After you upgrade to ZENworks 2017, the deployment status of bundles and policies might show inaccurate results.
This is due to performance improvements in the deployment status. Performance is improved by migrating the status reports to a new database schema. During the migration process, Primary Servers will not process the newly uploaded status files.
Wait till the migration process is completed, and then the latest status information will be displayed.
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.novell.com/company/legal/.
Copyright © 2018 Micro Focus Software Inc. All Rights Reserved.