3.3 Installing OES Linux as a New Installation

This section does not provide step-by-step instructions on how to do the installation, but it provides the following important information specific to OES Linux as you progress through the installation.

3.3.1 Starting the OES Linux Installation

Insert Open Enterprise Server SP2 CD1 into the CD-ROM drive of the computer you want to be your OES Linux server, then boot the machine. Then proceed with one of the following:

Network Installation Using DHCP

  1. From the CD boot menu, select the second option (Installation) but do not press Enter.

  2. Press F3, and then select the network installation type (NFS, FTP, HTTP) that you set up on your network installation server.

    See Step 4 of the Preparing for a Network Installation procedure.

  3. Specify the required information (server name and installation path), then select OK.

    When specifying the URL for the installation source path, the URL is the root of the directory where the installation source is created. For example, if you created the installation source under /srv/www/htdocs/oes, the URL would be http://your_server/OES.

    It is possible to specify the complete path to the individual CDs, but this is not necessary.

  4. Press Enter to begin the installation.

  5. Follow the screen prompts using the information contained in Specifying the Type of Installation, Specifying the Installation Settings for the Base OES Linux Installation, Specifying Configuration Information, and Finishing the Installation to complete the installation.

  6. Complete the server setup by following the procedures in Completing Post-Installation Tasks.

Network Installation without DHCP

  1. From the CD boot menu, select the fifth option (Manual Installation), then press Enter.

  2. Select the language, then press Enter.

  3. Select a keyboard map, then press Enter.

  4. Select Start Installation or System, then press Enter.

  5. Select Network, then press Enter.

  6. Select the network protocol that matches the configured protocol on your network installation server, then press Enter.

  7. (Conditional) If you have more than one network interface card, select one of the cards, then press Enter.

    We recommend eth0.

  8. When prompted whether you want to use DHCP, select No, then press Enter.

  9. Specify the IP address, then press Enter.

  10. Specify the subnet mask, then press Enter.

  11. Specify the gateway, then press Enter.

  12. Specify the IP address of a name server, then press Enter.

  13. Specify the IP address or the DNS hostname of the network installation server, then press Enter.

  14. Specify the path to your installation source on the network installation server, then press Enter.

    When specifying the URL for the installation source path, the URL is the root of the directory where the installation source is created. For example, if you created the installation source under /srv/www/htdocs/oes, the URL would be http://your_server/OES.

    It is possible to specify the complete path to the individual CDs, but this is not necessary.

  15. Follow the screen prompts using the information contained in Specifying the Type of Installation, Specifying the Installation Settings for the Base OES Linux Installation, Specifying Configuration Information, and Finishing the Installation to complete the installation.

  16. Complete the server setup by following the procedures in Completing Post-Installation Tasks.

CD Installation

  1. From the CD boot menu, select the second option (Installation), then press Enter.

    The installation process prompts you for each CD at the appropriate time. Disregard the progress status window at the right which uses internal names rather than the CD label names.

  2. Follow the screen prompts using the information contained in Specifying the Type of Installation, Specifying the Installation Settings for the Base OES Linux Installation, Specifying Configuration Information, and Finishing the Installation to complete the installation.

  3. Complete the server setup by following the procedures in Completing Post-Installation Tasks.

3.3.2 Specifying the Type of Installation

When selecting the type of installation, select New Installation.

3.3.3 Specifying the Installation Settings for the Base OES Linux Installation

The instructions in this section assume you are using the graphical YaST interface for installation. If you are installing from a shell prompt or the text-based YaST interface, you need to apply these installation instructions to the interface you are using.

This section does not provide step-by-step instructions on how to do the installation, but it provides important information specific to OES Linux as you progress through the installation and determine the Installation Settings.

For step-by-step information on performing a SLES installation, see Installation in the SUSE LINUX Enterprise Server 9 Administration Guide. The SUSE LINUX Enterprise Server 9 Administration Guide does not contain instructions for OES-specific components.

