Novell ZENworks Patch Management Update Agent 6.4 Service Pack 2

  • 7002958
  • 09-Apr-2009
  • 30-Apr-2012


Novell ZENworks Patch Management 6.4 - ZPM6.4


Service Pack 2 (SP2) for the ZPM Update Agent for Linux/Unix/Mac contains the latest enhancements and defects fixes that stabilizes the Agent to increase performance and reliability.

Note:Service Pack 2 for the Windows Agent is not included in this release.
Applies To:ZPM Update Agent Linux/Unix/Mac 6.4

Patch Name:Novell ZENworks Patch Management Update Agent 6.4 SP2 (LinuxUnixMac)


What's New
Patch and Remediation support for IBM AIX 6.1
Patch and Remediation support for HP-UX 11.31
Patch and Remediation support for RHEL 5x86 and x86_64

Linux/Unix/Mac (LUM)
Below are the list of fixes included in the ZPM Update Agent 6.4 SP2 (6.4xxx) for LUM:

55981LUM Agent on Mac OSX Reports Service Inventory With Memory Address and PID
55982LUM: Unable to resolve dirty R status after rebooting the Red Hat 5 Server.
56589LUM Agent: HP-UX  11.31 - Default BOOTDIR set to non-existent directory
57124LUM Agent: DAU NICE VALUE for Unix Agent Interpreted Incorrectly On Solaris



Lumension Security Engineering has created the following fixes:
Patch NameDescription
C - Lumension PatchLink Update Agent Upgrade for Linux/Unix/Mac from 6.0 or higher to 6.4xx (See Notes)Patch is designed to be deployed from the Update Server Web UI to upgrade your existing Update Agent for Linux/Unix/Mac to version 6.4xxx.
B - Lumension PatchLink Update Server 6.4 Service Pack 2Patch is designed to be installed on the Update Server 6.4.  Update will replace the Agent Installers Page with the latest version of the Agent.

Installation Notes


  • This patch will upgrade previous Agent versions 6.0 to 6.4191
  • Deploying this to a system that doesn't meet the requirements may result in the Agent going off-line; fixing it will require manual intervention.
  • Automatic installation uses the "at" subsystem to run the upgrade detached from the running Agent. On Mac OS X,"atrun" will be automatically enabled and disabled, if needed.
  • Automatic installation will normally "complete" successfully before actually upgrading the Agent. The actual installation is scheduled with "at" for "now + 2 minutes." When the actual upgrade is complete, a DAU will occur, and the server will become aware of the change.
  • The new Agent will run out of the "patchagent" directory; some earlier versions ran out of a different directory.