2.4.1. Selecting the Custom Installation

1. Select the LDAP directory that you want to use, then click Next. See Table 2-4 for details on LDAP options.

   Figure 2-2. Selecting a Directory Server

   

   Table 2-4. Directory Selection Criteria

   Directory	Explanation
   OpenLDAP	Installed with OpenLinux eServer. This selection completes the configuration and extends the schema of OpenLDAP to include the objects required by Volution Manager.
   eDirectory	Novell NDS eDirectory is included with your distribution of Volution Manager. It must be installed and configured before you install Volution Manager. For installation requirements, see Section 1.1.1.5.2.
   iPlanet	iPlanet is available from Sun Microsystems and Netscape. It must be installed and configured before you install Volution Manager.

   Note: Installation screens and required entries are the same regardless of your LDAP directory choice.

2. Configure your LDAP network settings. See Table 2-5 for details.

   Figure 2-3. Configuring LDAP Network Settings

   

   Table 2-5. LDAP Network Settings

   Setting	Description
   LDAP Server Hostname	Enter the DNS name or IP address of the server where LDAP is installed. For example, ldapservername.yourdomain.com
   Secure Server Port	Enter the port number that LDAP is running on. Port 636 is secure.
   Unsecure Server Port	Enter the port number that LDAP is running on. Port 389 is the standard LDAP port.
   LDAP Naming Context	Enter the top level (or root) of the directory. For example, o=caldera. For information on using LDAP naming conventions, see Table 2-1.

3. Enter the Directory Administrator's name and password information and click Next. See Table 2-6 for details.

   Figure 2-4. LDAP Administrator Options

   

   Table 2-6. Administrator Options for LDAP

   Setting	Description
   Directory Administrator	Enter the user name of the LDAP administrator. Use the LDAP entry format. For example, cn=admin,o=caldera. For information on using LDAP naming conventions, see, Table 2-1.
   Directory Administrator's Password	Enter the administrator's password. Use this password to log in to the VM Management Console.

   You can use the default location for the directory administrator object in your LDAP directory or enter your own location using the LDAP naming conventions.

4. Enter the information to set up the location where you want your computer objects stored and click Next. See Table 2-7 for details.

   Figure 2-5. Computer Creation Options

   

   Table 2-7. Options for Creating the Location where Computer Objects are stored

   Option	Description
   Computer Creation Location	Enter the location in your LDAP directory where the computer creation daemon creates the objects that represent managed clients. The job of the computer creation daemon is to detect and authenticate client systems as they come online. When a new client is detected, the daemon places an associated object in the directory structure. Enter the organizational unit first, followed by the organization. For example, ou=computers,o=caldera.
   Computer Search Location	Enter additional locations you want the computer creation daemon to check for existing computer objects before creating a new one. This should not be the same location as the Computer Creation Location since the daemon checks there first by default. Enter the organizational unit first, followed by the organization. For example, ou=testlab,o=caldera.
   Computer Creation Manager Password	Enter the password for the administrator with rights to this location.

5. Specify your software repository configuration then click Next. See Table 2-8 for details.

   Figure 2-6. Software Repository Options

   

   Table 2-8. Software Repository Configuration Options

   Option	Description
   Software Repository	An organizational unit in your LDAP directory that includes objects that represent software packages you plan to distribute. For supported versions of Linux, software packages are referred to as RPMs, SCO OpenServer packages are referred to as custom, and UnixWare® and Open UNIX® 8 packages are referred to as pkg. These objects provide information to the VM Clients on how to find these software packages on the network. Figure 2-7 shows the details for the RPM named "at" in the software repository. Enter the format for the software repository similar to the following: ou=Software Repository, o=caldera.
   Software Repository Manager Password	Enter the password for the administrator with rights in this location.

   The following figure displays RPM details as they appear in the software repository.

   Figure 2-7. RPM Details

   

