54 Chapter 8. MaintenanceIf you generated a new SSL certificate during secondary Satellite installation to include a newCommon Name value, instead copy the RPMs from the secondary to the primary Satellite andredistribute the client-side certificate. If you also created another bootstrap script, you may usethis to install the certificate on client systems.5. If you did not create a new bootstrap script, copy the contents of/var/www/html/pub/bootstrap/ from the primary Satellite to the secondary. If you didgenerate a new one, copy that directory’s contents to the primary Satellite.6. Turn off the RHN Task Engine on the secondary Satellite with the following command:/sbin/service taskomatic stopYou may use custom scripting or other means to establish automatic start-up/failover of theRHN Task Engine on the secondary Satellite. Regardless, it will need to be started uponfailover.7. Share channel package data (by default located in /var/satellite) between the Satellitesover some type of networked storage device. This eliminates data replication and ensures aconsistent store of data for each Satellite.8. Make the various Satellites available on your network via Common Name and a method suitingyour infrastructure. Options include round-robin DNS, a network load balancer, and a reverse-proxy setup.8.7. Conducting Satellite-Specific TasksUsing a RHN Satellite Server is quite similar to using the hosted version of Red Hat Network. Forthis reason, you should consult the RHN Reference Guide to obtain detailed instructions to standardtasks, such as editing System Profiles and updating packages. Tasks directly related to managingcustom channels and Errata are covered in the RHN Channel Management Guide. This section seeksto explain activities available only to Satellite customers.8.7.1. Using the Tools menuIn addition, to the standard categories available to all users through the top navigation bar, SatelliteOrganization Administrators also have access to a Tools menu. Clicking this opens the RHN InternalTools page.