| Installation GuidePart V. After installationThis part of the Red Hat Enterprise Linux Installation Guide covers finalizing the installation, as well as some installation-related tasks that you might perform at some time in the future. These include: using a Red Hat Enterprise Linux installation disc to rescue a damaged system. upgrading to a new version of Red Hat Enterprise Linux. removing Red Hat Enterprise Linux from your computer.
Firstboot is only available on systems after a graphical installation or after a kickstart installation where a desktop and the X window system were installed and graphical login was enabled. If you performed a text-mode installation or a kickstart installation that did not include a desktop and the X window system, the firstboot configuration tool does not appear. Firstboot launches the first time that you start a new Red Hat Enterprise Linux system. Use firstboot to configure the system for use before you log in. Click Forward to start firstboot. 34.1. License InformationThis screen displays the overall licensing terms for Red Hat Enterprise Linux. If you agree to the terms of the license, select Yes, I agree to the License Agreement and click Forward. 34.2. Configuring the Subscription ServiceThe products installed on a system (including the operating system itself) are covered by subscriptions. A subscription service is used to track registered systems, the products installed on those systems, and the subscriptions attached to the system to cover those products. The Subscription Management Registration screens identify which subscription service to use and, by default, attach the best-matched subscriptions to the system. 34.2.1. Set Up Software UpdatesThe first step is to select whether to register the system immediately with a subscription service. To register the system, select Yes, I'd like to register now, and click Forward. Even if a system is not registered at firstboot, it can be registered with any of those three subscription services later, using the Red Hat Subscription Manager tools . More information about the Red Hat Subscription Manager tools can be found in the Red Hat Subscription Management Guide. Use the Choose Service screen to choose what kind of subscription service to register the system with. Click Proxy Setup to configure a proxy server if necessary. - Red Hat Subscription Management
Any subscription service which uses the proper X.509 certificates to identify the system, installed products, and attached subscriptions is part of Red Hat Subscription Management. This includes Customer Portal Subscription Management (hosted services), Subscription Asset Manager (on-premise subscription service and proxied content delivery), and CloudForms System Engine (on-premise subscription and content delivery services). This option is the default. Red Hat Subscription Management is strongly recommended for organizations that do not run a local Satellite server. - Red Hat Network (RHN) Classic
Select the Red Hat Network (RHN) Classic option to use the legacy systems-management features of Red Hat Network. While RHN Classic can be used with Red Hat Enerprise Linux 6.x systems, it is intended primarily for existing, legacy systems. It is recommended that new installations use Red Hat Subscription Management. - An RHN Satellite or RHN Proxy
Use this option in environments with access to a local mirror of the Red Hat Network content.
34.2.3. Subscription Management RegistrationRed Hat uses X.509 certificates to identify installed products on a system, the subscriptions attached to a system, and the system itself within the subscription service inventory. There are several different subscription services which use and recognize certificate-base subscriptions, and a system can be registered with any of them in firstboot: Customer Portal Subscription Management, hosted services from Red Hat (the default) Subscription Asset Manager, an on-premise subscription server which proxies content delivery back to the Customer Portal's services CloudForms System Engine, an on-premise service which handles both subscription services and content delivery
The specific type of subscription/content service does not need to be selected; all three server types (Customer Portal Subscription Management, Subscription Asset Manager, and CloudForms System Engine) are within Red Hat Subscription Management and use the same types of service APIs. The only thing that needs to be identified is the hostname of the service to connect to and then the appropriate user credentials for that service. To identify which subscription server to use for registration, enter the hostname of the service. The default service is Customer Portal Subscription Management, with the hostname subscription.rhn.redhat.com. To use a different subscription service, such as Subscription Asset Manager, enter the hostname of the local server.
Click Forward. Enter the user credentials for the given subscription service to log in.
The user credentials to use depend on the subscription service. When registering with the Customer Portal, use the Red Hat Network credentials for the administrator or company account. However, for Subscription Asset Manager or CloudForms System engine, the user account to use is created within the on-premise service and probably is not the same as the Customer Portal user account. If you have lost your login or password for the Customer Portal, recover them from https://www.redhat.com/wapps/sso/rhn/lostPassword.html. For lost login or password information for Subscription Asset Manager or CloudForms System Engine, contact your local administrator. Set the system name for the host. This is anything which uniquely and clearly identifies the system within the subscription service inventory. This is usually the hostname or fully-qualified domain name of the machine, but it can be any string. Optional. Set whether subscriptions should be set manually after registration. By default, this checkbox is unchecked so that the best-matched subscriptions are automatically applied to the system. Selecting this checkbox means that subscriptions must be added to the system manuall after firstboot registration is complete. (Even if subscriptions are auto-attached, additional subscriptions can be added to the system later using the local Subscription Manager tools.) When registration begins, firstboot scans for organizations and environments (sub-domains within the organization) to which to register the system.
IT environments that use Customer Portal Subscription Management have only a single organization, so no further configuration is necessary. IT infrastructures that use a local subscription service like Subscription Asset Manager might have multiple organizations configured, and those organizations may have multiple environments configured within them. If multiple organizations are detected, Subscription Manager prompts to select the one to join.
If you decided to let Subscription Manager automatically attach subscriptions to the system (the default), then the system scans for the subscriptions to attach as part of the registration process.
When registration is complete, the Subscription Manager reports the applied service level for the system based on the information in the selected subscription and the specific subscription that has been attached to the new system. This subscription selection must be confirmed to complete the registration process.
If you selected to apply subscriptions later, then that part of the registration process is skipped, and the Subscription Manager screen in firstboot simply instructs you to attach subscriptions later.
Click Forward to move to the next configuration area for firstboot, user setup.
Create a user account for yourself with this screen. Always use this account to log in to your Red Hat Enterprise Linux system, rather than using the root account. Enter a user name and your full name, and then enter your chosen password. Type your password once more in the Confirm Password box to ensure that it is correct. To add additional user accounts to your system after the installation is complete, choose ⤍ ⤍ . 34.3.1. Authentication ConfigurationIf you clicked Use Network Login on the Create User screen, you must now specify how users are to be authenticated on the system. Use the drop-down menu to select from the following types of user database: (for use when the user database on the network is not accessible) (Lightweight Directory Access Protocol) (Network Information Service) (for use with Microsoft Active Directory)
When you select the type of user database appropriate for your network, you must provide additional details relevant to that database type. For example, if you select LDAP, you must specify the base distinguished name for LDAP searches, and the address of the LDAP server. You must also select an Authentication Method relevant to the type of user database that you chose, for example, a Kerberos password, LDAP password, or NIS password. The Advanced Options tab lets you enable other authentication mechanisms, including fingerprint readers, smart cards, and local access control in /etc/security/access.conf. For more information, refer to Authentication Configuration in the Red Hat Enterprise Linux Deployment Guide. Use this screen to adjust the date and time of the system clock. To change these settings after installation, click ⤍ ⤍ . Click the Synchronize date and time over the network checkbox to configure your system to use Network Time Protocol (NTP) servers to maintain the accuracy of the clock. NTP provides time synchronization service to computers on the same network. Many public NTP servers are available on the Internet. Use this screen to select whether or not to use Kdump on this system. Kdump is a kernel crash dumping mechanism. In the event of a system crash, Kdump will capture information from your system that can be invaluable in determining the cause of the crash. Note that if you select this option, you will need to reserve memory for Kdump and that this memory will not be available for any other purpose. If you do not want to use Kdump on this system, click Finish. If you want to use Kdump, select the Enable kdump option, then select an amount of memory to reserve for Kdump and click Finish. |
| |
