Installation guide

Chapter 1. Introduction 5
page. These Channel Content ISOs differ from the distribution ISOs previously mentioned in
that they contain metadata necessary for parsing and serving packages by Satellite.
6. If installing a Stand-Alone Database, you prepare your database instance using the formula
provided in Chapter 2 Requirements.
7. You install Red Hat Enterprise Linux AS and then RHN Satellite Server 3.7 on the Satellite
machine.
8. You create the first user account on the Satellite by opening the Satellite’s hostname in a Web
browser and clicking Create Account. This will be the Satellite Administrator’s account.
9. You use the RHN Satellite Synchronization Tool to import the channels and associated pack-
ages into the Satellite.
10. You register a representative machine for each distribution type, or channel (Red Hat Enterprise
Linux AS 2.1, 3, 4), to the Satellite.
11. You copy (using SCP) the rhn_register and up2date configuration files from the
/etc/sysconfig/rhn/ directory of each machine individually to the /pub directory on the
Satellite. The rhn-org-trusted-ssl-cert-*.noarch.rpm will already be there.
12. You download and install from the Satellite the configuration files and
rhn-org-trusted-ssl-cert-*.noarch.rpm on the remaining client systems of the same
distribution type. Repeat this and the previous step until all distribution types are complete.
13. Through the Satellite’s website, you create an Activation Key for each distribution aligned to
the appropriate base channel. At this point, system groups and child channels may also be pre-
defined.
14. You then run the Activation Key from the command line (rhnreg_ks) of each client system.
Note that this step can be scripted to batch register and reconfigure all remaining client systems
in a distribution.
15. You should record all relevant usernames, passwords and other login information and store in
multiple secure places.
16. Now that the Satellite is populated with standard Red Hat channels and packages and all clients
are connected to it, you may begin creating and serving custom channels and packages. Once the
custom RPMs are developed, you can import them into the Satellite using the RHN Push and
add custom channels to store them through the Satellite’s website. Refer to the RHN Channel
Management Guide for details.