This procedure describes how to upgrade Sun Ray Software on an existing Sun Ray server. This procedure relies on a specific Sun Ray configuration. See Chapter 4, Installing and Configuring for details.
Note the following information before performing the upgrade.
Make sure the operating system on the Sun Ray server complies with the Sun Ray Server 5.2 requirements listed in Section 2.1, “Operating System Requirements”. If not, you'll have to upgrade the operating system on the Sun Ray server as part of the Sun Ray Software upgrade.
Upgrades from Sun Ray Software 4 10/08 (Sun Ray Server Software 4.1) and later are supported with Sun Ray Software 5.2. You can upgrade directly to the latest Sun Ray Software 5.2.x release update, which means you do not have to upgrade to Sun Ray Software 5.2 first before upgrading to Sun Ray Software 5.2.x.
You cannot migrate a Sun Ray server configuration to a hardware platform of a different Instruction Set Architecture. For example, you cannot migrate an existing SPARC-based Sun Ray server configuration to a new x86-based Sun Ray server.
Although not necessary in most circumstances, you should preserve the configuration data on the Sun Ray server and copy the backup file to another location. See Section 6.3, “How to Preserve Sun Ray Software Configuration Data” for details.
Inform users about the upgrade.
Before you upgrade Sun Ray Software, inform your users of your plans, and have them terminate their sessions. An effect of the upgrade procedure is that all active and suspended sessions are lost.
If you are upgrading Sun Ray servers in a failover group, consider ways to reduce downtime.
See Section 6.2, “Planning Upgrades Using Failover Groups” for details.
Become superuser on the Sun Ray server.
To avoid installation script errors that can occur if user environment settings are carried forward, use the following command:
% su - root
List the current Sun Ray network configuration and retain the information. You need to reconfigure the Sun Ray network after the upgrade.
# /opt/SUNWut/sbin/utadm -l
If necessary, upgrade the operating system on the Sun Ray server.
Preserve the configuration data on the Sun Ray server and copy the backup file to another location. See Section 6.3, “How to Preserve Sun Ray Software Configuration Data” for details.
Uninstall the Sun Ray Software on the Sun Ray server. See Section 4.8, “How to Remove Sun Ray Software” for details.
Upgrade Oracle Linux on the Sun Ray server.
If neccessary, copy the Sun Ray server configuration data backup file created
earlier,
/var/tmp/SUNWut.upgrade/preserve_,
to the same location on the upgraded Sun Ray server. The Oracle Linux upgrade should
have retained this file.version.tar.gz
Go to Step 6.
(Optional) Preserve the configuration data on the Sun Ray server and copy the backup file to another location. See Section 6.3, “How to Preserve Sun Ray Software Configuration Data” for details.
This step is not necessary because the Solaris upgrade will not affect the Sun Ray Software configuration data. However, backing up data before performing an operating system upgrade is always good practice.
Upgrade Solaris on the Sun Ray server.
Go to Step 6.
Download and unzip the Sun Ray Software 5.2 Media Pack and make it accessible to the Sun Ray server.
Change directory to the downloaded media pack image.
Upgrade the Sun Ray Software.
# ./utsetup
The utsetup script preserves the current
Sun Ray Software configuration data in the
/var/tmp/SUNWut.upgrade/preserve_
file and restores it after the upgrade.
version.tar.gz
When the script ends, a log file is available at:
Linux:
/var/log/utinstall.year_month_date_hour:minute:second.log
Solaris:
/var/adm/log/utinstall.year_month_date_hour:minute:second.log
The values in the file name reflect a time stamp of when the commands are started. Check these files for notices of installation problems.
See Section 4.9, “Installation (utinstall) Error Messages” for a listing of utinstall error messages.
Reconfigure the Sun Ray network based on the previous configuration you confirmed in step 4.
For a shared network (LAN) with external DHCP server support (used utadm -L on) | No action is required. This configuration is preserved during the upgrade. |
For a shared network (LAN) with Sun Ray server DHCP support | # /opt/SUNWut/sbin/utadm -A |
For a private network | # /opt/SUNWut/sbin/utadm -a |
If necessary, update the location of the Tomcat installation.
# /opt/SUNWut/sbin/utconfig -w
See the Admin GUI Upgrade section in the Administration Guide.
Configure the Windows connector feature if it was not previously installed or configured properly on the Sun Ray server.
# /opt/SUNWut/sbin/utconfig -c
Repeat Steps 1 through 11 for each server in failover group.
Synchronize the updated firmware on the Sun Ray clients.
You must perform this task on a stand-alone Sun Ray server or the last Sun Ray server configured in a failover group. It takes the current firmware available on the Sun Ray server and upgrades all the firmware on the Sun Ray clients. The Sun Ray clients reboot themselves and load the new firmware.
# /opt/SUNWut/sbin/utfwsync
If you plan to use the Windows connector, upgrade the Windows Connector Components on your designated Windows Server.
There is no upgrade program for the Windows connector components. To upgrade a Windows system with the previous components installed, remove the current Windows connector components and install the new versions.