MSI bundle export with MST file lists MSI file twice in ActionContentInfo.xml file

  • 7012884
  • 17-Jul-2013
  • 30-Oct-2013

Environment

Novell ZENworks Configuration Management 11.2 Bundles

Situation

When exporting a Bundle that contains and MSI and MST file, the import of that Bundle may fail. The name of the MSI is specified twice instead of the name of the MST file in the ActionContentInfo.xml file.

Example:

<?xml version="1.0" encoding="UTF-8"?>
-<ActionInformation> -<ActionSet type="Install"> -<Action type="Install MSI
Action" index="1" name="Install MSI Action"> -<Content>
<!--Edit the file name in the <ContentFilePath> element to provide the full
path of the content file. Important: If you modify the file name here to
associate a file with a different name to this action, modify every occurrence
of this file name in the <Data> element for this action in the bundle XML file.
-->
 <ContentFilePath includeAllFilesinSubFolders="false"
includeAllFilesinFolder="false">Firefox.msi</ContentFilePath> </Content>
-<Content>
<!--Edit the file name in the <ContentFilePath> element to provide the full
path of the content file. Important: If you modify the file name here to
associate a file with a different name to this action, modify every occurrence
of this file name in the <Data> element for this action in the bundle XML file.
-->
 <ContentFilePath includeAllFilesinSubFolders="false"
includeAllFilesinFolder="false">Firefox.msi</ContentFilePath> </Content>
</Action> </ActionSet> </ActionInformation>


Note the second Firefox.msi. It should read:

 <ContentFilePath includeAllFilesinSubFolders="false"
includeAllFilesinFolder="false">firefox.mst</ContentFilePath> </Content>
</Action> </ActionSet> </ActionInformation>


Workaround:

Before creating a Bundle from an export, modify the file names to reflect the correct names of the files in the ActionContentInfo.xml file.

Resolution

This is fixed in version 11.2.4 - see KB 7012027 "ZENworks Configuration Management 11.2.4 - update information and list of fixes" which can be found at https://support.microfocus.com/kb/doc.php?id=7012027