Red Hat NETWORK 4.1.0 - CLIENT Configuration Manual

Also see for NETWORK 4.1.0 -: Manual Reference guide

Contents

Red Hat NETWORK 4.1.0 - CLIENT Configuration Manual Manual pdf 7 page image

Chapter 2.Client ApplicationsIn order to utilize most enterprise-class features of Red Hat Network, such as registeringwith a RHN Satellite, configuration of the latest client applications is required. Obtainingthese applications before the client has registered with Red Hat Network can be difficult.This paradox is especially problematic for customers migrating large numbers of oldersystems to Red Hat Network. This chapter identifies techniques to resolve this dilemma.ImportantRed Hat strongly recommends that clients connected to a RHN Proxy Server or RHNSatellite Server be running the latest update of Red Hat Enterprise Linux to ensure properconnectivity.2.1. Deploying the Latest Red Hat Network Client RPMsRed Hat Update Agent (up2date) and Red Hat Network Registration Client(rhn_register) are prerequisites for using much of Red Hat Network’s enterprisefunctionality. It is crucial to install them on client systems before attempting to use RHNProxy 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 clientsystems and deploying the packages with the simplest command possible. In nearly allcases, a manual deployment of up2date and rhn_register (if RHEL 2.1) do not needto be performed. Those client tools should have no issues connecting to your RHN Satelliteor Proxy environment. These discussion below assumes that the "out of box" up2date andrhn_register are not the latest and do not work for your environment.Remember, only systems running Red Hat Enterprise Linux 2.1 must use the Red HatNetwork Registration Client to register with RHN. Systems running Red Hat EnterpriseLinux 3 and later can use the registration functionality built into the Red Hat UpdateAgent.This document presumes that the customer has installed at least one RHN Satellite Serverand/or RHN Proxy Server on their network. The example below demonstrates a simple ap-proach of deploying up2date and rhn_register for the first time by an administrator as-suming the machines don’t already have a working RHN. The administrator has populatedthe /var/www/html/pub/ directory with a copy of the up2date and rhn_register(for RHEL 2.1 systems) RPMs that his client systems need, and then has simply deployed