Sun Ray Server Software 1.2 README



The Sun Ray server software 1.2 replaces the Sun Ray enterprise server software 1.1 as the next generation software release. This server-based software is used to manage, administer, and provide the screen display for Sun Ray appliances driven in a hot desk environment.

The Sun Ray server software 1.2 release includes the same functionality of the 1.1 release plus the following new features:

Location of the Product Notes

The product notes for this release are located in the /Supplemental directory on the Sun Ray Server Software 1.2 CD-ROM.

Enterprise 10000 Server

Sun Ray server software 1.2 is compatible with the Enterprise 10000 server in the Solaris 2.6, 7, and 8 operating environments; however, due to the Solaris 8 operating environment's trunking capabilities and a new and enhanced implementation of syncq, it is the recommended operating environment.

Summary of Known Issues

The remainder of this README describes the known issues with the release of the Sun Ray Server Software 1.2. Most of the issues involve known intermittent problems. It is advisable to read this document prior to installing the software.

The utfwsync Command

The utfwsync command refreshes the firmware level on Sun Ray Thin Clients to what is available on the Sun Ray servers in a failover group and then forces all the Sun Ray appliances within the group to restart, causing each appliance to attempt to download the latest firmware offered by the failover host to which it is attached as it restarts, as described in utfwadm(1M).

Note: Use this command after software upgrades and after new firmware has been installed on all hosts as part of a patch.

As the command executes, access to user sessions is interrupted, but the sessions are not lost and are returned after the command completes.

Note: The command must be run with superuser privileges.

The -v verbose mode option is supported.

The utxconfig Command

You must be root to use the utxconfig -o command.

Adding Smart Card Configuration Files

If you are adding multiple smart card configuration files at the same time in a failover environment, add the files only from the primary LDAP server using the utcard command.

Input to the Self-Registration GUI

The self-registration GUI only supports the input of ASCII characters. It does not support input of non-ASCII characters (for example, Asian characters or European letters that use diacritic marks). Contact your site system administrator to input these characters via the administration application (GUI or the command-line interface).

Language Environment

Sun Ray server software 1.2 has not been fully localized in the Traditional Chinese environment; consequently, if you use the software in this environment, most of messages are unreadable.

If you choose to run applications in the zh_TW locale, explicitly change your language environment to C before running them.

To set your environment for the C shell, type:

% setenv LC_ALL C

To set your environment for the Born or Korn shell, type:

$ LC_ALL=C; export LC_ALL


Hotsync can fail when using Digi 2 to sync big memo files. This problem is intermittent but frequent.

Multiple NICs Per Subnet

Multiple NICs per subnet are supported by the Solaris operating environment; however, such a setup is not necessarily supported by DHCP.

Omit one interface (using the -i option) so that in.dhcpd is only listening to one interface on the subnet.

Device Ownership

If you use printers that support lp printer queue, the print queue is owned by root. Consequently, even though a user inserts a smart card and takes ownership of an attached printer, anyone can send a print job to that printer and the print queue continues when the user removes the smart card.


In a failover scenario, the attached devices are able to communicate with the new device manager in 80 seconds.

Patch 106621-08

Patch 106621-08 replaces the dsadm file, breaking the following links:



Recreate the links by hand after patch 106621-08 has been applied.

Appliances Display Green Newt When Two Servers are Rebooted

In a failover environment, when the server resets on a panic message or is rebooted, some of the appliances connected to the server do not failover successfully. They display the hourglass and do not recover. To recover, power-cycle the affected appliances.

Hot Desking

There is a 15-second timeout period after a smart card is removed from a Sun Ray Thin Client during which most processes terminate. At the present time, jobs that are printing on printers with an lp printer queue continue to print.

Serial Printers

Serial printers are not supported in the Sun Ray server software 1.2 release.

The lpq Command

The lpq command does not work in the Solaris 8 operating environment.

Internet Protocol Multi-Pathing

Internet Protocol Multi-Pathing (IPMP) feature for the Solaris 8 operating environment is not supported in the Sun Ray server software 1.2 release.


Additional files for the StarOffice application are located in the Supplemental directory on the Sun Ray Server Software 1.2 CD-ROM.

After hotsyncing using StarOffice, exit and restart StarOffice.

Global Policy Issues

utglpolicy Option

Previous documention erroneously listed a del:tid option for utglpolicy.

The utglpolicy command must always be given a complete policy and token reader specification; therefore, if you want to add a token reader using utglpolicy, you must specify the current policy settings again.

Token Reader

After configuring token reader, restart services instead of resetting them to retain token reader status.

Installation and Upgrade Issues

When upgrading your operating environment, it is strongly recommended that you upgrade to the Solaris 8 operating environment.

Solaris 8 Patch

Patch 109472-02 or a later revision should be applied before installing Sun Ray server software 1.2. This patch is required only for Sun Ray server software 1.2 installation over the Internet because there is risk of potential data corruption on any piece of data transported by TCP.

If adding this patch does not solve this data corruption issue, then add this line in the /etc/init.d/inetinit file at about line 76.

# switch off TCP Selective Acknowledgement (SACK) processing because
# it contains a bug that causes the NFS client to corrupt data.
# See BugID 4319441
ndd -set /dev/tcp tcp_sack_permitted 0
Because of this problem, installation of Japanese documentation could fail on systems using the Solaris 8 operating environment if the Sun Ray packages reside on an NFS-mounted partition.

Adding Appliances During Upgrade

Do not add appliances while upgrading the primary server.

Inadvertent Installation of Japanese Documentation

During upgrade from 1.1 to 1.2, utinstall installs Japanese documentation by default.

