Upgrading SLES9 to OES Linux

In addition to installing a new OES Linux server, it is possible to upgrade an existing SLES9 server to OES. In order to upgrade a SLES9 server, that server must first meet the following requirements:

• The server must be configured with a static IP address.

• The server name must be properly registered in DNS.

• A server certificate must exist for this server, and this certificate must be exported as a "common server certificate."

• No LDAP daemons can be running on the server. These daemons will conflict with eDirectory and must be disabled.

If the SLES9 server meets these prerequisites, review the "Getting Ready for OES Linux" section earlier in this chapter, and then perform the upgrade to OES by following these steps:

1.	Insert the Open Enterprise Server CD1 in the server's CD-ROM drive and restart the server.
2.	Begin the OES installation by selecting an installation method as documented in step 2 of the "Installing a New OES Linux Server" section earlier in this chapter.
3.	Read through the license agreement. (The English agreement can be found near the bottom of the page.) When finished, select I Agree to begin the installation.
4.	Select the appropriate language for the installation and click Accept.
5.	Select Update an Existing System as the type of installation, and then click OK to continue.
6.	Select the Update Options category to customize the upgrade process to OES Linux.
7.	Select the radio option labeled "Update with Installation of New Software and Features Based on the Selection."
8.	At this point, you have the option of selecting one of the previously described OES installation patterns. Select the desired pattern, such as Novell Open Enterprise Server, then click Accept.
9.	If prompted for confirmation to reset your detailed selection, select Yes.
10.	Click Accept to begin the upgrade process.
11.	Click Yes, Update to acknowledge the warning and begin the file copy process. If you are performing a network-based installation, no intervention is required during the file copy. If you are installing from CD, you will be required to swap CDs when prompted.
12.	At the conclusion of the file copy process, the server will reboot. When the server restarts, the YaST installation process will resume.
13.	Select No to skip the network connectivity test, and then click Next.
14.	After the SuSEconfig process has completed writing the system configuration, click Next after reviewing the release notes and then Finish to exit the upgrade process. After the server has switched to the configured runlevel, OES component customization can be performed through YaST.