General Tips For Multi-Org Usage - Red Hat NETWORK SATELLITE 5.3.0 Reference Manual

Figure 9.2. Decentralized Satellite Management for Multi-Department Organization

9.1.3. General Tips for Multi-Org Usage

Regardless of the specific model above you choose in the management of your multi-org Satellite, the
following best practices tips can help.
It is not recommended to use the administrative organization (organization #1) for registering
systems and creating users in any situation unless you intend to the use Satellite as a single
organization Satellite or are in the process of migrating from a single organization Satellite to a
multiple organization Satellite. This is due to the following reasons:
1. The administrative organization is treated as a special case with respect to entitlements. You can
only add or remove entitlements to this organization implicitly by removing them or adding them
from the other organizations on the Satellite.
2. The administrative organization is intended to be a staging area for subscriptions and entitlements.
When you associate the Satellite with a new certificate, any new entitlements will by granted
to this organization by default. In order to make those new entitlements available to other
organizations on the Satellite, you will need to explicitly allocate those entitlements to the other
organizations from the administrative organization.
9.1.3.1. Certificate Has Less Entitlements Than I Am Using
If you are issued a new Satellite certificate and it contains less entitlements than the systems in the
organizations on your Satellite are consuming, you will be unable to activate this new certificate when
uploading it through the Satellite's web interface under Admin Satellite Configuration Certificate,
uploading it through the
http://rhn.redhat.com profile of the Satellite system under the Satellite tab,
General Tips for Multi-Org Usage
165