Chapter 1. Introduction4package profile to the database on the RHN Satellite Server; those packages are removed from thelist of outdated packages for the client.The organization can configure the website for the RHN Satellite Server to be accessible from thelocal area network only or from both the local area network and the Internet. The Satellite's version ofthe RHN website allows full control over client systems, system groups, and users.The RHN Satellite Server management tools are used to synchronize the RHN Satellite Serverdatabase and package repository with Red Hat Network. The RHN Satellite Server import tool allowsthe system administrator to include custom RPM packages in the package repository.RHN Satellite Server can be used in conjunction with RHN Proxy Server to deliver a distributed,self-contained Red Hat Network deployment for the organization. For example, an organization canmaintain one RHN Satellite Server in a secure location. Red Hat systems with local network accessto the RHN Satellite Server can connect to it. Other remote offices can maintain RHN Proxy Serverinstallations that connect to the RHN Satellite Server. The different locations inside the organizationmust be networked, but this can be a private network; an Internet connection is not required for any ofthe systems. Refer to the RHN Proxy Server Installation Guide for more information.Figure 1.1. Using RHN Satellite Server and RHN Proxy Server Together1.5. Summary of StepsImplementing a fully functional RHN Satellite Server requires more than installing software and adatabase. Client systems must be configured to use the Satellite. Custom packages and channelsshould be created for optimal use. Since these tasks extend beyond the basic installation, they arecovered in detail in other guides, as well as this RHN Satellite Server Installation Guide. For a full listof the necessary technical documents, refer to Chapter 2, Requirements.