RPM installation for the ZAM 7.5 Unix Client/Collector

  • 3884556
  • 31-Mar-2008
  • 27-Apr-2012


Novell Zenworks Asset Managment 7.5


An RPM was created to install the Zenworks Asset Management 7.5 Unix client. Until the RPM is officially released an FTF file can be requested from novell support. Looking at the bug, no ftf is available that is attached. This was worked on by an engineer that no longer works for Novell.


Fixed in ZENworks Asset Management 7.5 Interim Release 19 or newer

Interim Releases can be scheduled to run automatically or can be downloaded manually at https://download.novell.com/patch/finder . The Interim releases can be set up within the ZAM Manager for the Task server to check the site on a scheduled basis, and download and apply them automatically. Please refer to the Help Section details of how to set up automatic downloads if desired.

Each interim release is cumulative. If Interim Release 19 is not available due to a newer interim release being placed on the website, be assured that the code needed is in the later release.

Additional Information

In order for a Client installed through this RPM to function correctly,one of two things must also happenbefore the Client can begin communicating with the intended Collection Server
OPTION 1: The customer must hand-edit /etc/init.d/tscclient.conf , adding the name (or IP address) of the Collection Server to the line provided for that purpose. In this case, the Client will need to be restarted after hand-editing the tscclient.conf file.
OPTION 2: An auxiliary (Unix-format text) file named colsvr needs to be used with this RPM, including exactly one line:
...where TheCollectionServer'sName represents the name or IP address of the Collection Server to which this Client needs to report.
In this case, the colsvr file will need to be left in the CWD, the same directory as the .RPM file, where the RPM can find it at install time. Also in this case, the Client will NOT need to be restarted; after the install has completed, the Client should immediately begin reporting to the intended Collection Server. If neither option is used, the Client will have no idea what Collection Server it should report to, and will on startup begin broadcasting a "Lost" message.

Internal Notes