After selecting the language setting, you are presented with the Installation Settings proposal. You can accept the default settings or customize each setting to fit the needs of your organization. At this stage of the installation, you can change settings for the System, Mode, Keyboard Layout, Mouse, Partitioning, Software, Booting, Time Zone, Language, and Default Runlevel.

This section gives recommendations or procedures for the following tasks:

Setting Up Disk Partitions

In most cases, YaST proposes a reasonable partitioning scheme that can be accepted without change. You can also use YaST to customize the partitioning.

For OES Linux, Novell Storage Services™ (NSS) volumes can only be used as data volumes, not as system volumes. They cannot be created as part of the install process. You must also consider whether you will be creating NSS volumes in the future on the devices where you are installing Linux. The default volume manager for Linux traditional volumes on SUSE Linux is LVM (Linux Volume Manager). However, NSS volumes cannot be created on devices managed by LVM; NSS requires EVMS (Enterprise Volume Management System) management of its devices.

IMPORTANT:If you have only a single device on the server (such as a single physical disk or a hardware RAID 1 or RAID 5 device) and you plan to use NSS volumes as data volumes after the install, make sure to follow the partition configuration instructions in Installing Linux with EVMS as the Volume Manager of the System Device. You can also following this alternate setup if you have multiple devices and want to be able to create NSS volumes in the future on the same device that contains the system partitions.

Table 3-2 presents guidelines for setting up disk partitions on your OES Linux server. For more information, see Partitioning in the SUSE LINUX Enterprise Server 9 Administration Guide.

Table 3-2 Partition Guidelines

Partition to Create

Other Considerations

/boot

Depending on the hardware, it might be useful to create a boot partition (/boot) to hold the boot mechanism and the Linux kernel.

You should create this partition at the start of the disk and make it at least 8 MB or 1 cylinder. As a rule of thumb, always create such a partition if it was included in the YaST original proposal. If you are unsure about this, create a boot partition to be on the safe side.

/swap

Set aside 128 MB to 2 GB for the swap volume.

Swap management is different for Linux kernel 2.4.10 and later. How much swap to add depends on how much RAM there is, the tasks that are planned for the system, and whether you want to make more virtual memory available than the RAM provides.

Some swap (at least 128 MB) is good to have, but swap is not required for systems with more than 1 GB of RAM. You must have at least 1 GB of virtual memory (RAM plus swap) during the install. However, if the swap is more than 2 GB, you might not be able install on many (if not all) machines. A swap larger than 2 GB can degrade performance.

/

Define this partition as 3 GB or more.

/var

Define this partition as 4 GB or more.

/opt

Some (mostly commercial) programs install their data in /opt.

Define this partition as 4 GB or more.

/usr

Define this partition as 4 GB or more.

/home

You can allocate the rest of the disk space to this partition.

Customizing the Software Selections

To customize which software packages are installed on the server:

  1. On the Installation Settings page, click Software.

    Novell Open Enterprise Server is the default predefined server type. If you accept this selection, the OES Base install (similar to SLES Default installation) plus most of the OES components are installed.

    The following OES components are not preselected and installed by default with the Novell Open Enterprise Server predefined server type:

  2. At this point, you can do any of the following:

    • Select one of the other predefined server types.

      OES predefined server types

    • Select one of the other predefined server types, then click Detailed Selections. Then add additional items or remove a preselected item by selecting the check box next to the applicable item in the Selections list.

      Novell Selections in the Software Selections List

    • Click Detailed Selections and add additional items or remove a preselected items by selecting the check box next to the applicable item in the Selections list.

    For a list of OES predefined server types and the components preselected with each type, see Table 2-3.

  3. When you have the software components selected that you want to install, click Next or Accept depending on the actions you performed in Step 2.

  4. (Conditional) If the prompt for Automatic Changes displays, click Continue.

Setting Up the Time Zone