Smart Card Configuration Files

Smart card configuration files are not preserved during an upgrade to Sun Ray server software 1.2. These files could be overwritten with the new configuration files or be lost if the Solaris operating environment is reinstalled.

Note: Make a copy of these files before upgrading to the new software.

Matching Software and Firmware

The Sun Ray software version running on the server must match the Sun Ray firmware version running on the appliance. When upgrading a non-group environment, this is not a problem. To make sure all the appliances are running the new firmware in a group environment, you must install the new server software on all servers and then restart each appliance.

Note: If an appliance is not restarted after the new server software has been installed, it continues running the old firmware and the features in the new firmware are not available.

To Upgrade the Sun Ray Server Software in a Single Server Environment

  1. To preserve the current configuration and data, type:

       # /cdrom/cdrom0/.upgrade/utpreserve

  2. To install or upgrade to Sun Ray server software 1.2, type:

       # /cdrom/cdrom0/utinstall

  3. To upgrade the firmware, type:

       # /opt/SUNWut/sbin/utfwadm -A -a -n all
    # /etc/init.d/utsvc stop

  4. Wait 60 seconds.

  5. To reboot the system, type:

       # init 6

Note: For further information, please refer to the Sun Ray Server Software 1.2 Product Notes.

Note: Use the utinstall command to upgrade the existing installation. There is no need to remove the previous installation of Sun Ray server software.

To Upgrade Sun Ray Server Software in a Multiple Server Environment (Failover Group)

  1. Before starting an installation or upgrade procedure, disable the firmware download by typing:

       # /opt/SUNWut/sbin/utfwadm -D -a -n all

    This prevents appliances from getting the new firmware before the entire server group is upgraded.

    Note: All servers within a group must be upgraded before any of the appliances download the new firmware.

  2. To upgrade each server within the group:

    1. Notify users connected to the server requesting that they switch their sessions to another server in the group.

      Note: Do not run utreplica -u as described in the Sun Ray Server Software 1.2 Product Notes.

    2. To preserve current configuration and data, type:

      # /cdrom/cdrom0/.upgrade/utpreserve

    3. To install or upgrade the Sun Ray server software 1.2, type:

      # /cdrom/cdrom0/utinstall

      Note: For further information, please refer to the Sun Ray Enterprise Server Software 1.1 Installation Guide.

      Note: While upgrading the primary server, do not add new DTUs or register new users. Because the primary server is not available, DTUs and user information cannot be propagated to the secondary servers.

      Note: While transitioning from version 1.1 to 1.2, you might have a group of servers which are upgraded and others which are not. In this case, basic functionalities are supported (attaching a new DTU or register a new card). However, 1.2 features are not be supported until all servers in the group have been upgraded to 1.2 and it is strongly recommended not to use them in a mixed environment.

      Note: In a mixed environment (1.1 and 1.2 servers), edit desktop properties can fail but changes are applied.

      Note: Do not follow the steps in the section "Sun Ray 1 Thin Client Firmware Update" in Chapter 6 of the Sun Ray Enterprise Server Software 1.1 Installation Guide. This should be done after all servers in the group have been upgraded.

      Note: The utinstall command performs an upgrade of the existing installation. There is no need to remove the previous installation of Sun Ray software.

  3. From the console of the primary, to enable the appliance firmware upgrade and cause all applicances to load the new firmware, type:

    # /opt/SUNWut/sbin/utfwsync

    Note: This command temporarily resets all appliances in the group and holds them at reset for approximately 60 seconds in order to cause the new firmware to be loaded. Sessions are not lost, and all services resume after the 60 second delay.

    Note: The section "Sun Ray 1 Thin Client Firmware Update" in Chapter 6 of the Sun Ray Enterprise Server Software 1.1 Installation Guide contains another option for enabling firmware upgrades.

    Note: If utfwsync is not used, you can download the new firmware to each appliance by using the key sequence Cntrl-Power to reset the the appliance. This must be done on each appliance. If utfwsync is used, this step is not necessary.

Multihead Issues

Locking the Display for a Multihead Group

If you are using CDE and the display is locked for a multihead group containing more than ten appliances, the session is lost. Use xlock as a workaround.

Cannot Log Into a Multihead Group

For CDE, if a user logs into a multihead group containing six or more appliances on the Solaris 2.6 and Solaris 7 operating environments, the dtlogin screen is redisplayed each time the user tries to log in after providing a user name and password.

Note: This is not the case for OpenWindows.

Auto Sizing

With this release the default resolution is auto sized. The largest resolution supported by the monitor is automatically used when a session is created. Auto sizing can be turned off and on using the utxconfig command.

In addition to resolution, auto sizing also looks for the best fit for two other startup parameters: screen geometry and screen order by automatically defining the number of screens used when a session is created in a multihead group and their order.

With auto sizing enabled (the default), a session group is always created to equal the size of the multihead group where the session is created.

The utmhadm Command

To communicate the physical layout of the Sun Ray Thin Clients in a multihead group to the system, the canonical identifiers (CID) must be specified in row-major order using the utmhadm command with the -l option. Row-major order means that you start with the top-left corner, then move to the right until you complete the top row, then start on the next row down on the left edge, and proceed to the right, and so on.

In the current software release the CID can be specified using the 12-digit hexadecimal MAC address of the terminal. The maximum number of terminals allowed is 16.

Multihead Group Names

Multihead group names must consist of ASCII alphanumerics and hyphens.

Problems Fixed Since the Beta Release

The following problems have been fixed in this release:

Further Information

Further information on Sun Ray server software 1.2 can be found on the website: