Novell Home

My Favorites

Close

Please to see your favorites.

System Update overwrites zman-config.properties

This document (7011396) is provided subject to the disclaimer at the end of this document.

Environment

Novell ZENworks Endpoint Security Management 11.2
Novell ZENworks Patch Management 11
Novell ZENworks Configuration Management 11.2
Novell ZENworks Asset Management 11.2

Situation

Whenever a Primary server is upgraded, the zman-config.properties file (see "Files" in the zman reference at http://www.novell.com/documentation/zenworks11/zen11_utils/data/bookinfo.html) is overwritten, losing any customization.

If the server uses a non-standard port (not 80 and 443, such as with OES) and the GLOBAL_OPTIONS_FILE parameter is used to specify the port, then after an upgrade, zman may fail with the error
Error:Could not connect to the ZENworks Server using SSL. If you are connecting to a server on a different management zone, use the --cleartext option to connect without SSL because zman will not be able to validate the servers certificate. If the ZENworks Server is running on a port other than 443, use the --port option to specify the correct port. Note that the ZENworks Servers on the OES platform are usually configured on a different port because the port 443 is in use by another application.

Resolution

Workaround:
take a backup copy of zman-config.properties before an upgrade, and copy back afterwards

Status

Reported to Engineering

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7011396
  • Creation Date:19-NOV-12
  • Modified Date:19-NOV-12
    • NovellZENworks Asset Management
      ZENworks Configuration Management
      ZENworks Endpoint Security Management
      ZENworks Patch Management

Did this document solve your problem? Provide Feedback