To set your correct region, time zone, date, and time, click Time Zone. You can configure this information after the installation is complete, but it is easier to do it during the installation.

Accepting the Installation Settings

After you have changed all the Installation Settings as desired, click Accept > Yes, install.

For a network install, you can remove the network boot CD (Open Enterprise Server SP2 CD 1) from the CD drive.

For a CD install, leave the CD in the CD-ROM drive.

The base installation settings are applied and the server reboots. Proceed with Specifying Configuration Information.

3.3.4 Specifying Configuration Information

When the server reboots, you are required to complete the following configuration information:

Root Password

After the base installation is complete and your server reboots, the Password for “root,” the system administrator dialog is displayed.

For security reasons, the Root password should be between five and eight characters long and should contain a mixture of both uppercase and lowercase letters and numbers. The maximum length for passwords is 72 characters, and passwords are case sensitive. If you have a password longer than eight characters, click Expert Options > Blowfish > OK.

Network Configuration

Configuration success is directly tied to specific networking configuration requirements. Make sure that the following settings are configured exactly as specified for the Network Interfaces dialogs.

NOTE:If you selected a manual installation and provided previously the following information, you don't need to provide it again. Your network configuration should still be intact. But you still need to set the DNS hostname.

Table 3-3 Network Interfaces Settings

Setting

Recommendation

Steps

IP Address

Use a static IP address for the network card.

By default, the OES Linux installation requires you to configure the network card to use a static IP address.

  1. During the YaST installation, in the Network Configuration panel, click Network Interfaces.

  2. From the Network Cards to Configure list, select the network card you want to configure and then click Configure.

  3. Select Static Address Setup, then specify the IP address and the subnet mask for the server.

Host Name and Domain Name

Specify the hostname and the DNS domain name separately.

  1. From the Detailed Settings list, select Host Name and Name Server.

  2. Specify the information described for the following two fields:

    Host Name: Type only the hostname. Do not include DNS domain information with the hostname.

    For example: Type only mylinuxbox, not mylinuxboxdigitalairlines.com

    Domain Name: Type only the domain name without the hostname.

    For example, type only digitalairlines.com.

Name Servers

Specify one or more name servers.

  1. From the Detailed Settings list, select Host Name and Name Server.

  2. In the Name Servers and Domain Search List panel, specify from one to three DNS server IP addresses and a domain name for each address.

  3. Click OK to return to the Detailed Settings list.

Routing

Specify a default gateway (router).

  1. From the Detailed Settings list, select the Routing option and specify the IP address of the default gateway on the subnet where you are installing the OES Linux server.

  2. Click OK to return to the Detailed Settings list.

When you have completed the options for each of the parameters in Table 3-3 for each of the network boards in the server:

  1. Click Next > Finish to save the network card configuration.

    If you receive any errors regarding invalid hostnames or IP addresses, click Back > Back and fix your network configuration.

    When the network configuration is correct, proceed with Step 2.

  2. Click Next to continue with the configuration.

Test Internet Connection and Online Update

At the Test Internet Connection screen:

  1. Select Yes, Test Connection to the Internet, then click Next.

    Obtaining the latest SUSE release notes might fail at this point. If it does, view the log to verify that the network configuration is correct, then, proceed with Step 2.

    If the network configuration is not correct, click Back > Back and fix your network configuration. See Network Configuration.

    You can get the latest release notes at http://www.suse.com/relnotes/i386/Open-Enterprise-Server/9/release-notes.rpm.

  2. Run the online update to download and install any available updates.

    1. Click Next.

    2. Select Yes, Run Online Update Now.

    3. If the update fails, do the following:

      1. Click OK.

      2. On the Welcome to YaST Online Update screen in the Update Configuration field, click the Installation Source drop-down arrow to select User-Defined Location.

      3. In the Location field, type http://update.novell.com/YOU.

      4. Click Next > Accept.

        The YaST Online Update (YOU) client contacts the YOU server and checks for new patches that are considered mandatory, even those that have already been applied. The YOU client automatically selects the newer patches, downloads them, and applies them.

      5. Click Close.

      6. If this still fails, you can continue with the installation, then update the server later. See Patching an OES Linux Server.

