Cool Solutions

How to Rerun ZCM System Update 10.0.3 on a Windows Device



June 5, 2008 2:51 pm





Note: This is an excerpt from this TID. Since the Support TIDs are sometimes updated after we have showcased them in Cool Solutions, please refer to the actual TID before implementing this solution, to ensure that you are working with the most current version.

In some cases, 10.0.3 may not install properly or completely to a device. In such situations, it may be necessary to reapply the system update. One common cause of such a requirement is rebooting the device in the middle of the update process prior to prompting.

The update files are located in the %ZENWORKS_HOME%\work\system-update\10_0_3 directory.

The System Update process should create a series of log files ranging from “command0.log” to “command67.log” from the processing of the various MSI components.

While it is normal for a couple of log files to not appear since they are 32/64-bit specific, if command67.log is missing, it is one indication that something has gone amiss. However, just because all of the logs appear does not guarantee everything ran successfully.

(Note: Client Devices will create far fewer logs than Servers since fewer MSIs will be installed.)

%ZENWORKS_HOME%\logs\SystemUpdate_10_0_3.log is another key log file to look at to see what may or may not have worked during the update process.


If you determine that you would like to rerun system update on a device, please perform the following:

  1. Rename %ZENWORKS_HOME%\Work\SystemUpdate\10_0_3\SystemUpdate.INI. to SystemUpdate.INI
  2. Edit SystemUpdate.INI and remove [ExitCodes] and [Results] Sections from the end of the INI file. (Note: These were added during the previous update process.)
  3. Make sure the “Novell ZENworks Update Service 10.0.3” does not exist. If it does, run “SC Delete zenupdate_10_0_3” to remove it.
  4. Run “SystemUpdate_10_0_3.exe -i -s”. This should install and start the Update Service.

It may take a few minutes before much happens and when the process is running there will be few if any visible signs its running.

Check time/date sample on the XXCommand.log files to see if new ones are being created.

You can also echo the %ZENWORKS_HOME%\logs\SystemUpdate_10_0_3.log file to the screen to see if updates are being written to it.

In some cases, the final update prompt does not happen for nearly 30 minutes after the update process appears to have completed.

Please be patient and wait for the process to complete.

There should not be any danger in re-running this update process against a server that has already run the update.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Categories: Uncategorized


Disclaimer: This content is not supported by Micro Focus. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.


  1. By:mdstewar

    Great article!

  2. By:mmoran2

    “Rename %ZENWORKS_HOME%\Work\SystemUpdate\10_0_3\SystemUpdate.INI. to SystemUpdate.INI ”

    I do not see the difference in SystemUpdate.INI and SystemUpdate.INI .. am I missing something??