6. Configure the Software Repository Daemon (SRD) then click Next. See Table 2-9 for details.

   Figure 2-8. Software Repository Daemon Options

   

   The Software Repository Daemon, volutionsrd, monitors the SRD Source Directory for new software packages to process. When you copy software packages to the SRD Source Directory the next time the SRD is scheduled to check the Source Directory, volutionsrd checks for new packages and copies them to the Destination Directory, making them available via the HTTP (default) or FTP server. The SRD then generates a signature security file for that package (packagename.signature) and creates a package object in the Software Repository in the container named secure that contains the URL to the HTTP or FTP server where the file can be found. If the same object created in the container, secure also exists in the container pub, it will be deleted from pub.

   Note: The FTP server on OpenLinux is not started by default. If you want to allow anonymous FTP access, you must start the server. For information on starting the FTP server, see the OpenLinux System Administration Guide.

   The SRD also checks for Caldera Volution Online requests to process. Caldera Volution Online is Caldera's new Internet-delivered software management service. Caldera Volution Online manages Linux systems by providing alerts, information, and software updates to keep your VM Server and VM Client systems up-to-date, secure, and reliable.Volution Manager provides integration with Caldera Volution Online through the Volution Manager Management Console (VM Management Console).

   The SRD retrieves the packages from Caldera Volution Online and adds them to the software repository.

   Table 2-9. Software Repository Daemon Configuration Options

   Option	Description
   LDAP Check Interval (minutes)	Establishes the frequency that you want the SRD to look in the LDAP directory for packages that have been requested through the Caldera Volution Online integration. Generating Caldera Volution Online requests is done through the VM Management Console.
   File System Check Interval	Establishes how often you want the SRD to check the SRD Source Directory for any new package files.
   SRD Source Directory	The location where the SRD looks for packages to process. Manually copy packages here that you want imported into the software repository by the SRD.
   SRD Destination Directory	The directory where the SRD puts package files to distribute. This directory must correspond with the HTTP server URL specified in the SRD URL.
   SRD URL	The URL for the HTTP server on your OpenLinux server.

   Volution Manager provides X.509 certificate-based security. Select your security level and click Next. See Table 2-10 for details.

   If you selected Normal, continue with the next step. If you selected Minimum, skip to the end of the installation instructions.

7. Complete the fields on the Volution Certificate Information screen, then click Next. See Table 2-11 for details.

   Figure 2-9. Volution Manager Security Level

   

   Table 2-10. Security Level

   Level	Description
   Normal	Creates and installs the Volution Manager Certificate Authority (CA). A CA is an authority that issues and manages security credentials and keys for message encryption. As a part of the public key infrastructure (PKI), a CA checks to verify information provided by the requester of a digital certificate. If the request is verified, the CA can then issue a certificate.
   Minimum	Provided for ease of installation. There is no security installation required with this selection. However, a pre-generated place-holder certificate is installed by default.

8. Complete the fields on the Volution Certificate Information screen, then click Next. See Table 2-11 for details.

   Figure 2-10. Volution Manager Certificate Information

   

   Table 2-11. Creating the Volution Manager Authority Key

   Field	Description
   Name of your company or organization	Enter the name of your company or organization.
   Your name	Enter the name of the system administrator generating this authority key.
   Your email address	Enter the email address of the system administrator generating this authority key.
   Enter the CA Key password	This password must be at least six characters. Use the regular password precautions to create your password. For example, your password should not be a dictionary word.
   Directory to backup keys and certificates	Enter the location where you want to keep the Volution Manager Authority Key. To protect the key from exposure to computers on the network, the default backup location is a floppy.

   Important: The Volution Manager Authority Key on the VM Server includes a subject, issuer, and fingerprint. The VM Client CA Certificate also includes this information. As an extra measure of security you can cross check the information on the VM Server's Volution Authority Key with the VM Client CA Certificate when you install VM Clients. To do this, you must know what the information is on the VM Server Authority Key. If your VM Clients are remote you need to have this information written down for those installing VM Clients. To view this information on the VM Server, enter /opt/volution/bin/volutionkeytool cacert list. Keep this information available when you install your VM Clients.

   For information on the Volution Manager Key Tool, see Section 3.3.1.3, Section 3.3.2.1, and Section 3.3.3.1.

   Volution Manager provides secure communication between your web browser and the Apache Web Server using an SSL certificate. If you already created a certificate for Apache, you don't need to create another one. If you want to use the certificate that the Volution Manager creates during installation, you can make that selection now.

9. Check the checkbox to use the Volution Manager certificate created during installation for the Apache Web Server to use. If you would be prefer to have separate certificates, leave the box unchecked.

   Figure 2-11. Apache Certificate

   

10. Verify that the information on the Installation Approval screen is correct and then click Next.

    Figure 2-12. Installation Approval

    

    The Postinstall Diagnostics screen appears with the URL for your VM Management Console.