Service Configuration

In the Service Configuration screen, there are two important things to keep in mind:

  • At the CA Management screen, do not skip this configuration.

    The certificate that is created is used by the Apache Web server. If you skip this configuration, each service that uses Apache will not work. The option to run the CA Management configuration is selected by default.

    For more information about Certificate Authority Management, see X.509 Certification with YaST in the SUSE LINUX Enterprise Server 9 Administration Guide.

  • Do not enable OpenLDAP server.

    Because the Novell eDirectory™ LDAP server replaces the SLES 9 OpenLDAP server, you must not select this option. It is deselected by default.

OES Configuration

At the beginning of the OES configuration, you are given the option to Configure Now or Configure Later.

If you select Configure Now (recommended), you are prompted for the configuration information for each OES component you are installing. Common configuration values populate common fields, so you don't have to type them in each time.

If you select Configure Later, you will configure the OES components after the installation is complete. See Installing or Configuring OES Components on an Existing Server.

When confirming the OES component configurations, you might receive the following error:

The proposal contains an error that must be resolved before continuing.

If this error is displayed, check the list of configured products for a message immediately below the product heading that indicates the product needs to be configured. If you are running the YaST graphical interface, the text appears red. If you are installing using the YaST text-base interface, it is not red.

For example, if you have selected iFolder 2 in connection with other OES Web service products, you see a message that iFolder 2 needs to be configured.

You must then assign iFolder an alternate IP address, subnet mask, and hostname for the iFolder service to use. And if you have installed Novell NetStorage™, you should also configure it with the iFolder server IP address.

After resolving all product configuration problems, you can proceed with the install.

Each OES component and the configurable fields associated with it are listed in the following sections. These components also include the default or previously entered values, where applicable. Some components might require some additional configuration as part of the OES installation; this information is also included in the tables. If the component requires configuration that is not part the OES installation, see the component's administration guide for more information. You can find administration guides for all OES products at the OES Documentation Web site .

Keep the following in mind as you configure the OES components:

Table 3-4 Guidelines for Configuring OES Components

Issue

Guideline

Software Selections When Using Text-Based YaST

Some older machines (Dell* 1300) use the text mode install by default when the video card does not meet SLES 9 specifications. When you go into the Software Selection, and then to the details of the OES software selections, YaST doesn’t bring up the OES selections like it does when you use the graphical YaST (YaST2).

To view this screen, select Filter > Selections (or press Alt+F > Alt+I).

Specifying Typeful Admin Names

When installing OES, you must specify a fully distinguished admin name using the typeful syntax that includes object type abbreviations (cn=, ou=, o=, etc.). For example, you might specify the following:

cn=admin.ou=example_organization.o=example_company

Using Dot-Delimited or Comma-Delimited Input for All Products

For all parameters requiring full contexts, you can separate the names using dot-delimited or comma-delimited syntax; however, you must be consistent in your usage within the field. Do not mix dot and comma delimitations.

The OES installation routine displays all input in the dot-delimited (NDAP) format. However, it converts the name separators to commas when this is required by individual product components.

When using NDAP format (periods), you must escape all embedded periods. For example: cn=admin.o=novell\.provo

When using LDAP format (commas), you must escape all embedded commas. For example: cn=admin,o=novell\,provo

IMPORTANT:After the OES components are installed, be sure to follow the conventions specified in the documentation for each product. Some contexts must be specified using periods (.) and others using commas (,). However, eDirectory ™ supports names like cn=juan\.garcia.ou=users.o=novell. The period (.) inside a name component must be escaped.

The installation disallows a backslash and period (\.) in the CN portion of the admin name.

For example, these names are supported:

cn=admin.o=novell
cn=admin.o=novell\.provo
cn=admin.ou=deployment\.linux.o=novell\.provo

