Show Table of Contents
3.7. General Management: Firstboot
Registering a system during firstboot is the same as registering a system using Red Hat Subscription Manager later, so there is no special workflow associated with it. The main reason for mentioning firstboot is that the firstboot wizard does provide several different ways to configure the system for subscriptions and content updates. The system always has some kind of subscription configuration, from the first time it is configured, and understanding those options can make it easier to administer the system later.
During firstboot, the subscription service and attached subscriptions are configured in the Set Up Software Updates screens. There are four choices:
- Red Hat Subscription Management, which covers product-driven subscription services in Customer Portal Subscription Management, Subscription Asset Manager, and Satellite 6
- RHN Classic, which uses channel-driven access to content
- Satellite or Proxy content delivery, which uses a channel-based system similar to RHN Classic
- Register later
Figure 11. Firstboot
By default, firstboot registers the system to Customer Portal Subscription Management and autoattaches compatible subscriptions. Selecting the Skip automatic subscription selection... checkbox disables autosubscription, so that the system can have subscriptions attached manually.
The firstboot options for setting up the content server are the same as using Red Hat Subscription Manager to configure an existing system.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.