After being granted Organization Administrator access to the Satellite web interface, there are a few steps you’ll need to run through before registering any client systems:
- Create a default System Group
- Create a default Activation Key
- Create and configure accounts for other users
- Download and configure the Satellite migration script
Users without Organization Administrator access cannot see ungrouped systems. To avoid confusion, create a default System Group that newly registered systems will automatically be added to:
- Click on the Systems tab, and then select System Groups from the menu on the left
- Click the ‘create new group’ button at the upper right
- Give the group a name like ‘Default System Group’, and a short description.
- Click ‘Create Group’
In order to register systems with the migration script or as part of a kickstart operation, you must create an Activation Key. Activation keys can also be used in place of a username and password when registering systems manually. In this step, we create a default activation key and associate it with the Default System Group so that newly registered systems are automatically grouped and available to all users.
- Click on the Systems tab, and then select Activation Keys from the menu on the left.
- Click the ‘create new key’ button at the upper right.
- Give the group a short description like ‘Default Activation Key’.
- Check the ‘Universal Default’ box.
- Click on the ‘Create Activation Key’ button.
- Click on the ‘Groups’ tab under the group description text, and then click on the ‘Join’ subtab.
- Check the box next to ‘Default System Group’, and then click the ‘Join Selected Groups’ button.
Follow these steps to allow additional users to access UO RHN Satellite with their DuckID credentials
- Create Account:
- Click on the Users tab, and then click on the ‘create new user’ button at the upper right.
- Enter the username of the new account in the Desired Login field. This should match the user’s DuckID username.
- Check the ‘Pluggable Authentication Modules (PAM)’ box
- Select a salutation (Mr, Mrs, etc), and enter the user’s first name, last name, and e-mail address.
- Click on the ‘Create Login’ button.
If you do not check the PAM option, the account will be local to the UO RHN Satellite web interface, and the password will not be synchronized with the DuckID system. We ask that you avoid creating local accounts unless absolutely necessary.
- Grant Access to System Groups:
- Click on the System Groups tab under the username text.
- Check the box next to ‘Default System Group’.
- Select ‘Default System Group’ in the list of available Default System Groups.
- Click on the ‘Update Defaults’ button.
- Set Time Zone:
- Click on the Preferences tab under the username text, and then click on the Locale subtab
- Set the time zone to GMT
- Click on the ‘Save Preferences’ button
You may optionally assign additional roles to the user. The available roles are:
- Organization Administrator
Users with this role have full access to all of the items listed below, as well as all ungrouped systems. They may also edit the roles of other users within your organization.
- Activation Key Administrator
Users with this role can create, modify, and delete any key within your organization.
- Monitoring Administrator
Users with this role can schedule probes and edit settings for the Monitoring system, if you have Monitoring entitlements available.
- Configuration Administrator
Users with this role can edit managed configuration files and configuration channels, if you have Provisioning entitlements available.
- Channel Administrator
Users with this role can manage software channels, custom packages, and package channel memberships.
- System Group Administrator
Users with this role have complete authority over the systems and system groups to which they are granted access. This role allows users to create new system groups, delete any assigned systems groups, add systems to groups, and manage user access to groups.
A template migration script is available that will reconfigure Red Hat 3, 4, and 5 systems to use the UO RHN Satellite server. This script will need to be edited to use your organization’s Activation Key and to specify other runtime preferences. The script will not remove the system from rhn.redhat.com; it will appear on that site as inactive until deleted manually.
- Download the template from http://rhn.uoregon.edu/pub/bootstrap/bootstrap.sh
- Open the script in a text editor.
- Comment out the
exit 1line just below the echo block.
- Enter your Activation Key (created in Step 2) on the
- If you want to run a full package update after registering, set
- Save the script, and copy it to the system you want to migrate.
- SSH in to the system, and run
Be careful when sharing your modified bootstrap script – anyone with a copy of your activation key can register systems to your organization.