These names are not supported:

cn=admin\.first.o=novell
cn=admin\.root.o=novell

Before LUM enabling users whose cn contains a period (.), you must remove the backslash (\) from the unique_id field of the User object container.

For example, cn=juan.garcia has a unique_id attribute = juan\.garcia. Before such a user can be LUM enabled, the backslash (\) must be removed from the unique_id attribute.

After you complete the eDirectory information fields the server configures all of the other selected OES component. A summary screen is displayed showing all the components and their configuration settings. Review the setting for each component and click the component heading to change any settings required. When you are satisfied with the settings for each component, click Next.

The following section lists the specific information required for each component:

Novell eDirectory Configuration

Table 3-5 Novell eDirectory Configuration Parameters and Values

Parameter

Default or Previously Entered Values

New or Existing Tree Name

exampletree

FDN Admin Name with Context

cn=admin.o=example

Server Context

o=example

Directory Information Base (DIB) Location

/var/nds/dib

LDAP Port

389

LDAP Secure Port

636

iMonitor HTTP Port

8028

iMonitor HTTPS Port

8030

Network Time Protocol (NTP) Server

Local Clock

eDirectory Server Port

524

LDAP Server IP Address

Synchronizing Server Time

eDirectory requires that all OES servers, both NetWare and Linux, are time synchronized.

For information on this important topic, see Implementing Time Synchronization in the Novell OES SP2 Planning and Implementation Guide.

SLP Configuration

You have the following options for configuring SLP:

  • Do Not Configure SLP: This option is good for eDirectory trees with three or fewer eDirectory servers.

    Without SLP, users won't be able to see a tree list, but they should still be able to attach to a tree by name. Users can configure the Novell Client to use DNS, or they can configure the local host file (%SystemDrive%\windows\system32\drivers\etc\hosts on WinXP) to resolve tree and server names. Users can also specify preferred tree and context information in the DHCP Settings page of the Novell Client.

  • Use Multicast to Access SLP: This option allows the server to request SLP information using multicast packets. Use this in environments that have not established SLP DAs (Directory Agents).

  • Configure SLP to use an existing Directory Agent: This option configures SLP to use an existing Directory Agent (DA) in your network. Use this in environments that have established SLP DAs. When selecting this option, you configure which servers to use by adding or removing them from the SLP Directory Agent list.

For more information about configuring SLP, see Configuring OpenSLP for eDirectoryNovell eDirectory 8.7.3 Administration Guide.

Novell eGuide

Table 3-6 Novell eGuide Parameters and Values

Parameter

Default or Previously Entered Values

eDirectory Host

frankm.houston.example.com

Admin Name with Context

cn=admin.o=example

eDirectory LDAP Port

389

eDirectory LDAP Secure Port

636
Novell Backup Services (SMS)

Table 3-7 Novell Backup Services Parameters and Values

Parameter

Default or Previously Entered Values

Server Admin Name with Context

cn=admin.o=example

LDAP IP Address

127.0.0.1

LDAP Secure Port

636
Novell Cluster Services

Table 3-8 Novell Cluster Services Parameters and Values

Parameter

Default or Previously Entered Values

New or Existing Cluster

New Cluster

Cluster Name with Context

Node Name

frankm

Node's IP Address

127.0.0.1

Start Clustering

Now

Additional Cluster Services Configuration Information

