Client Applications; Deploying The Latest Red Hat Network Client Rpms - Red Hat NETWORK 4.0.5 - CLIENT Configuration Manual

Client Applications

In order to utilize most enterprise-class features of Red Hat Network, such as registering
with a RHN Satellite, configuration of the latest client applications is required. Obtaining
these applications before the client has registered with Red Hat Network can be difficult.
This paradox is especially problematic for customers migrating large numbers of older
systems to Red Hat Network. This chapter identifies techniques to resolve this dilemma.
Important
Red Hat strongly recommends that clients connected to a RHN Proxy Server or RHN
Satellite Server be running the latest update of Red Hat Enterprise Linux to ensure proper
connectivity.

2.1. Deploying the Latest Red Hat Network Client RPMs

Red Hat Update Agent (
( ) are prerequisites for using much of Red Hat Network's enterprise
rhn_register
functionality. It is crucial to install them on client systems before attempting to use RHN
Proxy Server or RHN Satellite Server in your environment.
There are several sensible approaches to accomplish this update of the RHN client soft-
ware. One of which involves storing the RPMs in a location that is accessible by all client
systems and deploying the packages with the simplest command possible. In nearly all
cases, a manual deployment of
to be performed. Those client tools should have no issues connecting to your RHN Satellite
or Proxy environment. These discussion below assumes that the "out of box"
are not the latest and do not work for your environment.
rhn_register
Remember, only systems running Red Hat Enterprise Linux 2.1 must use the Red Hat
Network Registration Client to register with RHN. Systems running Red Hat Enterprise
Linux 3 and later can use the registration functionality built into the Red Hat Update
Agent.
This document presumes that the customer has installed at least one RHN Satellite Server
and/or RHN Proxy Server on their network. The example below demonstrates a simple ap-
proach of deploying
suming the machines don't already have a working RHN. The administrator has populated
the
/var/www/html/pub/
(for RHEL 2.1 systems) RPMs that his client systems need, and then has simply deployed
up2date
up2date
and
up2date rhn_register
directory with a copy of the
) and Red Hat Network Registration Client
and
rhn_register
for the first time by an administrator as-
Chapter 2.
(if RHEL 2.1) do not need
and
up2date rhn_register
and
up2date