11. To verify that the VM Server is operational, open a web browser and enter:

    https://yourserver.yourcompany.com/volution

    Important: Make sure to enter https. The VM Management Console is a secure web site.

    For information on using the VM Management Console, see the Volution Manager Administration Guide.

You are ready to install VM Clients. See Chapter 3 for instructions.

If the status field for any component indicates that it failed to start, refer to Section 2.6.

2.4.2. Selecting the Quick Installation

To initiate the installation, see Section 2.4.

1. Select Quick Installation, and the following screen appears:

   Figure 2-13. Quick Installation

   

2. Enter the password for the OpenLDAP administrator. Use this password to log in to the VM Management Console. Defaults are used for all other settings. See Table 2-12 for defaults. The defaults are expressed using the example server hostname, yourserver.caldera.com.

   Table 2-12. Quick Installation Defaults

   Setting	Default
   LDAP Server Hostname	If Volution Manager is installed on an OpenLinux system named yourserver.caldera.com, the LDAP Server Hostname is also yourserver.caldera.com. See Table 2-5 for details.
   LDAP Naming Context or top level of the directory tree.	The top level or root of your LDAP directory is the domain name portion of the hostname or o=caldera. See Table 2-5 for details.
   Computer Creation Location	Using the example LDAP server hostname, yourserver.caldera.com, the computer creation location is ou=computers,o=caldera. See Table 2-5 for details.
   The LDAP Check Interval	2 minutes. See Table 2-9 for details.
   File Check Interval	1 minute. See Table 2-9 for details.
   SRD Source Directory	/opt/volution/srdfiles/ See Table 2-9 for details.
   SRD Destination Directory	/home/httpd/html/VolutionSoftware/ See Table 2-9 for details.
   SRD URL	http://yourserver.caldera.com/VolutionSoftware/ See Table 2-9 for details.
   Security	Minimum See Table 2-10 for details.

3. Verify that the information on the Installation Approval screen is correct, then click Next.

   Figure 2-14. Installation Approval

   

   The Postinstall Diagnostics screen appears with the URL for your VM Management Console.

4. To verify that the VM Server is operational, open a web browser and enter:

   https://yourserver.yourcompany.com/volution

   Important: Make sure to enter https. The VM Management Console is a secure web site.

   For information on using the VM Management Console, see the Volution Manager Administration Guide.

5. Enter the OpenLDAP administrator's password to log in to the VM Management Console.

You are ready to install VM Clients. See Chapter 3 for instructions.

If the status field for any component indicates that it failed to start, refer to Section 2.6.

2.4.3. Selecting the Demo Installation

To initiate the installation, see Section 2.4.

1. Select Demo Installation and the Volution Manager Installation screen appears.

2. Click Next. Defaults are used for all settings. See Table 2-13 for defaults. The defaults are expressed using the example server hostname, yourserver.caldera.com.

   The Postinstall Diagnostics screen appears.

   The Postinstall Diagnostics screen appears with the URL for your VM Management Console.

3. To verify that the VM Server is operational, open a web browser and enter:

   https://yourserver.yourcompany.com/volution

   Important: Make sure to enter https. The VM Management Console is a secure web site.

4. Enter demo to log in to the VM Management Console.

   For information on using the VM Management Console, see the Volution Manager Administration Guide.

You are ready to install VM Clients. See Chapter 3 for instructions.

If the status field for any component indicates that it failed to start, refer to Section 2.6.

2.6.1. Diagnosing Common Problems

Most of the errors that you might encounter when running Volution Manager fall into one of these categories:

• The computers running the VM Server, VM Management Console, Directory Services, or VM Client software are down. Ensure that these systems are functioning and on the network before further troubleshooting.

• The network is down. Test network connectivity between systems by running ping, telnet, or any other basic network command.

• Network services are not running or are not configured correctly. You must ensure that TCP/IP networking, including SNMP and DNS, are correctly installed, configured, and running on your system. See your System Administration Guide for more information.

• Services used by Volution Manager are not running. Volution Manager's key functionality is managed by daemons that run on the VM Server and VM Clients. Each daemon, such as densd or volutiond, can be manually started using the start command. For example, to start densd, enter:

  /etc/rc.d/init.d/ densd start

  The VM Server must be running volutionccd, densd, volutionsrd, and slpd. VM Client systems must be running volutiond.

  These services may also be running, but not configured correctly. See the Volution Manager Administration Guide for more troubleshooting information.

For more information on troubleshooting, see the Volution Manager Administration Guide.