2.1. Before You Upgrade

This section describes the things you must know and do before upgrading.

2.1.1. Upgrades and Early Access Program Software

Upgrades to, or upgrades from, Early Access Program (EAP) software releases of SGD are not supported. EAP software releases must always be a fresh installation.

2.1.2. Conditions for Upgrading

The supported upgrade paths to this version of SGD are listed in the Oracle Secure Global Desktop Platform Support and Release Notes for Release 4.7 available at http://www.oracle.com/technetwork/documentation/sgd-193668.html.

If you want to upgrade from any other version of SGD contact Oracle Support.

If you are sure you want to perform an unsupported upgrade, you must create an empty file /opt/tarantella/var/UPGRADE before installing the new version of the software. Your SGD installation might not be upgraded correctly.

2.1.3. Upgrades and Secure Mode Installations

Starting with SGD release 4.7, SGD is installed by default in secure mode. For secure mode installations, an SSL certificate is installed on the SGD server. The SSL certificate can be a self-signed certificate that is generated during installation, or you can use your own certificate.

What happens on upgrade depends on whether the pre-upgrade version of SGD uses secure connections as follows:

  • If the pre-upgrade installation is not secure, the upgrade defaults to a secure mode installation. This is the same as for a clean install of SGD.

  • If the pre-upgrade installation is secure and uses a self-signed certificate, the upgrade defaults to a secure mode installation and will install a new self-signed certificate.

    Note

    If you are using the SGD server with the SGD Gateway, you must reconfigure your Gateway deployment by installing the new certificate on the Gateway. See the Oracle Secure Global Desktop Gateway Administration Guide for Release 4.7 for details of how to install an SSL certificate on the Gateway.

  • If the pre-upgrade installation is secure and uses a certificate supplied by the user, the upgrade defaults to a secure mode installation using the same certificate.

2.1.4. Upgrades and Client Access Licenses

Starting with SGD release 4.7, Client Access Licenses (CALs) for non-Windows client devices are no longer stored in a license pool on the SGD server. CALs are now stored in a location on the client device.

Following an upgrade to SGD 4.7, non-Windows client devices can use temporary CALs issued by the Remote Desktop Session Host. The temporary CALs can be used until the correct CALs have been stored on the client device.

2.1.5. Before You Upgrade on Oracle Solaris Platforms

When you upgrade on Oracle Solaris platforms, the pkgadd command performs several checks and asks you to confirm the changes before installing the package. You can create an administration file that instructs pkgadd to bypass these checks and install the package without user confirmation.

To avoid user interaction, the administration file must contain the following lines:

conflict=nocheck
instance=unique

When you upgrade SGD, use the pkgadd -a adminfile command to specify the administration file.

If you do not specify an administration file when you upgrade, the SGD installation program creates one for you and gives you the option to quit the installation so that you can run the pkgadd command again with the -a adminfile option.

2.1.6. Upgrades and Your Existing Configuration

When you upgrade, the following changes are applied to your existing configuration:

  • Your existing local repository, formerly called the Enterprise Naming Scheme (ENS) datastore, is preserved and backed up.

    The local repository is the storage area for all the objects in your SGD organizational hierarchy.

    The /opt/tarantella/var/ens directory is backed up to the /opt/tarantella/var/ens.oldversion directory.

    The backup is not changed. The existing ENS database might be changed if changes are needed to enable it work with the new version of SGD.

  • The SGD server configuration and the SGD global configuration are preserved but not backed up.

    This configuration is stored in the /opt/tarantella/var/serverconfig directory.

    This configuration is changed only if new properties files need to be added or new attributes need to be added to existing properties.

  • All the server resources files in the /opt/tarantella/var/serverresources directory are replaced.

    These files are not normally edited as they control how SGD works.

  • Your SGD login scripts are preserved and backed up.

    The /opt/tarantella/var/serverresources/expect directory is backed up to /opt/tarantella/var/serverresources/expect.oldversion.

  • Your customized SGD files are backed up but they are not upgraded.

    You can customize SGD by changing the files found in a standard installation, for example webtop themes, or by adding your own files, for example login scripts.

    You have to upgrade these files manually.

    When you install the new version of SGD, the installation program warns you if files exist that might need to be upgraded manually. See Section 2.2.3, “Upgrading a Customized SGD Installation” for advice on how to upgrade these files.

2.1.7. Upgrades and UNIX Audio

Following an upgrade, if you want to use audio for X applications you must also upgrade the SGD Enhancement Module on your UNIX or Linux platform application servers. See Section 2.3.2, “How to Upgrade the SGD Enhancement Module for UNIX and Linux Platforms” for upgrade instructions.

UNIX audio services might not work correctly if the versions of SGD and SGD Enhancement Module are different.