System Update immediately becomes baselined when imported

• Importing modified System Update to a zone, to apply updated files automatically (as part of the install process for a patch)
• System Update immediately becomes "baselined"
  

This is fixed in version 11.2 - see KB 7010044 "ZENworks Configuration Management 11.2 - update information and list of fixes" which can be found at https://www.novell.com/support - from 11.2 onwards, baselining does not occur when using "zman sui", unless specifically requested - see https://www.novell.com/documentation/zenworks11/zen11_utils/data/b74pt40.html#bez3766

Workaround, for all versions of ZCM prior to 11.2:

1. delete the "baselined" System Update, using zman sudu e.g.,
   zman sudu "Update for ZENworks (11.0)" --force
   Note: the "--force" (or "-f") option will remove all existing assignments for the System Update
   See https://www.novell.com/documentation/zenworks11/zen11_utils/data/b74pt40.html#bez35yg for details of this command
   
2. To inform ZCM that this is an "upgrade", and should not be baselined, ensure that "superceded" files exist for a previous version; check
   Windows: %ZENWORKS_HOME%\install\downloads\msi
   and %ZENWORKS_HOME%\install\downloads\rpm
   Linux: /opt/novell/zenworks/install/downloads/msi
   and /opt/novell/zenworks/install/downloads/rpm
   look for *.superceded (files ending in .superceded), and if these do not exist, create one in each location
   for example, if upgrading to ZCM 11.0, create
   Windows: %ZENWORKS_HOME%\install\downloads\msi\novell-zenworks-version-10.3.0.msi.superceded
   and %ZENWORKS_HOME%\install\downloads\rpm\novell-zenworks-version-10.3.0.noarch.rpm.superceded
   Linux: /opt/novell/zenworks/install/downloads/msi/novell-zenworks-version-10.3.0.msi.superceded
   and /opt/novell/zenworks/install/downloads/rpm/novell-zenworks-version-10.3.0.noarch.rpm.superceded and then use
   chown zenworks.zenworks [filename]
   for each file to make zenworks user and group the owner
   Note: the filenames must begin novell-zenworks-version- and have a version number as shown above; the version number is not significant, as long as it's an earlier version than the SYSTEM Update being imported. These files can be empty (i.e., the content of the file is not important,. just the name).
   
3. Re-import the System Update - it should show as "downloaded", and can then be deployed as desired.
   

TID 7012095 Can "superceded" files be safely deleted? for information about why these files may be needed even after upgrading to 11.2.