ZENworks Linux Management – name resolution

ZLM name resolution
From zenwiki

RCE will use DNS for all name resolution between client and server.

There is a rule for server to client name resolution:

– if the hostname is ‘localhost.localdomain’ then never use DNS for
name resolution; instead use the last known IP address for the device

– if the hostname is not ‘localhost.localdomain’ then RCE assumes that
(Dynamic) DNS is being used and DNS is used for client resolution

If the deployment scenario:

does not include Dynamic DNS

and

managed clients have Dynamic IP addressing (via DHCP)

and

managed clients have been given hostnames

then the default RCE installation will have problems reliably
connecting from the RCE server to devices.

Symptoms of this include:

– managed machines never showing software inventory or target
information in RCE
– managed machines never receiving transaction or job data

The solution:
add the flag

client_comm_type=IP

to /etc/ximian/rcserver/rcserver.conf

ZLM troubleshooting
From zenwiki

– Some of the hardware information does not show up under VMware. Known
issue.

– if the software information and target do not get populated then check
the following:

– is the daemon running; telnet to 505 on the client from the server.

– is rcd-modules installed on the client

– how is the ZLM server resolving the client IP address? By default if
the machine name is not ‘linux’ or ‘localhost.localdomain’ then the ZLM
server will use DNS to find the client; if it can’t resolve (client not
in DNS) then you’ll not get things working.

– change ZLM name resolution mechanism.

ZENworks Linux Management – rcmirror-ftp.conf

Rcmirror-ftp.conf
From zenwiki

A rcmirror config to get SUSE LINUX Professional updates from ftp servers like ftp.uni-kl.de.

Exchange ftp.uni-kl.de with any prefereed SUSE mirror you get in YaSTs YOU menu

[rcmirror]
cachedir=/var/cache/rcmirror-you

[remote]
base=ftp://ftp.uni-kl.de/pub/linux/suse/
type=yast

[local]
rcmanuser=####
rcmanpassword=####

[channel]
name=suse-90-i586
localname=sl90-i586-patch
#target=suse-90-i586

[channel]
name=suse-91-i586
localname=sl91-i586-patch

[channel]
name=suse-92-i586
localname=sl92-i586-patch

ZENworks Linux Management – rcmirror-you.conf

Rcmirror-you.conf
From zenwiki

# rcmirror-you.conf
#
# ezs Nov 04
#
# ZLM 6.6 Mirror configuration to get updates from YOU
#
# create a unique cache for each rcmirror process
# the directory must exist

[rcmirror]
cachedir=/var/cache/rcmirror-you

[remote]
base=http://sdb2.suse.de/download
type=yast
user=
# NOTE: Do not use the MD5 hash for this password. Include it in clear text
password=

# a simple http proxy can be used
#proxy=http:// : @ : #proxy=http://proxyuser:[email protected]:2081

# create a ZLM service account – e.g. ZLM-rcmirror
[local]
rcmanuser=zlm-service
rcmanpassword=

# echo -n ‘password’ | md5sum

# To list all channels available use rcmirror -l -c/etc/ximian/rcmirror-you.conf

[channel]
name=nld-9-i586
localname=nld-9-i586-patch

[channel]
name=sles-9-i586
localname=sles-9-i586-patch

[channel]
name=sles-8-i386
localname=sles-8-i386-patch

ZENworks Linux Management – rcmirror-web-bos.conf

Rcmirror-web-bos.conf
From zenwiki

# rcmirror-web-bos.conf
#
# ezs Nov 04
#
# ZLM 6.6 Mirror configuration to get updates from
# the private Ximian ZLM update service web-bos-ma-us.rc.ximian.com
#
# create a unique cache for each rcmirror process
# the directory must exist

[rcmirror]
cachedir=/var/cache/rcmirror-web-bos

# rcd needs to be activated against the upstream ZLM server
[remote]
base=https://web-bos-ma-us.rc.ximian.com

# a simple http proxy can be used
#proxy=http:// : @ : #proxy=http://proxyuser:[email protected]:2081

# create a ZLM service account – e.g. ZLM-rcmirror
[local]
rcmanuser=zlm-service
rcmanpassword=

# echo -n ‘password’ | md5sum

# To list all channels available use
# rcmirror -l -c/etc/ximian/rcmirror-web-bos.conf

[channel]
name=zenworks66