Solstice AutoClient 2.1 Installation and Release Notes

Installing Your License Software and Enabling Your Licenses

A single script, lic_install, installs your license software and starts the license install tool (lit) which is used to enable your licenses. If you have more than one license server, you must use the following procedure on each license server.

Prerequisites

This procedure assumes the following conditions are true:

How to Install and Enable the License Software Using a License File

If you received the license information by email, follow these steps:

  1. Log in as root on the system that will be the license server.

  2. Run the lic_install script in the top-level product CD directory.


     # ./lic_install
    
  3. Select License Server Installation to install the license server packages.

    Answer yes to any pkgadd questions.

  4. After the license server packages are installed, select Product License Setup to set up the individual product licenses.

  5. Select the OpenWindows Graphical User Interface to run the Product License Tool.

  6. When the License Installation Tool window is displayed, select Solstice AutoClient 2.1 from the Products menu.

  7. Click on Select License From File button and supply the path name to the (saved email) license file in the space provided.

    A pop-up window displays the product o be licensed.

  8. Click on Continue to continue installing the license.

  9. Click on OK in the confirmation window that appears.

  10. Click on the Exit-Install Licences button to the install the license and exit the tool.

  11. Click on the Quit button in the pop-up window.

    A pop-up window that confirms that the product is successfully licensed is displayed.

  12. Follow the instructions displayed by the lic_install script to create the elementary license file on the AutoClient product servers.

    The AutoClient product servers are the station manager systems installed with the Solstice AutoClient 2.1 software on the local filesystem. Copy the /etc/opt/licenses/LIC_CONFIG_SCRIPT to each product server and execute it to create the elementary license file.

How to Install and Enable the License Software Without a License File

If you received the license information in a fax or over the phone, follow these steps:

  1. Log in as root on the system that will be the license server.

  2. Run the lic_install script in the top-level product CD directory.


     # ./lic_install
    
  3. Select License Server Installation to install the license server packages.

    Answer yes to any pkgadd questions.

  4. After the license server packages are installed, select Product License Setup to set up the individual product licenses.

  5. Select the OpenWindows Graphical User Interface to run the Product License Tool.

  6. When the License Installation Tool window is displayed, select Solstice AutoClient 2.1 from the Products menu.

  7. Enter the information requested.

    Use the license information you received from the license distribution center.

  8. Verify that the Data and Password Checksum fields match the information you received from the license distribution center.

  9. Select Done With License.

  10. Click on the Exit-Install Licences button to the install the licenses and exit the tool.

  11. Click on the Quit button in the pop-up window.

    A pop-up window that confirms that the products are successfully licensed is displayed.

  12. Follow the instructions displayed by the lic_install script to create the elementary license file on the AutoClient product servers.

    The AutoClient product servers are the station manager systems installed with the Solstice AutoClient 2.1 software on the local filesystem. Copy the /etc/opt/licenses/LIC_CONFIG_SCRIPT to each product server and execute it to create the elementary license file.

Verifying That Licensing Was Set Up Correctly

After installing and configuring the licensing software, try adding an AutoClient and see if license error messages are displayed. If they are, licensing was not set up correctly. Look for errors (for example, encryption errors) in the start-up file /tmp/license_log.