-<simpara>When installing Red Hat Enterprise Linux, you can customize location, software, and system settings and parameters, using the <emphasis role="strong">Installation Summary</emphasis> window.</simpara>
+<simpara>When installing MSVSphere, you can customize location, software, and system settings and parameters, using the <emphasis role="strong">Installation Summary</emphasis> window.</simpara>
-<simpara role="_abstract">When installing Red Hat Enterprise Linux, you can customize location, software, and system settings and parameters, using the <emphasis role="strong">Installation Summary</emphasis> window.</simpara>
+<simpara role="_abstract">When installing MSVSphere, you can customize location, software, and system settings and parameters, using the <emphasis role="strong">Installation Summary</emphasis> window.</simpara>
<simpara>The <emphasis role="strong">Installation Summary</emphasis> window contains the following categories:</simpara>
<itemizedlist>
<listitem>
<simpara><emphasis role="strong">LOCALIZATION</emphasis>: You can configure Keyboard, Language Support, and Time and Date.</simpara>
</listitem>
<variablelist>
<varlistentry>
@@ -18,7 +18,7 @@
<varlistentry>
<term>SOFTWARE</term>
<listitem>
-<simpara><emphasis role="strong">SOFTWARE</emphasis>: You can configure Connect to Red Hat, Installation Source, and Software Selection.</simpara>
+<simpara><emphasis role="strong">SOFTWARE</emphasis>: You can configure Installation Source, and Software Selection.</simpara>
-<simpara>You can configure Connect to Red Hat, Installation Source, and Software Selection.</simpara>
+<simpara>You can configure Installation Source, and Software Selection.</simpara>
</listitem>
<listitem>
<simpara><emphasis role="strong">SYSTEM</emphasis>: You can configure Installation Destination, KDUMP, Network and Host Name, and Security Policy.</simpara>
@@ -37,7 +37,7 @@
</varlistentry>
<varlistentry>
@@ -49,7 +49,7 @@
<tbody>
<row>
<entry align="left" valign="top"><simpara>Yellow triangle with an exclamation mark and red text</simpara></entry>
@ -68,16 +69,31 @@ index 28ee770..87c0fc1 100644
</row>
<row>
<entry align="left" valign="top"><simpara>Grayed out and with a warning symbol (yellow triangle with an exclamation mark)</simpara></entry>
@@ -49,7 +49,7 @@
@@ -61,39 +61,36 @@
<note>
<simpara>A warning message is displayed at the bottom of the <emphasis role="strong">Installation Summary</emphasis> window and the <emphasis role="strong">Begin Installation</emphasis> button is disabled until you configure all of the required categories.</simpara>
</note>
-<simpara>This section contains information about customizing your Red Hat Enterprise Linux installation using the Graphical User Interface (GUI). The GUI is the preferred method of installing Red Hat Enterprise Linux when you boot the system from a CD, DVD, or USB flash drive, or from a network using PXE.</simpara>
+<simpara>This section contains information about customizing your MSVSphere installation using the Graphical User Interface (GUI). The GUI is the preferred method of installing MSVSphere when you boot the system from a CD, DVD, or USB flash drive, or from a network using PXE.</simpara>
<title>Configuring language and location settings</title>
@@ -69,19 +69,19 @@
<simpara role="_abstract">The installation program uses the language that you selected during installation.</simpara>
<orderedlist numeration="arabic">
<title>Prerequisites</title>
<listitem>
-<simpara>You created installation media. See <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#making-an-installation-cd-or-dvd_assembly_creating-a-bootable-installation-medium">Creating a bootable DVD or CD</link></simpara>
+<simpara>You specified an installation source if you are using the Boot ISO image file.</simpara>
</listitem>
<listitem>
-<simpara>You specified an installation source if you are using the Boot ISO image file. See <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#prepare-installation-source_installing-RHEL">Preparing an installation source</link></simpara>
-</listitem>
-<listitem>
-<simpara>You booted the installation. See <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#booting-the-installer_installing-RHEL">Booting the installer</link></simpara>
+<simpara>You booted the installation.</simpara>
</listitem>
</orderedlist>
<orderedlist numeration="arabic">
<title>Procedure</title>
<listitem>
@ -92,8 +108,7 @@ index 28ee770..87c0fc1 100644
+<simpara>From the right-hand pane of the <emphasis role="strong">Welcome to MSVSphere</emphasis> window, select a location specific to your region.</simpara>
</listitem>
<listitem>
-<simpara>Click <guibutton>Continue</guibutton> to proceed to the <citetitle>Installing and deploying RHEL</citetitle> on the Red Hat Customer Portal window.</simpara>
+<simpara>Click <guibutton>Continue</guibutton> to proceed to the <citetitle>Installing and deploying MSVSphere</citetitle>.</simpara>
<simpara>Click <guibutton>Continue</guibutton> to proceed to the <link linkend="graphical-installation_graphical-installation">Graphical installations</link> window.</simpara>
</listitem>
<listitem>
-<simpara>If you are installing a pre-release version of Red Hat Enterprise Linux, a warning message is displayed about the pre-release status of the installation media.</simpara>
@ -101,55 +116,59 @@ index 28ee770..87c0fc1 100644
<orderedlist numeration="loweralpha">
<listitem>
<simpara>To continue with the installation, click <guibutton>I want to proceed</guibutton>, or</simpara>
@@ -136,7 +136,7 @@ To change any of the settings, complete the following steps, otherwise proceed t
<title>Configuring keyboard, language, and time and date settings</title>
-<simpara>Keyboard, Language, and Time and Date Settings are configured by default as part of <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#installing-rhel-using-anaconda_graphical-installation">Installing RHEL using Anaconda</link>.
-To change any of the settings, complete the following steps, otherwise proceed to <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#configuring-software-settings_graphical-installation">Configuring software settings</link>.</simpara>
+<simpara>Keyboard, Language, and Time and Date Settings are configured by default as part of Installing MSVSphere using Anaconda.</simpara>
</note>
</listitem>
<orderedlist numeration="arabic">
<title>Procedure</title>
@@ -128,7 +121,7 @@ To change any of the settings, complete the following steps, otherwise proceed t
<simpara>Configure keyboard settings:</simpara>
<orderedlist numeration="loweralpha">
<listitem>
-<simpara>Click <guibutton>Done</guibutton> to apply the settings and return to <citetitle>Installing and deploying RHEL</citetitle> on the Red Hat Customer Portal.</simpara>
+<simpara>Click <guibutton>Done</guibutton> to apply the settings and return to <citetitle>Installing and deploying MSVSphere</citetitle>.</simpara>
</listitem>
</orderedlist>
</listitem>
@@ -150,7 +150,7 @@ To change any of the settings, complete the following steps, otherwise proceed t
<simpara>From the left pane, click a group to select additional languages, and from the right pane, select regional options. Repeat this process for languages that you require.</simpara>
-<simpara>From the <emphasis role="strong">Installation Summary</emphasis> window, click <emphasis role="strong">Keyboard</emphasis>. The default layout depends on the option selected in <link linkend="installing-rhel-using-anaconda_graphical-installation">Installing RHEL using Anaconda</link>.</simpara>
+<simpara>From the <emphasis role="strong">Installation Summary</emphasis> window, click <emphasis role="strong">Keyboard</emphasis>. The default layout depends on the option selected in <link linkend="installing-msvsphere-using-anaconda_graphical-installation">Installing MSVSphere using Anaconda</link>.</simpara>
</listitem>
<listitem>
-<simpara>Click <guibutton>Done</guibutton> to apply the changes and return to <citetitle>Installing and deploying RHEL</citetitle> on the Red Hat Customer Portal.</simpara>
+<simpara>Click <guibutton>Done</guibutton> to apply the changes and return to <citetitle>Installing and deploying MSVSphere</citetitle>.</simpara>
</listitem>
</orderedlist>
</listitem>
@@ -161,7 +161,7 @@ To change any of the settings, complete the following steps, otherwise proceed t
<simpara>Click <guibutton>+</guibutton> to open the <emphasis role="strong">Add a Keyboard Layout</emphasis> window and change to a different layout.</simpara>
@@ -173,8 +166,8 @@ To change any of the settings, complete the following steps, otherwise proceed t
<listitem>
<simpara>From the <emphasis role="strong">Installation Summary</emphasis> window, click <emphasis role="strong">Time & Date</emphasis>. The <emphasis role="strong">Time & Date</emphasis> window opens.</simpara>
<note>
<simpara>The <emphasis role="strong">Time & Date</emphasis> settings are configured by default based on the settings you selected in <xref linkend="installing-rhel-using-anaconda_graphical-installation"/>.</simpara>
-<simpara>The <emphasis role="strong">Time & Date</emphasis> settings are configured by default based on the settings you selected in <link linkend="installing-rhel-using-anaconda_graphical-installation">Installing RHEL using Anaconda</link>.</simpara>
-<simpara>The list of cities and regions come from the Time Zone Database (<literal role="package">tzdata</literal>) public domain that is maintained by the Internet Assigned Numbers Authority (IANA). Red Hat can not add cities or regions to this database. You can find more information at the <link xl:href="http://www.iana.org/time-zones">IANA official website</link>.</simpara>
+<simpara>The <emphasis role="strong">Time & Date</emphasis> settings are configured by default based on the settings you selected in <link linkend="installing-msvsphere-using-anaconda_graphical-installation">Installing MSVSphere using Anaconda</link>.</simpara>
+<simpara>The list of cities and regions come from the Time Zone Database (<literal role="package">tzdata</literal>) public domain that is maintained by the Internet Assigned Numbers Authority (IANA). MSVSphere can not add cities or regions to this database. You can find more information at the <link xl:href="http://www.iana.org/time-zones">IANA official website</link>.</simpara>
</note>
</listitem>
<listitem>
@@ -180,7 +180,7 @@ To change any of the settings, complete the following steps, otherwise proceed t
</note>
</listitem>
<listitem>
-<simpara>Click <guibutton>Done</guibutton> to apply the changes and return to <citetitle>Installing and deploying RHEL</citetitle> on the Red Hat Customer Portal.</simpara>
+<simpara>Click <guibutton>Done</guibutton> to apply the changes and return to <citetitle>Installing and deploying MSVSphere</citetitle>.</simpara>
<note>
<simpara>If you disable network time synchronization, the controls at the bottom of the window become active, allowing you to set the time and date manually.</simpara>
</note>
@@ -195,9 +195,9 @@ To change any of the settings, complete the following steps, otherwise proceed t
@@ -207,9 +200,9 @@ To change any of the settings, complete the following steps, otherwise proceed t
<simpara>This section contains information about configuring Installation Destination, KDUMP, Network and Host Name, and Security Policy.</simpara>
-<simpara>Use the <emphasis role="strong">Installation Destination</emphasis> window to configure the storage options, for example, the disks that you want to use as the installation target for your Red Hat Enterprise Linux installation. You must select at least one disk.</simpara>
+<simpara>Use the <emphasis role="strong">Installation Destination</emphasis> window to configure the storage options, for example, the disks that you want to use as the installation target for your MSVSphere installation. You must select at least one disk.</simpara>
-<simpara role="_abstract">Use the <emphasis role="strong">Installation Destination</emphasis> window to configure the storage options, for example, the disks that you want to use as the installation target for your Red Hat Enterprise Linux installation. You must select at least one disk.</simpara>
+<simpara role="_abstract">Use the <emphasis role="strong">Installation Destination</emphasis> window to configure the storage options, for example, the disks that you want to use as the installation target for your MSVSphere installation. You must select at least one disk.</simpara>
<warning>
-<simpara>Back up your data if you plan to use a disk that already contains data. For example, if you want to shrink an existing Microsoft Windows partition and install Red Hat Enterprise Linux as a second system, or if you are upgrading a previous release of Red Hat Enterprise Linux. Manipulating partitions always carries a risk. For example, if the process is interrupted or fails for any reason data on the disk can be lost.</simpara>
+<simpara>Back up your data if you plan to use a disk that already contains data. For example, if you want to shrink an existing Microsoft Windows partition and install MSVSphere as a second system, or if you are upgrading a previous release of MSVSphere. Manipulating partitions always carries a risk. For example, if the process is interrupted or fails for any reason data on the disk can be lost.</simpara>
</warning>
<important>
<itemizedlist>
@@ -207,10 +207,10 @@ To change any of the settings, complete the following steps, otherwise proceed t
@@ -219,10 +212,10 @@ To change any of the settings, complete the following steps, otherwise proceed t
If you choose to partition your system automatically, you should manually edit your <literal>/boot</literal> partition.</simpara>
</listitem>
<listitem>
@ -162,7 +181,7 @@ index 28ee770..87c0fc1 100644
</listitem>
</itemizedlist>
</important>
@@ -226,7 +226,7 @@ If you choose to partition your system automatically, you should manually edit y
@@ -238,7 +231,7 @@ If you choose to partition your system automatically, you should manually edit y
<listitem>
<simpara>From the <emphasis role="strong">Local Standard Disks</emphasis> section, select the storage device that you require; a white check mark indicates your selection. Disks without a white check mark are not used during the installation process; they are ignored if you choose automatic partitioning, and they are not available in manual partitioning.</simpara>
<note>
@ -171,7 +190,12 @@ index 28ee770..87c0fc1 100644
</note>
</listitem>
<listitem>
@@ -256,7 +256,7 @@ If you choose to partition your system automatically, you should manually edit y
@@ -265,11 +258,11 @@ If you choose to partition your system automatically, you should manually edit y
<simpara>Optional: Under <emphasis role="strong">Storage Configuration</emphasis>, select the <emphasis role="strong">Automatic</emphasis> radio button.</simpara>
<important>
<simpara>Automatic partitioning is the <emphasis role="strong">recommended</emphasis> method of partitioning your storage.</simpara>
-<simpara>You can also configure custom partitioning, for more details see <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#manual-partitioning_graphical-installation">Configuring manual partitioning</link></simpara>
+<simpara>You can also configure custom partitioning</simpara>
</important>
</listitem>
<listitem>
@ -180,16 +204,24 @@ index 28ee770..87c0fc1 100644
</listitem>
<listitem>
<simpara>Optional: Select <emphasis role="strong">Encrypt my data</emphasis> to encrypt all partitions except the ones needed to boot the system (such as <literal>/boot</literal>) using <emphasis>Linux Unified Key Setup</emphasis> (LUKS). Encrypting your hard drive is recommended.</simpara>
@@ -270,7 +270,7 @@ If you choose to partition your system automatically, you should manually edit y
@@ -283,7 +276,7 @@ If you choose to partition your system automatically, you should manually edit y
<listitem>
<simpara>Click <guibutton>Save Passphrase</guibutton> to complete disk encryption.</simpara>
<warning>
-<simpara>If you lose the LUKS passphrase, any encrypted partitions and their data is completely inaccessible. There is no way to recover a lost passphrase. However, if you perform a Kickstart installation, you can save encryption passphrases and create backup encryption passphrases during the installation. See the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/performing_an_advanced_rhel_installation/index/"><emphasis>Performing an advanced RHEL installation</emphasis></link> document for information.</simpara>
-<simpara>If you lose the LUKS passphrase, any encrypted partitions and their data is completely inaccessible. There is no way to recover a lost passphrase. However, if you perform a Kickstart installation, you can save encryption passphrases and create backup encryption passphrases during the installation. See the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_an_advanced_rhel_9_installation/index/"><emphasis>Performing an advanced RHEL 9 installation</emphasis></link> document for information.</simpara>
+<simpara>If you lose the LUKS passphrase, any encrypted partitions and their data is completely inaccessible. There is no way to recover a lost passphrase. However, if you perform a Kickstart installation, you can save encryption passphrases and create backup encryption passphrases during the installation.</simpara>
</warning>
</listitem>
</orderedlist>
@@ -287,7 +287,7 @@ If you choose to partition your system automatically, you should manually edit y
@@ -292,7 +285,6 @@ If you choose to partition your system automatically, you should manually edit y
</listitem>
<listitem>
<simpara>Optional: Click the <emphasis role="strong">Full disk summary and bootloader</emphasis> link in the lower left-hand side of the window to select which storage device contains the boot loader.</simpara>
-<simpara>For more information, see <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#boot-loader-installation_configuring-system-settings">Boot loader installation</link>.</simpara>
<note>
<simpara>In most cases it is sufficient to leave the boot loader in the default location. Some configurations, for example, systems that require chain loading from another boot loader require the boot drive to be specified manually.</simpara>
</note>
@@ -301,7 +293,7 @@ If you choose to partition your system automatically, you should manually edit y
<simpara>If you <emphasis role="strong">delete</emphasis> a partition, all data on that partition is lost. If you want to preserve your data, use the <emphasis role="strong">Shrink</emphasis> option, not the <emphasis role="strong">Delete</emphasis> option.</simpara>
</warning>
@@ -298,11 +298,11 @@ If you choose to partition your system automatically, you should manually edit y
@@ -312,12 +304,9 @@ If you choose to partition your system automatically, you should manually edit y
<listitem>
<simpara>To reclaim space, select a disk or partition, and click either the <guibutton>Delete</guibutton> button to delete that partition, or all partitions on a selected disk, or click <guibutton>Shrink</guibutton> to use free space on a partition while preserving the existing data.</simpara>
<note>
@ -206,18 +238,18 @@ index 28ee770..87c0fc1 100644
+<simpara>Alternatively, you can click <guibutton>Delete all</guibutton>, this deletes all existing partitions on all disks and makes this space available to MSVSphere. Existing data on all disks is lost.</simpara>
</note>
</listitem>
<listitem>
-<simpara>Click <guibutton>Reclaim space</guibutton> to apply the changes and return to <citetitle>Installing and deploying RHEL</citetitle> on the Red Hat Customer Portal.</simpara>
+<simpara>Click <guibutton>Reclaim space</guibutton> to apply the changes and return to <citetitle>Installing and deploying MSVSphere</citetitle>.</simpara>
</listitem>
-<listitem>
-<simpara>Click <guibutton>Reclaim space</guibutton> to apply the changes and return to <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#graphical-installation_graphical-installation">Graphical installations</link>.</simpara>
-</listitem>
</orderedlist>
</listitem>
@@ -313,13 +313,13 @@ If you choose to partition your system automatically, you should manually edit y
</orderedlist>
@@ -333,13 +322,13 @@ If you choose to partition your system automatically, you should manually edit y
-<simpara>Red Hat Enterprise Linux uses GRand Unified Bootloader version 2 (<emphasis role="strong"><phrase role="application">GRUB2</phrase></emphasis>) as the boot loader for AMD64 and Intel 64, IBM Power Systems, and ARM. For IBM Z, the <emphasis role="strong">zipl</emphasis> boot loader is used.</simpara>
+<simpara>MSVSphere uses GRand Unified Bootloader version 2 (<emphasis role="strong"><phrase role="application">GRUB2</phrase></emphasis>) as the boot loader for AMD64 and Intel 64, IBM Power Systems, and ARM. For IBM Z, the <emphasis role="strong">zipl</emphasis> boot loader is used.</simpara>
-<simpara role="_abstract">Red Hat Enterprise Linux uses GRand Unified Bootloader version 2 (<emphasis role="strong"><phrase role="application">GRUB2</phrase></emphasis>) as the boot loader for AMD64 and Intel 64, IBM Power Systems, and ARM. For 64-bit IBM Z, the <emphasis role="strong">zipl</emphasis> boot loader is used.</simpara>
+<simpara role="_abstract">MSVSphere uses GRand Unified Bootloader version 2 (<emphasis role="strong"><phrase role="application">GRUB2</phrase></emphasis>) as the boot loader for AMD64 and Intel 64, IBM Power Systems, and ARM. For 64-bit IBM Z, the <emphasis role="strong">zipl</emphasis> boot loader is used.</simpara>
<simpara>The boot loader is the first program that runs when the system starts and is responsible for loading and transferring control to an operating system. <emphasis role="strong"><phrase role="application">GRUB2</phrase></emphasis> can boot any compatible operating system (including Microsoft Windows) and can also use chain loading to transfer control to other boot loaders for unsupported operating systems.</simpara>
<warning>
<simpara>Installing <emphasis role="strong"><phrase role="application">GRUB2</phrase></emphasis> may overwrite your existing boot loader.</simpara>
@ -229,38 +261,65 @@ index 28ee770..87c0fc1 100644
<orderedlist numeration="arabic">
<title>Procedure</title>
<listitem>
@@ -358,7 +358,7 @@ If you choose to partition your system automatically, you should manually edit y
</orderedlist>
@@ -377,9 +366,6 @@ If you choose to partition your system automatically, you should manually edit y
</listitem>
<listitem>
-<simpara>Click <guibutton>Done</guibutton> to apply the settings and return to <citetitle>Installing and deploying RHEL</citetitle> on the Red Hat Customer Portal.</simpara>
+<simpara>Click <guibutton>Done</guibutton> to apply the settings and return to <citetitle>Installing and deploying MSVSphere</citetitle>.</simpara>
</orderedlist>
</listitem>
-<listitem>
-<simpara>Click <guibutton>Done</guibutton> to apply the settings and return to <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#graphical-installation_graphical-installation">Graphical installations</link>.</simpara>
-</listitem>
</orderedlist>
<note>
@@ -384,7 +384,7 @@ If you choose to partition your system automatically, you should manually edit y
<simpara>The amount of memory that you reserve is determined by your system architecture (AMD64 and Intel 64 have different requirements than IBM Power) as well as the total amount of system memory. In most cases, automatic reservation is satisfactory.</simpara>
@@ -404,7 +390,7 @@ If you choose to partition your system automatically, you should manually edit y
<note>
<itemizedlist>
<listitem>
-<simpara>There are several types of network device naming standards used to identify network devices with persistent names, for example, <literal>em1</literal> and <literal>wl3sp0</literal>. For information about these standards, see the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_and_managing_networking/index/"><emphasis>Configuring and managing networking</emphasis></link> document.</simpara>
-<simpara>There are several types of network device naming standards used to identify network devices with persistent names, for example, <literal>em1</literal> and <literal>wl3sp0</literal>. For information about these standards, see the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/configuring_and_managing_networking/index/"><emphasis>Configuring and managing networking</emphasis></link> document.</simpara>
+<simpara>There are several types of network device naming standards used to identify network devices with persistent names, for example, <literal>em1</literal> and <literal>wl3sp0</literal>.</simpara>
</listitem>
</itemizedlist>
</note>
@@ -493,7 +493,7 @@ If you choose to partition your system automatically, you should manually edit y
@@ -432,7 +418,7 @@ If you choose to partition your system automatically, you should manually edit y
<simpara>The host name can either be a fully qualified domain name (FQDN) in the format <literal><emphasis>hostname.domainname</emphasis></literal>, or a short host name without the domain. Many networks have a Dynamic Host Configuration Protocol (DHCP) service that automatically supplies connected systems with a domain name. To allow the DHCP service to assign the domain name to this system, specify only the short host name.</simpara>
</listitem>
<listitem>
-<simpara>When using static IP and host name configuration, it depends on the planned system use case whether to use a short name or FQDN. Red Hat Identity Management configures FQDN during provisioning but some 3rd party software products may require short name. In either case, to ensure availability of both forms in all situations, add an entry for the host in <literal>/etc/hosts`</literal> in the format <literal>IP FQDN short-alias</literal>.</simpara>
+<simpara>When using static IP and host name configuration, it depends on the planned system use case whether to use a short name or FQDN. MSVSphere Identity Management configures FQDN during provisioning but some 3rd party software products may require short name. In either case, to ensure availability of both forms in all situations, add an entry for the host in <literal>/etc/hosts`</literal> in the format <literal>IP FQDN short-alias</literal>.</simpara>
</listitem>
<listitem>
<simpara>The value <literal>localhost</literal> means that no specific static host name for the target system is configured, and the actual host name of the installed system is configured during the processing of the network configuration, for example, by NetworkManager using DHCP or DNS.</simpara>
@@ -471,7 +457,7 @@ If you choose to partition your system automatically, you should manually edit y
</listitem>
<listitem>
<simpara><emphasis role="strong">Team</emphasis>: NIC Teaming, a new implementation to aggregate links, designed to provide a small kernel driver to implement the fast handling of packet flows, and various applications to do everything else in user space.</simpara>
-<simpara>Network teaming is deprecated in Red Hat Enterprise Linux 9. Consider using the network bonding driver as an alternative. For details, see <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_and_managing_networking/configuring-network-bonding_configuring-and-managing-networking">Configuring network bonding</link>.</simpara>
+<simpara>Network teaming is deprecated in MSVSphere 9. Consider using the network bonding driver as an alternative.</simpara>
</listitem>
<listitem>
<simpara><emphasis role="strong">Vlan</emphasis> (<emphasis>Virtual LAN</emphasis>): A method to create multiple distinct broadcast domains which are mutually isolated.</simpara>
@@ -481,7 +467,6 @@ If you choose to partition your system automatically, you should manually edit y
</listitem>
<listitem>
<simpara>Select the interface type and click <guibutton>Add</guibutton>. An editing interface dialog box opens, allowing you to edit any available settings for your chosen interface type.</simpara>
-<simpara>For more information see <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#editing-network-interface-configuration_network-hostname">Editing network interface</link>.</simpara>
</listitem>
<listitem>
<simpara>Click <guibutton>Save</guibutton> to confirm the virtual interface settings and return to the <emphasis role="strong">Network & Host name</emphasis> window.</simpara>
@@ -521,7 +506,7 @@ If you choose to partition your system automatically, you should manually edit y
<important>
<itemizedlist>
<listitem>
-<simpara>When enabled on a wired connection, the system automatically connects during startup or reboot. On a wireless connection, the interface attempts to connect to any known wireless networks in range. For further information about NetworkManager, including the <literal>nm-connection-editor</literal> tool, see the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_and_managing_networking/index?lb_target=production"><emphasis>Configuring and managing networking</emphasis></link> document.</simpara>
+<simpara>When enabled on a wired connection, the system automatically connects during startup or reboot. On a wireless connection, the interface attempts to connect to any known wireless networks in range. For further information about NetworkManager, including the <literal>nm-connection-editor</literal> tool.</simpara>
-<simpara>When enabled on a wired connection, the system automatically connects during startup or reboot. On a wireless connection, the interface attempts to connect to any known wireless networks in range. For further information about NetworkManager, including the <literal>nm-connection-editor</literal> tool, see the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/configuring_and_managing_networking/index?lb_target=production"><emphasis>Configuring and managing networking</emphasis></link> document.</simpara>
+<simpara>When enabled on a wired connection, the system automatically connects during startup or reboot. On a wireless connection, the interface attempts to connect to any known wireless networks in range.</simpara>
</listitem>
<listitem>
<simpara>You can enable or disable all users on the system from connecting to this network using the <emphasis role="strong">All users may connect to this network</emphasis> option. If you disable this option, only <literal role="systemitem">root</literal> will be able to connect to this network.</simpara>
@@ -569,365 +569,17 @@ If you choose to partition your system automatically, you should manually edit y
@@ -597,373 +582,17 @@ If you choose to partition your system automatically, you should manually edit y
<title>Additional resources</title>
<itemizedlist>
<listitem>
-<simpara>To learn more about network configuration after installation, see the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_and_managing_networking/index/"><emphasis>Configuring and managing networking</emphasis></link> document.</simpara>
-<simpara><link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/configuring_and_managing_networking/index/"><emphasis>Configuring and managing networking</emphasis></link></simpara>
-<simpara>System Purpose is an optional but recommended feature of the Red Hat Enterprise Linux installation. You use System Purpose to record the intended use of a Red Hat Enterprise Linux 9 system, and ensure that the entitlement server auto-attaches the most appropriate subscription to your system.</simpara>
-<simpara role="_abstract">System Purpose is an optional but recommended feature of the Red Hat Enterprise Linux installation. You use System Purpose to record the intended use of a Red Hat Enterprise Linux 9 system, and ensure that the entitlement server auto-attaches the most appropriate subscription to your system.</simpara>
-<simpara>Benefits include:</simpara>
-<itemizedlist>
-<listitem>
@ -306,6 +365,9 @@ index 28ee770..87c0fc1 100644
-<listitem>
-<simpara>During a Kickstart installation when using Kickstart automation scripts</simpara>
-</listitem>
-<listitem>
-<simpara>After installation using the <literal>subscription-manager syspurpose</literal> command-line (CLI) tool</simpara>
-</listitem>
-</itemizedlist>
-<simpara>To record the intended purpose of your system, you can configure the following components of System Purpose. The selected values are used by the entitlement server upon registration to attach the most suitable subscription for your system.</simpara>
-<itemizedlist>
@ -352,22 +414,22 @@ index 28ee770..87c0fc1 100644
-</itemizedlist>
-</listitem>
-</itemizedlist>
-<itemizedlist>
-<itemizedlist role="_additional-resources">
-<title>Additional resources</title>
-<listitem>
-<simpara>For more information about Image Builder, see the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/composing_a_customized_rhel_system_image/index/"><emphasis>Composing a customized RHEL system image</emphasis></link> document.</simpara>
-<simpara><link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/composing_a_customized_rhel_system_image/index/">Composing a customized RHEL system image</link></simpara>
-</listitem>
-<listitem>
-<simpara>For more information about Kickstart, see the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/performing_an_advanced_rhel_installation/index/"><emphasis>Performing an advanced RHEL installation</emphasis></link> document.</simpara>
-<simpara><link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_an_advanced_rhel_9_installation/index/">Performing an advanced RHEL 9 installation</link></simpara>
-</listitem>
-<listitem>
-<simpara>For more information about Subscription Manager, see the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_subscription_management/1/html-single/rhsm/index/"><emphasis>Using and Configuring Red Hat Subscription Manager</emphasis></link> document.</simpara>
-<simpara><link xl:href="https://access.redhat.com/documentation/en-us/red_hat_subscription_management/1/html-single/rhsm/index/">Using and Configuring Red Hat Subscription Manager</link></simpara>
-<title>Configuring Connect to Red Hat options</title>
-<simpara>Use the following procedure to configure the Connect to Red Hat options in the GUI.</simpara>
-<simpara role="_abstract">Use the following procedure to configure the Connect to Red Hat options in the GUI.</simpara>
-<note>
-<simpara>You can register to the CDN using either your Red Hat account or your activation key details.</simpara>
-</note>
@ -410,11 +472,14 @@ index 28ee770..87c0fc1 100644
-<simpara>Select the <emphasis role="strong">Use HTTP proxy</emphasis> check box if your network environment only allows external Internet access or access to content servers through an HTTP proxy. Clear the <emphasis role="strong">Use HTTP proxy</emphasis> check box if an HTTP proxy is not used.</simpara>
-</listitem>
-<listitem>
-<simpara>If you are running Satellite Server or performing internal testing, select the <emphasis role="strong">Custom server URL</emphasis> and <emphasis role="strong">Custom base URL</emphasis> check boxes and enter the required details.</simpara>
-<simpara>If you are running Satellite Server or performing internal testing, select the <emphasis role="strong">Satellite URL</emphasis> and <emphasis role="strong">Custom base URL</emphasis> check boxes and enter the required details.</simpara>
-<important>
-<itemizedlist>
-<listitem>
-<simpara>The <emphasis role="strong">Custom server URL</emphasis> field does not require the HTTP protocol, for example <literal>nameofhost.com</literal>. However, the <emphasis role="strong">Custom base URL</emphasis> field requires the HTTP protocol.</simpara>
-<simpara>RHEL 9 is supported only with Satellite 6.11 or later. Check the version prior attempting to register the system.</simpara>
-</listitem>
-<listitem>
-<simpara>The <emphasis role="strong">Satellite URL</emphasis> field does not require the HTTP protocol, for example <literal>nameofhost.com</literal>. However, the <emphasis role="strong">Custom base URL</emphasis> field requires the HTTP protocol.</simpara>
-</listitem>
-<listitem>
-<simpara>To change the <emphasis role="strong">Custom base URL</emphasis> after registration, you must unregister, provide the new details, and then re-register.</simpara>
-<title>Verifying your system registration from the CDN</title>
-<simpara>Use this procedure to verify that your system is registered to the CDN using the GUI.</simpara>
-<simpara role="_abstract">Use this procedure to verify that your system is registered to the CDN using the GUI.</simpara>
-<warning>
-<simpara>You can only verify your registration from the CDN if you have <emphasis role="strong">not</emphasis> clicked the <emphasis role="strong">Begin Installation</emphasis> button from the <emphasis role="strong">Installation Summary</emphasis> window. Once the <emphasis role="strong">Begin Installation</emphasis> button is clicked, you cannot return to the Installation Summary window to verify your registration.</simpara>
-</warning>
-<itemizedlist>
-<title>Prerequisite</title>
-<listitem>
-<simpara>You have completed the registration process as documented in the <citetitle>Installing and deploying RHEL</citetitle> on the Red Hat Customer Portal and <emphasis>Registered</emphasis> is displayed under <emphasis role="strong">Connect to Red Hat</emphasis> on the <emphasis role="strong">Installation Summary</emphasis> window.</simpara>
-<simpara>You have completed the registration process as documented in the <link linkend="register-and-install-from-cdn-using-gui_register-and-install-from-cdn">Register and install from CDN using GUI</link> and <emphasis>Registered</emphasis> is displayed under <emphasis role="strong">Connect to Red Hat</emphasis> on the <emphasis role="strong">Installation Summary</emphasis> window.</simpara>
-</listitem>
-</itemizedlist>
-<orderedlist numeration="arabic">
@ -521,13 +586,13 @@ index 28ee770..87c0fc1 100644
-<title>Unregistering your system from the CDN</title>
-<simpara>Use this procedure to unregister your system from the CDN using the GUI.</simpara>
-<simpara role="_abstract">Use this procedure to unregister your system from the CDN using the GUI.</simpara>
-<warning>
-<itemizedlist>
-<listitem>
@ -549,7 +614,7 @@ index 28ee770..87c0fc1 100644
-<itemizedlist>
-<title>Prerequisite</title>
-<listitem>
-<simpara>You have completed the registration process as documented in the <citetitle>Installing and deploying RHEL</citetitle> on the Red Hat Customer Portal and <emphasis>Registered</emphasis> is displayed under <emphasis role="strong">Connect to Red Hat</emphasis> on the <emphasis role="strong">Installation Summary</emphasis> window.</simpara>
-<simpara>You have completed the registration process as documented in the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#register-and-install-from-cdn-using-gui_register-and-install-from-cdn">Registering and installing RHEL from the CDN</link> and <emphasis>Registered</emphasis> is displayed under <emphasis role="strong">Connect to Red Hat</emphasis> on the <emphasis role="strong">Installation Summary</emphasis> window.</simpara>
-</listitem>
-</itemizedlist>
-<orderedlist numeration="arabic">
@ -599,8 +664,10 @@ index 28ee770..87c0fc1 100644
-<note>
-<simpara>After unregistering, it is possible to register your system again. Click <emphasis role="strong">Connect to Red Hat</emphasis>. The previously entered details are populated. Edit the original details, or update the fields based on the account, purpose, and connection. Click <guibutton>Register</guibutton> to complete.</simpara>
-<simpara>For information about Red Hat Insights, see the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_insights/"><emphasis>Red Hat Insights product documentation</emphasis></link>.</simpara>
-</listitem>
@ -615,48 +682,58 @@ index 28ee770..87c0fc1 100644
-<simpara>This section contains information about the Red Hat Enterprise Linux 9 security policy and how to configure it for use on your system.</simpara>
+<simpara>This section contains information about the MSVSphere 9 security policy and how to configure it for use on your system.</simpara>
<title>Installing System Aligned with a Security Policy</title>
-<simpara>This section contains information about applying Red Hat Enterprise Linux 9 security policy during installation and how to configure it for use on your system before the first boot.</simpara>
+<simpara>This section contains information about applying MSVSphere 9 security policy during installation and how to configure it for use on your system before the first boot.</simpara>
-<simpara>The Red Hat Enterprise Linux security policy adheres to restrictions and recommendations (compliance policies) defined by the Security Content Automation Protocol (SCAP) standard. The packages are automatically installed. However, by default, no policies are enforced and therefore no checks are performed during or after installation unless specifically configured.</simpara>
+<simpara>The MSVSphere security policy adheres to restrictions and recommendations (compliance policies) defined by the Security Content Automation Protocol (SCAP) standard. The packages are automatically installed. However, by default, no policies are enforced and therefore no checks are performed during or after installation unless specifically configured.</simpara>
<simpara>Applying a security policy is not a mandatory feature of the installation program. If you apply a security policy to the system, it is installed using restrictions and recommendations defined in the profile that you selected. The <emphasis role="strong"><phrase role="package">openscap-scanner</phrase></emphasis> package is added to your package selection, providing a preinstalled tool for compliance and vulnerability scanning. After the installation finishes, the system is automatically scanned to verify compliance. The results of this scan are saved to the <literal>/root/openscap_data</literal> directory on the installed system. You can also load additional profiles from an HTTP, HTTPS, or FTP server.</simpara>
@@ -981,9 +633,6 @@ A separate window opens allowing you to enter a URL for valid security content.<
-<simpara role="_abstract">The Red Hat Enterprise Linux includes OpenSCAP suite to enable automated configuration of the system in alignment with a particular security policy. The policy is implemented using the Security Content Automation Protocol (SCAP) standard. The packages are available in the AppStream repository. However, by default, the installation and post-installation process does not enforce any policies and therefore does not involve any checks unless specifically configured.</simpara>
+<simpara role="_abstract">The MSVSphere includes OpenSCAP suite to enable automated configuration of the system in alignment with a particular security policy. The policy is implemented using the Security Content Automation Protocol (SCAP) standard. The packages are available in the AppStream repository. However, by default, the installation and post-installation process does not enforce any policies and therefore does not involve any checks unless specifically configured.</simpara>
<simpara>Applying a security policy is not a mandatory feature of the installation program. If you apply a security policy to the system, it is installed using restrictions and recommendations defined in the profile that you selected. The <literal role="package">openscap-scanner</literal> and <literal role="package">scap-security-guide</literal> packages are added to your package selection, providing a preinstalled tool for compliance and vulnerability scanning.</simpara>
<simpara>When you select a security policy, the Anaconda GUI installer requires the configuration to adhere to the policy’s requirements. There might be conflicting package selections, as well as separate partitions defined. Only after all the requirements are met, you can start the installation.</simpara>
<simpara>At the end of the installation process, the selected OPenSCAP security policy automatically hardens the system and scans it to verify compliance, saving the scan results to the <literal>/root/openscap_data</literal> directory on the installed system.</simpara>
@@ -1019,9 +648,6 @@ A separate window opens allowing you to enter a URL for valid security content.<
<listitem>
<simpara><literal role="literal">scap-security-guide(8)</literal> - The manual page for the <literal role="literal">scap-security-guide</literal> project contains information about SCAP security profiles, including examples on how to utilize the provided benchmarks using the OpenSCAP utility.</simpara>
</listitem>
-<listitem>
-<simpara>Red Hat Enterprise Linux security compliance information is available in the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/security_hardening/index/"><emphasis>Security hardening</emphasis></link> document.</simpara>
-<simpara>Red Hat Enterprise Linux security compliance information is available in the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/security_hardening/index/"><emphasis>Security hardening</emphasis></link> document.</simpara>
-</listitem>
</itemizedlist>
</section>
</section>
@@ -993,9 +642,9 @@ A separate window opens allowing you to enter a URL for valid security content.<
@@ -1031,17 +657,17 @@ A separate window opens allowing you to enter a URL for valid security content.<
<simpara>This section contains information about configuring your installation source and software selection settings, and activating a repository.</simpara>
-<simpara>Complete the steps in this procedure to configure an installation source from either auto-detected installation media, Red Hat CDN, or the network.</simpara>
+<simpara>Complete the steps in this procedure to configure an installation source from either auto-detected installation media or the network.</simpara>
-<simpara role="_abstract">Complete the steps in this procedure to configure an installation source from either auto-detected installation media, Red Hat CDN, or the network.</simpara>
+<simpara role="_abstract">Complete the steps in this procedure to configure an installation source from either auto-detected installation media or the network.</simpara>
<note>
-<simpara>When the <emphasis role="strong">Installation Summary</emphasis> window first opens, the installation program attempts to configure an installation source based on the type of media that was used to boot the system. The full Red Hat Enterprise Linux Server DVD configures the source as local media.</simpara>
+<simpara>When the <emphasis role="strong">Installation Summary</emphasis> window first opens, the installation program attempts to configure an installation source based on the type of media that was used to boot the system. The full MSVSphere Server DVD configures the source as local media.</simpara>
</note>
<itemizedlist>
<title>Prerequisites</title>
@@ -1028,7 +677,7 @@ A separate window opens allowing you to enter a URL for valid security content.<
<listitem>
-<simpara>You have downloaded the full installation image. <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#downloading-beta-installation-images_installing-RHEL">Downloading a RHEL installation ISO image</link></simpara>
+<simpara>You have downloaded the full installation image.</simpara>
</listitem>
<listitem>
-<simpara>You have created a bootable physical media. <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#making-an-installation-cd-or-dvd_assembly_creating-a-bootable-installation-medium">Creating a bootable CD or DVD</link></simpara>
+<simpara>You have created a bootable physical media.</simpara>
</listitem>
<listitem>
<simpara>The <emphasis role="strong">Installation Summary</emphasis> window is open.</simpara>
@@ -1066,7 +692,7 @@ A separate window opens allowing you to enter a URL for valid security content.<
<simpara><emphasis role="strong">No additional configuration is necessary as the BaseOS and AppStream repositories are installed as part of the full installation image.</emphasis></simpara>
</listitem>
<listitem>
-<simpara><emphasis role="strong">Do not disable the AppStream repository check box if you want a full Red Hat Enterprise Linux9 installation.</emphasis></simpara>
-<simpara><emphasis role="strong">Do not disable the AppStream repository check box if you want a full Red Hat Enterprise Linux9 installation.</emphasis></simpara>
+<simpara><emphasis role="strong">Do not disable the AppStream repository check box if you want a full MSVSphere 9 installation.</emphasis></simpara>
</listitem>
</itemizedlist>
</important>
@@ -1036,9 +685,6 @@ A separate window opens allowing you to enter a URL for valid security content.<
@@ -1074,18 +700,9 @@ A separate window opens allowing you to enter a URL for valid security content.<
</orderedlist>
</listitem>
<listitem>
@ -666,43 +743,57 @@ index 28ee770..87c0fc1 100644
<simpara>Optional: Select the <emphasis role="strong">On the network</emphasis> option to download and install packages from a network location instead of local media.</simpara>
<note>
<itemizedlist>
@@ -1116,15 +762,14 @@ A separate window opens allowing you to enter a URL for valid security content.<
-<listitem>
-<simpara>If you do not want to download and install additional repositories from a network location, proceed to <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#configuring-software-selection_configuring-software-settings">Configuring software selection</link>.</simpara>
-</listitem>
-<listitem>
-<simpara>This option is available only when a network connection is active. See <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#network-hostname_configuring-system-settings">Configuring network and host name options</link> for information about how to configure network connections in the GUI.</simpara>
-</listitem>
</itemizedlist>
</note>
<orderedlist numeration="loweralpha">
@@ -1154,18 +771,17 @@ A separate window opens allowing you to enter a URL for valid security content.<
</listitem>
</itemizedlist>
<simpara>Use a predefined environment and additional software to customize your system. However, in a standard installation, you cannot select individual packages to install. To view the packages contained in a specific environment, see the <literal role="filename"><emphasis>repository</emphasis>/repodata/*-comps-<emphasis>repository</emphasis>.<emphasis>architecture</emphasis>.xml</literal> file on your installation source media (DVD, CD, USB). The XML file contains details of the packages installed as part of a base environment. Available environments are marked by the <literal><environment></literal> tag, and additional software packages are marked by the <literal><group></literal> tag.</simpara>
-<simpara>If you are unsure about which packages to install, Red Hat recommends that you select the <emphasis role="strong">Minimal Install</emphasis> base environment. Minimal install installs a basic version of Red Hat Enterprise Linux with only a minimal amount of additional software. After the system finishes installing and you log in for the first time, you can use the <emphasis role="strong">Yum package manager</emphasis> to install additional software.
-For more information about Yum package manager, see the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_basic_system_settings/index/"><emphasis>Configuring basic system settings</emphasis></link> document.</simpara>
+<simpara>If you are unsure about which packages to install, MSVSphere recommends that you select the <emphasis role="strong">Minimal Install</emphasis> base environment. Minimal install installs a basic version of MSVSphere with only a minimal amount of additional software. After the system finishes installing and you log in for the first time, you can use the <emphasis role="strong">Yum package manager</emphasis> to install additional software.</simpara>
-<simpara>If you are unsure about which packages to install, Red Hat recommends that you select the <emphasis role="strong">Minimal Install</emphasis> base environment. Minimal install installs a basic version of Red Hat Enterprise Linux with only a minimal amount of additional software. After the system finishes installing and you log in for the first time, you can use the <emphasis role="strong">DNF package manager</emphasis> to install additional software.
-For more information about DNF package manager, see the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/configuring_basic_system_settings/index/"><emphasis>Configuring basic system settings</emphasis></link> document.</simpara>
+<simpara>If you are unsure about which packages to install, MSVSphere recommends that you select the <emphasis role="strong">Minimal Install</emphasis> base environment. Minimal install installs a basic version of MSVSphere with only a minimal amount of additional software. After the system finishes installing and you log in for the first time, you can use the <emphasis role="strong">DNF package manager</emphasis> to install additional software.</simpara>
<note>
<itemizedlist>
<listitem>
-<simpara>The <literal>yum group list</literal> command lists all package groups from yum repositories. See the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_basic_system_settings/index/"><emphasis>Configuring basic system settings</emphasis></link> document for more information.</simpara>
+<simpara>The <literal>yum group list</literal> command lists all package groups from yum repositories.</simpara>
-<simpara>The <literal>dnf group list</literal> command lists all package groups from dnf repositories. See the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/configuring_basic_system_settings/index/"><emphasis>Configuring basic system settings</emphasis></link> document for more information.</simpara>
+<simpara>The <literal>dnf group list</literal> command lists all package groups from dnf repositories.</simpara>
</listitem>
<listitem>
-<simpara>If you need to control which packages are installed, you can use a Kickstart file and define the packages in the <literal>%packages</literal> section. See the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/performing_an_advanced_rhel_installation/index/"><emphasis>Performing an advanced RHEL installation</emphasis></link> document for information about installing Red Hat Enterprise Linux using Kickstart.</simpara>
-<simpara>If you need to control which packages are installed, you can use a Kickstart file and define the packages in the <literal>%packages</literal> section. See the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_an_advanced_rhel_9_installation/index/"><emphasis>Performing an advanced RHEL 9 installation</emphasis></link> document for information about installing Red Hat Enterprise Linux using Kickstart.</simpara>
+<simpara>If you need to control which packages are installed, you can use a Kickstart file and define the packages in the <literal>%packages</literal> section.</simpara>
</listitem>
</itemizedlist>
</note>
@@ -1155,14 +800,14 @@ For more information about Yum package manager, see the <link xl:href="https://a
<simpara>From the <emphasis role="strong">Additional Software for Selected Environment</emphasis> pane, select one or more options.</simpara>
</listitem>
<listitem>
-<simpara>Click <guibutton>Done</guibutton> to apply the settings and return to <citetitle>Installing and deploying RHEL</citetitle> on the Red Hat Customer Portal.</simpara>
+<simpara>Click <guibutton>Done</guibutton> to apply the settings and return to <citetitle>Installing and deploying MSVSphere</citetitle>.</simpara>
-<simpara>By default, RHEL 9 does not install the TuneD package. You can manually install the TuneD package using the <literal>dnf install tuned</literal> command.</simpara>
+<simpara>By default, MSVSphere 9 does not install the TuneD package. You can manually install the TuneD package using the <literal>dnf install tuned</literal> command.</simpara>
</listitem>
</orderedlist>
</section>
</itemizedlist>
</note>
@@ -1203,7 +819,7 @@ For more information about DNF package manager, see the <link xl:href="https://a
-<simpara>You can install Red Hat Enterprise Linux on a large variety of storage devices. You can configure basic, locally accessible, storage devices in the <emphasis role="strong">Installation Destination</emphasis> window. Basic storage devices directly connected to the local system, such as hard disk drives and solid-state drives, are displayed in the <emphasis role="strong">Local Standard Disks</emphasis> section of the window.
+<simpara>You can install MSVSphere on a large variety of storage devices. You can configure basic, locally accessible, storage devices in the <emphasis role="strong">Installation Destination</emphasis> window. Basic storage devices directly connected to the local system, such as hard disk drives and solid-state drives, are displayed in the <emphasis role="strong">Local Standard Disks</emphasis> section of the window.
On IBM Z, this section contains activated Direct Access Storage Devices (DASDs).</simpara>
On 64-bit IBM Z, this section contains activated Direct Access Storage Devices (DASDs).</simpara>
<warning>
<simpara>A known issue prevents DASDs configured as HyperPAV aliases from being automatically attached to the system after the installation is complete. These storage devices are available during the installation, but are not immediately accessible after you finish installing and reboot. To attach HyperPAV alias devices, add them manually to the <literal>/etc/dasd.conf</literal> configuration file of the system.</simpara>
@@ -1399,10 +1044,10 @@ If discovery succeeds, the <literal>Add iSCSI Storage Target</literal> window di
@@ -1413,7 +1029,7 @@ If discovery succeeds, the <literal>Add iSCSI Storage Target</literal> window di
<simpara>Type the 4 digit hexadecimal device number in the <emphasis role="strong">Device number</emphasis> field.</simpara>
</listitem>
<listitem>
-<simpara>When installing RHEL-9.0 or older releases or if the <literal>zFCP</literal> device is not configured in NPIV mode, or when <literal>auto LUN</literal> scanning is disabled by the <literal>zfcp.allow_lun_scan=0</literal> kernel module parameter, provide the following values:</simpara>
+<simpara>When installing MSVSphere 9 or older releases or if the <literal>zFCP</literal> device is not configured in NPIV mode, or when <literal>auto LUN</literal> scanning is disabled by the <literal>zfcp.allow_lun_scan=0</literal> kernel module parameter, provide the following values:</simpara>
<orderedlist numeration="loweralpha">
<listitem>
<simpara>Type the 16 digit hexadecimal World Wide Port Number (WWPN) in the <emphasis role="strong">WWPN</emphasis> field.</simpara>
@@ -1445,10 +1061,10 @@ If discovery succeeds, the <literal>Add iSCSI Storage Target</literal> window di
@ -710,35 +801,36 @@ index 28ee770..87c0fc1 100644
+<simpara>Non-Volatile Dual In-line Memory Module (NVDIMM) devices combine the performance of RAM with disk-like data persistence when no power is supplied. Under specific circumstances, MSVSphere 9 can boot and run from NVDIMM devices.</simpara>
<title>Criteria for using an NVDIMM device as an installation target</title>
-<simpara>You can install Red Hat Enterprise Linux 9 to Non-Volatile Dual In-line Memory Module (NVDIMM) devices in sector mode on the Intel 64 and AMD64 architectures, supported by the <emphasis role="strong">nd_pmem</emphasis> driver.</simpara>
+<simpara>You can install MSVSphere 9 to Non-Volatile Dual In-line Memory Module (NVDIMM) devices in sector mode on the Intel 64 and AMD64 architectures, supported by the <emphasis role="strong">nd_pmem</emphasis> driver.</simpara>
-<simpara role="_abstract">You can install Red Hat Enterprise Linux 9 to Non-Volatile Dual In-line Memory Module (NVDIMM) devices in sector mode on the Intel 64 and AMD64 architectures, supported by the <emphasis role="strong">nd_pmem</emphasis> driver.</simpara>
+<simpara role="_abstract">You can install MSVSphere 9 to Non-Volatile Dual In-line Memory Module (NVDIMM) devices in sector mode on the Intel 64 and AMD64 architectures, supported by the <emphasis role="strong">nd_pmem</emphasis> driver.</simpara>
<formalpara>
<title>Conditions for using an NVDIMM device as storage</title>
<para>To use an NVDIMM device as storage, the following conditions must be satisfied:</para>
@@ -1440,7 +1085,7 @@ If discovery succeeds, the <literal>Add iSCSI Storage Target</literal> window di
@@ -1486,7 +1102,7 @@ If discovery succeeds, the <literal>Add iSCSI Storage Target</literal> window di
<title>Configuring an NVDIMM device using the graphical installation mode</title>
-<simpara>A Non-Volatile Dual In-line Memory Module (NVDIMM) device must be properly configured for use by Red Hat Enterprise Linux 9 using the graphical installation.</simpara>
+<simpara>A Non-Volatile Dual In-line Memory Module (NVDIMM) device must be properly configured for use by MSVSphere 9 using the graphical installation.</simpara>
-<simpara role="_abstract">A Non-Volatile Dual In-line Memory Module (NVDIMM) device must be properly configured for use by Red Hat Enterprise Linux 9 using the graphical installation.</simpara>
+<simpara role="_abstract">A Non-Volatile Dual In-line Memory Module (NVDIMM) device must be properly configured for use by MSVSphere 9 using the graphical installation.</simpara>
<warning>
<simpara>Reconfiguration of a NVDIMM device process destroys any data stored on the device.</simpara>
</warning>
@@ -1495,11 +1140,11 @@ If discovery succeeds, the <literal>Add iSCSI Storage Target</literal> window di
@@ -1541,11 +1157,11 @@ If discovery succeeds, the <literal>Add iSCSI Storage Target</literal> window di
-<simpara>You can use manual partitioning to configure your disk partitions and mount points and define the file system that Red Hat Enterprise Linux is installed on.</simpara>
+<simpara>You can use manual partitioning to configure your disk partitions and mount points and define the file system that MSVSphere is installed on.</simpara>
<note>
<simpara>Before installation, you should consider whether you want to use partitioned or unpartitioned disk devices. For more information, see the Knowledgebase article at <link xl:href="https://access.redhat.com/solutions/163853">https://access.redhat.com/solutions/163853</link>.</simpara>
-<simpara>Before installation, you should consider whether you want to use partitioned or unpartitioned disk devices. For more information on the advantages and disadvantages to using partitioning on LUNs, either directly or with LVM, see the article at <link xl:href="https://access.redhat.com/solutions/163853">https://access.redhat.com/solutions/163853</link>.</simpara>
+<simpara>Before installation, you should consider whether you want to use partitioned or unpartitioned disk devices.</simpara>
</note>
-<simpara>An installation of Red Hat Enterprise Linux requires a minimum of one partition but Red Hat recommends using at least the following partitions or volumes: <literal>/</literal>, <literal>/home</literal>, <literal>/boot</literal>, and <literal>swap</literal>. You can also create additional partitions and volumes as you require.</simpara>
+<simpara>An installation of MSVSphere requires a minimum of one partition but Red Hat recommends using at least the following partitions or volumes: <literal>/</literal>, <literal>/home</literal>, <literal>/boot</literal>, and <literal>swap</literal>. You can also create additional partitions and volumes as you require.</simpara>
+<simpara>An installation of MSVSphere requires a minimum of one partition but MSVSphere recommends using at least the following partitions or volumes: <literal>/</literal>, <literal>/home</literal>, <literal>/boot</literal>, and <literal>swap</literal>. You can also create additional partitions and volumes as you require.</simpara>
<warning>
<simpara>To prevent data loss it is recommended that you back up your data before proceeding. If you are upgrading or creating a dual-boot system, you should back up any data you want to keep on your storage devices.</simpara>
</warning>
@@ -1562,7 +1207,7 @@ If discovery succeeds, the <literal>Add iSCSI Storage Target</literal> window di
@@ -1608,7 +1224,7 @@ If discovery succeeds, the <literal>Add iSCSI Storage Target</literal> window di
<simpara>The dialog has a check box that you can use to remove all other partitions used by the system to which the deleted partition belongs.</simpara>
</listitem>
<listitem>
@ -747,7 +839,7 @@ index 28ee770..87c0fc1 100644
<simpara>A <literal>/boot</literal> partition, a <literal>/</literal> (root) volume, and a <literal>swap</literal> volume proportionate to the size of the available storage are created and listed in the left pane. These are the recommended file systems for a typical installation, but you can add additional file systems and mount points.</simpara>
</listitem>
</itemizedlist>
@@ -1617,7 +1262,7 @@ If discovery succeeds, the <literal>Add iSCSI Storage Target</literal> window di
@@ -1663,7 +1279,7 @@ If discovery succeeds, the <literal>Add iSCSI Storage Target</literal> window di
<note>
<itemizedlist>
<listitem>
@ -756,31 +848,31 @@ index 28ee770..87c0fc1 100644
</listitem>
<listitem>
<simpara>The <literal>/boot</literal> partition is always located on a standard partition, regardless of the value selected.</simpara>
@@ -1719,23 +1364,23 @@ If discovery succeeds, the <literal>Add iSCSI Storage Target</literal> window di
@@ -1765,23 +1381,23 @@ If discovery succeeds, the <literal>Add iSCSI Storage Target</literal> window di
-<simpara>In a Red Hat Enterprise Linux 9 graphical installation, you can preserve the <literal role="filename">/home</literal> directory that was used on your RHEL 7 system.</simpara>
+<simpara>In a MSVSphere 9 graphical installation, you can preserve the <literal role="filename">/home</literal> directory that was used on your EL 7 system.</simpara>
-<simpara role="_abstract">In a Red Hat Enterprise Linux 9 graphical installation, you can preserve the <literal role="filename">/home</literal> directory that was used on your RHEL 8 system.</simpara>
+<simpara role="_abstract">In a MSVSphere 9 graphical installation, you can preserve the <literal role="filename">/home</literal> directory that was used on your EL 8 system.</simpara>
<warning>
-<simpara>Preserving <literal role="filename">/home</literal> is only possible if the <literal role="filename">/home</literal> directory is located on a separate <literal>/home</literal> partition on your RHEL 7 system.</simpara>
+<simpara>Preserving <literal role="filename">/home</literal> is only possible if the <literal role="filename">/home</literal> directory is located on a separate <literal>/home</literal> partition on your EL 7 system.</simpara>
-<simpara>Preserving <literal role="filename">/home</literal> is only possible if the <literal role="filename">/home</literal> directory is located on a separate <literal>/home</literal> partition on your RHEL 8 system.</simpara>
+<simpara>Preserving <literal role="filename">/home</literal> is only possible if the <literal role="filename">/home</literal> directory is located on a separate <literal>/home</literal> partition on your EL 8 system.</simpara>
</warning>
-<simpara>Preserving the <literal role="filename">/home</literal> directory that includes various configuration settings, makes it possible that the GNOME Shell environment on the new Red Hat Enterprise Linux 9 system is set in the same way as it was on your RHEL 7 system.
-Note that this applies only for users on Red Hat Enterprise Linux 9 with the same user name and ID as on the previous RHEL 7 system.</simpara>
-<simpara>Complete this procedure to preserve the <literal role="filename">/home</literal> directory from your RHEL 7 system.</simpara>
+<simpara>Preserving the <literal role="filename">/home</literal> directory that includes various configuration settings, makes it possible that the GNOME Shell environment on the new MSVSphere 9 system is set in the same way as it was on your EL 7 system.
+Note that this applies only for users on MSVSphere 9 with the same user name and ID as on the previous EL 7 system.</simpara>
+<simpara>Complete this procedure to preserve the <literal role="filename">/home</literal> directory from your EL 7 system.</simpara>
-<simpara>Preserving the <literal role="filename">/home</literal> directory that includes various configuration settings, makes it possible that the GNOME Shell environment on the new Red Hat Enterprise Linux 9 system is set in the same way as it was on your RHEL 8 system.
-Note that this applies only for users on Red Hat Enterprise Linux 9 with the same user name and ID as on the previous RHEL 8 system.</simpara>
-<simpara>Complete this procedure to preserve the <literal role="filename">/home</literal> directory from your RHEL 8 system.</simpara>
+<simpara>Preserving the <literal role="filename">/home</literal> directory that includes various configuration settings, makes it possible that the GNOME Shell environment on the new MSVSphere 9 system is set in the same way as it was on your EL 8 system.
+Note that this applies only for users on MSVSphere 9 with the same user name and ID as on the previous EL 8 system.</simpara>
+<simpara>Complete this procedure to preserve the <literal role="filename">/home</literal> directory from your EL 8 system.</simpara>
<itemizedlist>
<title>Prerequisites</title>
<listitem>
-<simpara>RHEL 7 system is installed on your computer.</simpara>
+<simpara>EL 7 system is installed on your computer.</simpara>
-<simpara>RHEL 8 system is installed on your computer.</simpara>
+<simpara>EL 8 system is installed on your computer.</simpara>
</listitem>
<listitem>
-<simpara>The <literal role="filename">/home</literal> directory is located on a separate <literal>/home</literal> partition on your RHEL 7 system.</simpara>
+<simpara>The <literal role="filename">/home</literal> directory is located on a separate <literal>/home</literal> partition on your EL 7 system.</simpara>
-<simpara>The <literal role="filename">/home</literal> directory is located on a separate <literal>/home</literal> partition on your RHEL 8 system.</simpara>
+<simpara>The <literal role="filename">/home</literal> directory is located on a separate <literal>/home</literal> partition on your EL 8 system.</simpara>
</listitem>
<listitem>
-<simpara>The Red Hat Enterprise Linux 9 <literal>Installation Summary</literal> window is currently displayed.</simpara>
@ -788,50 +880,58 @@ index 28ee770..87c0fc1 100644
</listitem>
</itemizedlist>
<orderedlist numeration="arabic">
@@ -1753,7 +1398,7 @@ Note that this applies only for users on Red Hat Enterprise Linux 9 wi
@@ -1799,7 +1415,7 @@ Note that this applies only for users on Red Hat Enterprise Linux 9 wi
<simpara>Choose the <literal>/home</literal> partition, fill in <literal>/home</literal> under <literal>Mount Point:</literal> and clear the <emphasis role="strong">Reformat</emphasis> check box.</simpara>
</listitem>
<listitem>
-<simpara>Optional: You can also customize various aspects of the <literal>/home</literal> partition required for your Red Hat Enterprise Linux 9 system as described in <xref linkend="customizing-a-partition-or-volume_manual-partitioning"/>. However, to preserve <literal>/home</literal> from your RHEL 7 system, it is necessary to clear the <emphasis role="strong">Reformat</emphasis> check box.</simpara>
+<simpara>Optional: You can also customize various aspects of the <literal>/home</literal> partition required for your MSVSphere 9 system as described in <xref linkend="customizing-a-partition-or-volume_manual-partitioning"/>. However, to preserve <literal>/home</literal> from your EL 7 system, it is necessary to clear the <emphasis role="strong">Reformat</emphasis> check box.</simpara>
-<simpara>. Optional: You can also customize various aspects of the <literal>/home</literal> partition required for your Red Hat Enterprise Linux 9 system as described in <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#customizing-a-partition-or-volume_manual-partitioning">Customizing a mount point file system</link>. However, to preserve <literal>/home</literal> from your RHEL 8 system, it is necessary to clear the <emphasis role="strong">Reformat</emphasis> check box.</simpara>
+<simpara>. Optional: You can also customize various aspects of the <literal>/home</literal> partition required for your MSVSphere 9 system as described in Customizing a mount point file system. However, to preserve <literal>/home</literal> from your EL 8 system, it is necessary to clear the <emphasis role="strong">Reformat</emphasis> check box.</simpara>
</listitem>
<listitem>
<simpara>After you customized all partitions according to your requirements, click <guibutton>Done</guibutton>. The <emphasis role="strong">Summary of changes</emphasis> dialog box opens.</simpara>
@@ -1813,7 +1458,7 @@ Note that this applies only for users on Red Hat Enterprise Linux 9 wi
</listitem>
@@ -1860,9 +1476,6 @@ Note that this applies only for users on Red Hat Enterprise Linux 9 wi
</orderedlist>
<simpara>A message is displayed at the bottom of the window if the specified RAID level requires more disks.</simpara>
-<simpara>To learn more about soft corruption and how you can protect your data when configuring a RAID LV, see <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_and_managing_logical_volumes/index#using-dm-integrity-with-raid-lv_configure-manage-raid">Using DM integrity with RAID LV</link>.</simpara>
+<simpara>To learn more about soft corruption and how you can protect your data when configuring a RAID LV.</simpara>
<itemizedlist role="_additional-resources">
<title>Additional resources</title>
-<listitem>
-<simpara><link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_and_managing_logical_volumes/assembly_configure-mange-raid-configuring-and-managing-logical-volumes#creating-a-raid-lv-with-dm-integrity_configuring-raid-logical-volumes">Creating a RAID LV with DM integrity</link></simpara>
@@ -1832,15 +1477,12 @@ Note that this applies only for users on Red Hat Enterprise Linux 9 wi
@@ -1882,15 +1495,12 @@ Note that this applies only for users on Red Hat Enterprise Linux 9 wi
<listitem>
<simpara>Click the <emphasis role="strong">Device Type</emphasis> drop-down menu and select <literal>LVM</literal>. The <emphasis role="strong">Volume Group</emphasis> drop-down menu is displayed with the newly-created volume group name.</simpara>
<note>
-<simpara>You cannot specify the size of the volume group’s physical extents in the configuration dialog. The size is always set to the default value of 4 MiB. If you want to create a volume group with different physical extents, you must create it manually by switching to an interactive shell and using the <literal role="command">vgcreate</literal> command, or use a Kickstart file with the <literal role="command">volgroup --pesize=<emphasis>size</emphasis></literal> command. See the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/performing_an_advanced_rhel_installation/index/"><emphasis>Performing an advanced RHEL installation</emphasis></link> document for more information about Kickstart.</simpara>
-<simpara>You cannot specify the size of the volume group’s physical extents in the configuration dialog. The size is always set to the default value of 4 MiB. If you want to create a volume group with different physical extents, you must create it manually by switching to an interactive shell and using the <literal role="command">vgcreate</literal> command, or use a Kickstart file with the <literal role="command">volgroup --pesize=<emphasis>size</emphasis></literal> command. See the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_an_advanced_rhel_9_installation/index/"><emphasis>Performing an advanced RHEL 9 installation</emphasis></link> document for more information about Kickstart.</simpara>
+<simpara>You cannot specify the size of the volume group’s physical extents in the configuration dialog. The size is always set to the default value of 4 MiB. If you want to create a volume group with different physical extents, you must create it manually by switching to an interactive shell and using the <literal role="command">vgcreate</literal> command, or use a Kickstart file with the <literal role="command">volgroup --pesize=<emphasis>size</emphasis></literal> command.</simpara>
</note>
</listitem>
</orderedlist>
<itemizedlist>
<itemizedlist role="_additional-resources">
<title>Additional resources</title>
-<listitem>
-<simpara>For more information about LVM, see the <emphasis><link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_and_managing_logical_volumes/index">Configuring and managing logical volumes</link></emphasis> document.</simpara>
-<simpara><link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/configuring_and_managing_logical_volumes/index">Configuring and managing logical volumes</link></simpara>
-<simpara>You cannot specify the size of the volume group’s physical extents in the configuration dialog. The size is always set to the default value of 4 MiB. If you want to create a volume group with different physical extents, you must create it manually by switching to an interactive shell and using the <literal role="command">vgcreate</literal> command, or use a Kickstart file with the <literal role="command">volgroup --pesize=<emphasis>size</emphasis></literal> command. See the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/performing_an_advanced_rhel_installation/index/"><emphasis>Performing an advanced RHEL installation</emphasis></link> document for more information about Kickstart.</simpara>
-<simpara>You cannot specify the size of the volume group’s physical extents in the configuration dialog. The size is always set to the default value of 4 MiB. If you want to create a volume group with different physical extents, you must create it manually by switching to an interactive shell and using the <literal role="command">vgcreate</literal> command, or use a Kickstart file with the <literal role="command">volgroup --pesize=<emphasis>size</emphasis></literal> command. See the <link xl:href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_an_advanced_rhel_9_installation/index/"><emphasis>Performing an advanced RHEL 9 installation</emphasis></link> document for more information about Kickstart.</simpara>
+<simpara>You cannot specify the size of the volume group’s physical extents in the configuration dialog. The size is always set to the default value of 4 MiB. If you want to create a volume group with different physical extents, you must create it manually by switching to an interactive shell and using the <literal role="command">vgcreate</literal> command, or use a Kickstart file with the <literal role="command">volgroup --pesize=<emphasis>size</emphasis></literal> command.</simpara>
</note>
</listitem>
<listitem>
@@ -2098,4 +1708,4 @@ Note that this applies only for users on Red Hat Enterprise Linux 9 wi
