zman petf and betf do not export content

  • 7002543
  • 04-Feb-2009
  • 30-May-2012

Environment

Novell ZENworks 10 Configuration Management with Support Pack 1 - 10.1
Novell ZENworks 10 Configuration Management with Support Pack 2 - 10.2
Novell ZENworks 10 Configuration Management with Support Pack 3 - 10.3
Novell ZENworks 11 Configuration Management
Novell ZENworks 11 Configuration Management Support Pack 1 - ZCM 11 SP1

Situation

Using zman petf and zman betf do not provide content file for policies with content, such as GPO policies.  How can the content be obtained?

Resolution

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

In 11.2 and later, use betf with command line option:
 
-c, --export-content
as shown in the documentation https://www.novell.com/documentation/zenworks11/zen11_utils/data/b74pt40.html#b8an1xx

For prior releases:
Workaround

To export the policy:

  1. Launch ZCC.
  2. Navigate to the list of policies screen.
  3. Select the policy to be exported and click the "details " tab .
  4. Click the "configure" button in the "Windows Group Policy settings" panel to launch the Group Policy helper tool.
  5. Close the helper tool.
  6. Click "ok " on the "success " dialog  window.
  7. Click "upload " on the "confirm group policy settings " dialog window.
  8. Note the "path to the zip file " that is displayed in the windows confirmation dialog window.
  9. This zip file can be used along with the settings file and action file (XMLs) generated with the zman petf command to create a new group policy.
  10. Run the zman petf command to export the policy to a xml file such as export.xml
    For example,
    zman petf \policies c:\export.xml
  11. Edit the export_actioncontentinfo.xml file to update the path of the zip file created in step 8 above.
To import the policy in a new zone:
 
Run:
zman pc myPolicyName c:\export.xml --actioninfo=c:\export_ActionContentInfo.xml
zman bc .
If the original MSI is not available, assign the original zone bundle to a device and refresh the device.  The MSI will be available in the cache\zmd folder within some subfolder dynamically generated during refresh.

For non-MSI bundles:
make the files available in the same location as the XML file and use --actioninfo on zman bc to import the content

Feedback service temporarily unavailable. For content questions or problems, please contact Support.