Registering A System To An Organization - Red Hat NETWORK SATELLITE 5.1.1 Reference Manual

Hide thumbs Also See for NETWORK SATELLITE 5.1.1:
Table of Contents

Advertisement

channels that contain packages unsuitable for the system. For example, a Red Hat Enterprise Linux
2.1 system cannot be subscribed to the Red Hat Enterprise Linux 3 channel.
The unique Digital Certificate for the system is generated on the system in the file /etc/sysconfig/
rhn/systemid.
When using activation keys to assign channels, consider these rules:
• A key may specify either zero or one base channel. If specified, it must be a custom base channel.
If not, the base channel corresponding to the system's Red Hat distribution is chosen. For instance,
you may not subscribe a Red Hat Enterprise Linux 2.1 system to the Red Hat Enterprise Linux 3
channel.
• A key may specify any number of child channels. For each child channel, subscription is attempted.
If the child channel matches the system's base channel, subscription succeeds. If it does not, the
subscription fails silently. Refer to
• Keys may be modified by any user with the role of Activation Key
Administrator or Satellite Administrator (or both). These permissions are set
through the Users tab of the RHN website. Refer to
"
for details.
• Systems registered by activation keys are tied to the organization account in which the key was
created, not the key itself. After registration, a key can be deleted safely without any effect on the
systems it was used to register.

2.6. Registering a System to an Organization

RHN Satellite Server now supports the Organizations feature, which allows administrators to
appropriate software and system entitlements across various organizations, as well as control
an organization's access to systems management. Systems can now be registered directly to an
organization.
To register a system to an organization on a satellite, you can use the username and password of an
account that is created within that organization. For example, if there is an organization called Sales
Team, with a username salesadmin and password abc123, using these credentials assures that a
system is registered to the proper organization.
For example:
rhnreg_ks --user=salesadmin --password=abc123
Important
The --orgid option (for RHEL 4 and 5) and the --orgpassword option (in RHEL 4)
in the rhnreg_ks command are not related to the Organizations feature and should
not be used in the context of registering systems to organizations.
For more information about the Organizations feature, refer to
Organizations".
Section 6.6, "Channels"
Section 6.9, "Users —
Registering a System to an Organization
for more information.
Section 6.11.1, "Satellite Tools
33

Advertisement

Table of Contents
loading

Table of Contents