On the Installation Settings screen, click Cluster Services and do the following:

  1. Select whether you are installing locally or remotely, accept or change the admin name and password, then click Next.

    Locally indicates that you are also installing eDirectory on this server. We recommend that you install eDirectory on cluster nodes. If you are not installing eDirectory on this server, select Remote.

    NOTE:When installing OES Linux clustering into a NetWare 5.1 or NetWare 6 tree, the Local LDAP server option should be used or clustering might fail to install. NetWare 5.1 or NetWare 6 LDAP servers are incompatible with the OES Linux Cluster Services installation.

  2. Choose to either create a new cluster or install Novell Cluster Services™ on a server that you will add to an existing cluster, or configure later.

    Create a New Cluster is the default when installing Novell Cluster Services during the OES installation.

  3. Specify the fully distinguished name (FDN) of the cluster.

    NOTE:Use the dot format illustrated in the example. Do not use commas.

    If you are creating a new cluster, this is the name you will give the new cluster and the eDirectory context where the new Cluster object will reside.

    If you are adding a server to an existing cluster, this is the name and eDirectory context of the cluster that you are adding this server to.

  4. (Conditional) If you are creating a new cluster, specify a unique IP address for the cluster.

    The cluster IP address is separate from the server IP address, is required to be on the same IP subnet as the other cluster servers, and is required for certain external network management programs to get cluster status alerts. The cluster IP address provides a single point for cluster access, configuration, and management. A Master IP Address resource is created automatically during the Cluster Services installation that makes this possible.

    The cluster IP address is bound to the master node and remains with the master node regardless of which server is the master node.

  5. (Conditional) If you chose to install remotely in Step 1, accept the default server name and IP address (recommended), or specify the IP address and server name for server that has eDirectory installed.

  6. (Conditional) If you are creating a new cluster:

    1. Specify the device where you want the SBD partition to be created, then click Next.

      For example, the device might be something similar to /dev/sdc.

      If you have a shared disk system or SAN attached to your cluster servers, Novell Cluster Services creates a small cluster partition on that shared disk system. This small cluster partition is referred to as the Split Brain Detector (SBD) partition. Provide the drive or device where you want the small cluster partition created.

      If you do not have a shared disk system connected to your cluster servers, accept the default (none).

      IMPORTANT:You must have at least 20 MB of free space on one of the shared disk drives to create the cluster partition. If no free space is available, the shared disk drives can't be used by Novell Cluster Services.

    2. Select the IP address clustering should use. If you have multiple network boards installed, you need to select the IP address bound to the desired network board.

    3. Start clustering now indicates if clustering should start now or after the machine is rebooted.

  7. Continue through the rest of the OES installation.

Novell Health Monitoring

Table 3-9 Novell Health Monitoring Parameters and Values

Parameter

Default or Previously Entered Values

LDAP Admin Name with Context

cn=admin.o=example

LDAP IP Address

127.0.0.1

LDAP Secure Port

636
Novell iFolder 2.x

Table 3-10 Novell iFolder 2.x Parameters and Values

Parameter

Default or Previously Entered Values

LDAP Admin Name with Context

cn=admin.o=example

LDAP IP Address

127.0.0.1

LDAP Secure Port

636

iFolder 2.x Server IP Address

iFolder 2.x Server Netmask

iFolder 2.x Server DNS Name

iFolder 2.x User Data Path

/var/opt/novell/ifolderdata

iFolder 2.x Admin Users

 
Novell iFolder 3.x

When you configure iFolder as part of the OES install and configuration, you can specify only an EXT3 or ReiserFS volume location for the System Store Path, which is where you are storing iFolder data for all your users. You cannot create NSS volumes during the system install.

If you want to use an NSS volume to store iFolder data, you must reconfigure iFolder 3.x and 3.x Web Access after the OES install. To reconfigure, use Novell iManager to create an NSS volume, then go to YaST > Network Services and select iFolder 3.x and iFolder 3.x Web Access to enter new information. All previous configuration information is removed and replaced.

Table 3-11 Novell iFolder 3.x Parameters and Values

Parameter

Default or Previously Entered Values

Directory Server Address

Local select by default

Admin Name with Context

cn=admin.o=example

LDAP Port

389

LDAP Secure Port

636

A secure port is recommended when the eDirectory server and iFolder enterprise server are on different computers.

iFolder Admin DN

 

iFolder Admin Password

 

Proxy Context

 

System Name

System Store Path

/var/opt/novell/ifolder3

