6.4.6.2. Using Multiple Activation Keys at Once —
Provisioning customers should note that multiple activation keys can be included at the command line or in a single kickstart profile. This allows you to aggregate the aspects of various keys without recreating a new key specific to the desired systems, simplifying the registration and kickstart processes while slowing the growth of your key list.
Without this stacking ability, your organization would need at least six activation keys to manage four server groups and subscribe a server to any two groups. Factor in two versions of the operating system, such as Red Hat Enterprise Linux 3 and 4, and you need twice the number of activation keys. A larger organization would need keys in the dozens.
Registering with multiple activation keys requires some caution; conflicts between some values cause registration to fail. Conflicts in the following values do not cause registration to fail, a combination of values is applied: software packages, software child channels, and config channels. Conflicts in the remaining properties are resolved in the following manner:
- base software channels — registration fails
- entitlements — registration fails
- enable config flag — configuration management is set
Do not use system-specific activation keys along with other activation keys; registration fails in this event.
You are now ready to use multiple activation keys at once. This is done with comma separation at the command line with
rhnreg_ks
or in a kickstart profile within the Post tab of the Kickstart Details page. Refer to Section 2.5, “Registering with Activation Keys” and Section 6.4.9.3, “Create a New Kickstart Profile”, respectively, for instructions.