SUSE Manager/System Activation Keys

From MicroFocusInternationalWiki
Revision as of 09:47, 16 March 2015 by Gameboy974 (Talk | contribs) (Undo revision 21139 by (talk))

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

SUSE Manager Main Page

System Activation Keys creation best-practice

1. Avoid using the "SUSE Manager Default" parent channel. You will probably never have an action key where you want the system "guessing" as to which is the best parent channel. Assign it yourself - and create another activation key for each distribution and architecture.

2. Create bootstrap script/Activation Key "pairs" - designed to work together for proper channel, group, and config assignments.

3. Do as much automation as is practical in your activation key - like channel assignments, package installs, System Group memberships, and Configuration Channel assignments. That way you will have less manual interaction with systems post-registration.

4. Use something human readable for the key itself - unless you really enjoy auto-generated numbers.

5. Always check the "Provisioning" entitlement box - now that the mandatory module (Lifecycle Management) includes it. Add the SUSE Manager Tools child channel after that. Then return to details and select the check box by "Configuration File Deployment" - and your packages get "magically" added for Configuration Management.

One thing about the "Configuration File Deployment" check-box... People ALWAYS miss this at least once. The check-box only appears AFTER you click the "create key" button on the first page. And you have to scroll back down the page to see it!

After you click the "create key" the first time - scroll down and check the box and then click "Update Key" to save that feature.