System Description

Novell iFolder 3.x Web Access

If you plan to reconfigure iFolder 3.x after the OES configuration to use an NSS volume as the System Store Path, make sure you also reconfigure iFolder 3.x Web Access.

Table 3-12 Novell iFolder 3.x Web Access Parameters and Values

Parameter

Default or Previously Entered Values

Web Access Alias

/ifolder

iFolder Server URL

http://localhost

https://IP_address

Specify an HTTPS and an IP address to configure secure SSL exchanges between the Web Access server and the iFolder enterprise server.

Novell iManager

Table 3-13 Novell iManager Parameters and Values

Parameter

Default or Previously Entered Values

eDirectory Tree Name

exampletree

eDirectory Admin with Context

cn=admin.o=example

NOTE:iManager is fully functional from a SUSE Linux server console using Mozilla* 1.7 or Mozilla* Firefox* 1.0 browsers only.

Novell iPrint

Table 3-14 Novell iPrint Parameters and Values

Parameter

Default or Previously Entered Values

iPrint eDirectory tree

exampletree

LDAP IP address

127.0.0.1

LDAP Admin name with context

cn=admin.o=example

LDAP secure port number

636
Novell Linux User Management

Table 3-15 Novell Linux User Management Parameters and Values

Parameter

Default or Previously Entered Values

LDAP Admin Name with Context

cn=admin.o=example

LDAP Server IP Address

127.0.0.1

LDAP Port Number

389

LDAP Secure Port

636

Linux/Unix Config Context

o=example

LUM Workstation Context

o=example

Proxy User Name with Context

PAM-enabled Services to Allow Authentication via eDirectory:

  • login: yes
  • ftp: yes
  • sshd: yes
  • su: yes
  • rsh: yes
  • rlogin: yes
  • passwd: no
  • xdm: yes
  • openwbem: yes

IMPORTANT:Before you accept the default PAM-enabled service settings, be sure you understand the security implications explained in User Restriction Limitations in the Novell OES SP2 Planning and Implementation Guide.
Novell NCP Server

Table 3-16 Novell NCP Server Parameters and Values

Parameter

Default or Previously Entered Values

Admin Name with Context

cn=admin.o=example
Novell NetStorage

Table 3-17 Novell NetStorage Parameters and Values

Parameter

Default or Previously Entered Values

Directory Server Address

frankm.houston.example.com

Admin Name with Context

cn=admin.o=example

LDAP Secure Port

636

iFolder 2 Server Address

Authentication Domain Host

frankm.houston.example.com

Proxy User Name with Context

cn=admin.o=example

User Context

o=example
Novell QuickFinder

Table 3-18 Novell QuickFinder Parameters and Values

Parameter

Default or Previously Entered Values

QuickFinder Admin Name

cn=admin.o=example

LUM Enable QuickFinder Admin User

yes

eDirectory Admin Name

cn=admin.o=example

Add novlwww User to the Shadow Group

yes
Novell Samba

Table 3-19 Novell Samba Parameters and Values

Field or Selection

Default or Previously Entered Values and Comments

Local or Remote Directory Server

Directory Server Address

Required only with remote system selection

Admin Name with Context

cn=admin.o=example

Admin Password

LDAP Port

389

LDAP Secure Port

636

Base Context for Samba Users

o=example

Proxy User Name with Context

cn=admin.o=example

Proxy User Password

Novell Storage Services (NSS)

Table 3-20 Novell Storage Services Parameters and Values

Parameter

Default or Previously Entered Values

LDAP Address

127.0.0.1

LDAP Port

389

LDAP Secure Port

636

Server Admin Name

cn=admin.o=example

NSS Admin Name

cn=serveradmin.o=example

3.3.5 Finishing the Installation

The installation concludes with the following steps:

  1. Cleanup

  2. Release Notes

  3. Device Configuration

After you click Finish, the OES Linux server finishes loading the configured components and reboots.