This section provides detailed information about how to install Sun Ray Software.
The utinstall and utconfig commands are the basic commands to install and configure Sun Ray software on a system. There are also a number of additional commands that you need to run to configure a basic Sun Ray server and make it ready to provide sessions to clients.
The utsetup command provides a way to run all
the appropriate commands, including utinstall
and utconfig, in the appropriate sequence to
install and configure a Sun Ray server. By design, the
utsetup command configures a Sun Ray server
to use a shared network (LAN) and it generates a set of
.parms
files in the
/tftpboot
directory for managing Sun Ray
client firmware. This recommended configuration is detailed in
Chapter 2, Planning a Sun Ray Network Environment.
When you use utsetup command to initially install a Sun Ray server, it runs the following commands in sequence:
utinstall
utconfig
utpolicy -a -z both -g -M
utreplica (if HA/failover group selected)
utfwadm -A -a -V (optional)
utadm -L on (optional)
utstart -c
See Section 3.2.5, “How to Install and Configure Sun Ray Software” for installation instructions using the utsetup command.
If you need to install and configure a Sun Ray server in a different way than what the utsetup command provides, you must run the individual commands as noted in Section 3.2.1, “Using the utsetup Command”. The following situations may force you to do this:
Using JumpStart (Oracle Solaris) or Kickstart (Oracle Linux) to install the software.
Configuring the Sun Ray Software without the Sun Ray data store, which is known as zero administration mode.
This document does not provide detailed instructions about how to use the individual commands instead of using the utsetup command. Refer to the man pages for detailed information about the alternative commands.
The utsetup command enables you to clone the
Sun Ray Software installation and configuration process by
recording the user responses to the installation prompts and
then using those responses at another time and even on another
Sun Ray server. User responses are stored in the
/var/opt/SUNWut/utdialog.d/*.utdialog_responses.props
files and are known as response files.
With utsetup and response files, you have the ability to clone a Sun Ray server installation and configuration setup or to provide default settings for a hands-free, automated installation and configuration solution. Cloning Sun Ray servers can be helpful in many situations, including setting up a number of Sun Ray servers in a failover group.
Using the utsetup command without any options performs an actual install and configuration on the server you run it on.
The following commands can use the information recorded in the response files:
utsetup
utinstall
utconfig
utpolicy
utpw
utgroupsig
utreplica
See the following procedures for automating Sun Ray Software installations:
Starting with Sun Ray Software release 5.3, the Sun Ray Operating Software, formerly known as Sun Ray Client firmware, is no longer included with Sun Ray Software and must be downloaded from My Oracle Support separately. Updating the Sun Ray Clients with the latest Sun Ray Operating Software ensures that the latest Sun Ray Software features are provided. The Sun Ray Client firmware is now officially called Sun Ray Operating Software, but the term "firmware" will continue to be used throughout the documentation. See Sun Ray Operating Software 11.0 Release for details.
If you download and install the latest Sun Ray Operating Software before you install Sun Ray Software on a server, the utsetup command enables you to configure the installed firmware and make it available to clients through the utfwadm command similar to previous releases. The current installation procedure provides steps on how to download and install the firmware.
Installing the latest Sun Ray Operating Software before installing Sun Ray Software is recommended, but you can still install and configure the firmware after installing Sun Ray Software. To update the firmware on Sun Ray Clients outside of the Sun Ray Software installation process, refer to Section 14.3, “How to Update Firmware on Sun Ray Clients”.
If the firmware is not installed on the server, the Sun Ray Software installation script will provide the following warning:
Sun Ray Operating Software (firmware) is not installed. It is recommended that you install the latest firmware before installing Sun Ray Software. Continue without firmware? (Y/N) [Y]
Also, if an older firmware version is installed on the server, the Sun Ray Software installation script will provide the following warning:
You are attempting to install SRS on a system with an old version of Sun Ray Operating Software. Continue with old firmware? (Y/N) [N]
This procedure uses the utsetup command to install and configure a Sun Ray server for both the Oracle Linux or Oracle Solaris operating system.
The utsetup command optionally configures a Sun Ray server to use a
shared network (LAN) and generates a set of .parms
files in the
/tftpboot
directory for managing Sun Ray client firmware (DHCP is not
configured to manage firmware downloads). This configuration is detailed in Chapter 2, Planning a Sun Ray Network Environment.
Make sure the server targeted to become the Sun Ray server meets the Sun Ray Software product requirements.
A Sun Ray server requires both a fixed host name and a static IP address. A Sun Ray server cannot be a DHCP client.
It is recommended that you download and install the latest Sun Ray Operating Software (firmware) before starting the Sun Ray Software installation. Updating the Sun Ray Clients with the latest firmware ensures that the latest Sun Ray Software features are provided.
(Oracle Linux only) The Sun Ray Software installation script removes the Shutdown/Restart options from the console; however, you can open a terminal and execute the commands.
Download and unzip the Sun Ray Software 5.3 media pack and make it accessible to the Sun Ray server.
See http://www.oracle.com/technetwork/server-storage/sunrayproducts/downloads/index.html
(Optional) Download and unzip the latest Sun Ray Operating Software (firmware) and make it accessible to the Sun Ray server.
See http://www.oracle.com/technetwork/server-storage/sunrayproducts/downloads/index.html
Updating the Sun Ray Clients with the latest firmware ensures that the latest Sun Ray Software features are provided.
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
If you downloaded the latest Sun Ray Operating Software (firmware), change directory to the unzipped firmware directory and install the firmware to make it available to the Sun Ray Software installation script.
# ./utfwinstall
Change directory to the unzipped Sun Ray Software media pack and install Sun Ray Software on the Sun Ray server.
# ./utsetup
See the Examples section below for an example of the utsetup output.
When the installation script ends, the log files are available at:
Oracle Linux:
/var/log/utsetup.year
_month
_date
_hour
:minute
:second
.log
Oracle Solaris:
/var/adm/log/utsetup.year
_month
_date
_hour
:minute
:second
.log
The values in the file names reflect a time stamp of when the command was started. Check these files for notices of problems.
See Section 3.2.10, “Installation (utinstall) Error Messages” for a listing of utinstall error messages.
If the Sun Ray server is running Oracle Solaris, use the following steps to increase the performance of the Sun Ray Clients:
Add the following line to the Sun Ray server's /etc/system
file.
set hires_tick=1
Reboot the Sun Ray server.
For more information, see Section 21.2, “How to Improve Sun Ray Client Performance by Decreasing Buffering on the Network Switch (Oracle Solaris)”.
Repeat steps 3 through 6 for each secondary server if in a failover group.
If you choose the HA group (failover group) configuration during the
utsetup installation of the primary server, you can copy the
generated response files to each secondary server and use the utsetup
command to replicate the failover group configuration. For example, you can save the
response files to the secondary's server's /tmp
directory and then
use the utsetup -a -D /tmp command.
This strategy reduces the time needed to re-enter the same configuration information and can minimize configuration errors. See Section 3.2.7, “How to Clone a Sun Ray Server” for details.
Add the Sun Ray server's host name or IP address to the
sunray-config-servers
and
sunray-servers
DNS entries, which will
make the server available to clients for firmware updates
and Sun Ray sessions, respectively.
See Chapter 2, Planning a Sun Ray Network Environment for details.
To configure any site-wide settings for the Sun Ray Clients, such as
the automatic poweroff feature, you need to update the .parms
file for each client. You need to do this on each designated firmware
server.
See Section 13.1, “How to Centralize Sun Ray Client Configurations (.parms)” for details.
Reboot the Sun Ray Clients to download and update to the new Sun Ray Operating Software (firmware) provided by the Sun Ray server.
When installing Sun Ray Operating Software on Sun Ray 3 Series Clients, the smart card LED will blink for approximately 40 seconds as the smart card controller firmware is being updated. This is normal.
If you plan to use the Windows connector, install the Windows Connector Components on your designated Windows Server. See Section 3.2.6, “How to Install the Windows Connector Components on a Windows System” for details.
The Java Desktop System (JDS) integration package, which delivers a CLI called uttscwrap that improves integration of the Windows connector with the JDS desktop on Oracle Solaris 10.
Change to the media pack location where the JDS integration package is located.
# cd media_pack_directory
/Supplemental/JDS_Integrator/Solaris10+/sparc/Packages
Install the JDS integration package
(SUNWuttscwrap
).
# pkgadd -d .
The uttscwrap command is installed in
the /opt/SUNWuttscwrap/bin
directory.
For more information about the
uttscwrap command, see
Section 18.3, “Using the Windows Connector”.
The Sun Ray Software installation does not install all the locales by default for the Admin GUI. If you want to install the Swedish or Portuguese locales. use the following steps:
Change directory to the media pack image locations where the locale packages are
located (the kio
packages are located in the
Kiosk_Mode_4.4
path):
# cd media_pack_directory
/Components/10-SRSS/Content/Sun_Ray_Core_Services_4.4/Linux/Packages
# cd media_pack_directory
/Components/10-SRSS/Content/Kiosk_Mode_4.4/Linux/Packages
Install the Portuguese locale.
# rpm -i SUNWputo-4.1-04.i386.rpm # rpm -i SUNWpkio-4.1-04.i386.rpm
Install the Swedish locale.
# rpm -i SUNWsuta-4.3-04.i386.rpm # rpm -i SUNWsuto-4.3-04.i386.rpm # rpm -i SUNWsutwa-4.3-04.i386.rpm # rpm -i SUNWsutwh-4.3-04.i386.rpm # rpm -i SUNWsutwl-4.3-04.i386.rpm # rpm -i SUNWskio-4.3-04.i386.rpm
The Sun Ray Software installation does not install all the locales by default for the Admin GUI. If you want to install the Swedish or Portuguese locales. use the following steps:
Change directory to the media pack image locations where the locale packages are located
depending on the hardware architecture of the Sun Ray server (the kio
packages are located in the
Kiosk_Mode_4.4
path):
# cd media_pack_directory
/Components/10-SRSS/Content/Sun_Ray_Core_Services_4.4/Solaris_10+\
/sparc/Packages
# cd media_pack_directory
/Components/10-SRSS/Content/Kiosk_Mode_4.4/Solaris_10+\
/sparc/Packages
# cd media_pack_directory
/Components/10-SRSS/Content/Sun_Ray_Core_Services_4.4/Solaris_10+\
/i386/Packages
# cd media_pack_directory
/Components/10-SRSS/Content/Kiosk_Mode_4.4/Solaris_10+\
/i386/Packages
Install the Portuguese locale.
# pkgadd -d . SUNWputes # pkgadd -d . SUNWputo # pkgadd -d . SUNWpkio
Install the Swedish locale.
# pkgadd -d . SUNWsuta # pkgadd -d . SUNWsutes # pkgadd -d . SUNWsuto # pkgadd -d . SUNWsutwa # pkgadd -d . SUNWsutwh # pkgadd -d . SUNWsutwl # pkgadd -d . SUNWskio
If you plan to use a headless Sun Ray server running Oracle Linux and Sun Ray clients using Gnome Display Manager (GDM), then this configuration will generate errors on the Sun Ray client and consume CPU processes. The errors occur because GDM assumes that the console display is present and GDM will continually attempt to (and fail to) service a non-existent console device.
The workaround is to add the -no-console
option to the preadm command in the Sun Ray
server's /etc/inittab
file:
x:5:respawn:/etc/X11/prefdm --nodaemon --no-console
This workaround is not required for Oracle servers, since they have the Integrated Lights Out Manager (ILOM) Service Processor that provides a virtual console.
The following code output shows an example installing a Oracle Solaris-based Sun Ray server using the utsetup -d command, which installs all the default settings:
# ./utsetup -d ================================================================== === Installing Sun Ray Software - utinstall === . . . . . ***License Agreement (not shown)*** . . . . . Accept? (Y/N) # utinstall-srss Version: 4.4 Thu Dec 29 09:44:34 CST 2011 Sun Ray Server Software 4.4 not installed Sun Ray Data Store 3.4 not installed Kiosk Mode 4.4 not installed Enter Java v1.6 (or later) location: [/usr/java] About to Install Sun Ray Server Software 4.4 Continue? (Y/N) [Y] About to carry out the following operations: Install [ Sun Ray Server Software 4.4 ] Install [ Sun Ray Data Store 3.4 ] Install [ Sun Ray Server Software 4.4 French Admin GUI ] Install [ Sun Ray Server Software 4.4 Japanese Admin GUI ] Install [ Sun Ray Server Software 4.4 Simplified Chinese Admin GUI ] Install [ Sun Ray Server Software 4.4 ] Install [ Kiosk Mode 4.4 ] Install [ Kiosk Mode 4.4 localized files ] Install [ data for utslaunch ] Install [ Sun Ray Server Software 4.4 modules for utsunmc ] Install [ Service Tags 1.1 ] Install [ Smart Card Services 1.5 ] Install [ VMware View Connector 1.4 ] . . . . . ***Sun Ray Server Software package/RPM installation output (not shown)*** . . . . . Installation of Sun Ray Server Software has completed. +++ Installing 'Sun Ray Connector 2.5' . . . . . ***Sun Ray Connector package/RPM installation output (not shown)*** . . . . . +++ Done. ================================================================== === Creating directory structure - utacleanup ================================================================== === Performing basic configuration - utconfig Activating product Product activation output being logged at /var/adm/log/utctl.2011_12_29_09:47:26.log Configuration of Sun Ray Server Software This script automates the configuration of the Sun Ray Server Software and related software products. Before proceeding, you should have read the Installation and Configuration Guide for planning purposes. For your convenience, default values (where applicable) are shown in brackets. Continue? (Y/N) [Y] Enter new UT admin password: Again: Enter new UT admin password: Configure Sun Ray Web Administration? (Y/N) [N] Enter Apache Tomcat installation directory [/opt/apache-tomcat] Enter HTTP port number [1660] Enable secure connections? (Y/N) [Y] Enter HTTPS port number [1661] Enter Tomcat process username [utwww] Enable remote server administration? (Y/N) [N] Configure Sun Ray Kiosk Mode? (Y/N) [N] Enter user prefix [utku] Enter group [utkiosk] Enter userID range start [150000] Enter number of users [25] Configure this server for a failover group? (Y/N) [N] About to configure the following software products: Sun Ray Data Store 3.4 Hostname: sray-server Sun Ray root entry: o=utdata Sun Ray root name: utdata Sun Ray utdata admin password: (not shown) SRDS 'rootdn': cn=admin,o=utdata Sun Ray Web Administration hosted at Apache Tomcat/5.5.20 Apache Tomcat installation directory: /opt/apache-tomcat HTTP port number: 1660 HTTPS port number: 1661 Tomcat process username: utwww Remote server administration: Disabled Sun Ray Server Software 4.4 Failover group: no Sun Ray Kiosk Mode: yes Sun Ray Kiosk Mode 4.4 User name prefix: utku Base user ID: 300000 Number of accounts: 25 Kiosk group name: utkiosk Kiosk group ID: auto Continue? (Y/N) [Y] Updating Sun Ray Data Store schema ... Updating Sun Ray Data Store ACL's ... Creating Sun Ray Data Store ... Restarting Sun Ray Data Store ... . Thu Dec 29 09:51 : utdsd starting Loading Sun Ray Data Store ... Executing '/usr/bin/ldapadd -p 7012 -D cn=admin,o=utdata' ... adding new entry o=utdata adding new entry o=v1,o=utdata adding new entry utname=sray-server,o=v1,o=utdata adding new entry utname=desktops,utname=sray-server,o=v1,o=utdata adding new entry utname=users,utname=sray-server,o=v1,o=utdata adding new entry utname=logicalTokens,utname=sray-server,o=v1,o=utdata adding new entry utname=rawTokens,utname=sray-server,o=v1,o=utdata adding new entry utname=multihead,utname=sray-server,o=v1,o=utdata adding new entry utname=container,utname=sray-server,o=v1,o=utdata adding new entry utname=properties,utname=sray-server,o=v1,o=utdata adding new entry cn=utadmin,utname=sray-server,o=v1,o=utdata adding new entry utname=smartCards,utname=sray-server,o=v1,o=utdata adding new entry utordername=probeorder,utname=smartCards,utname=sray-server,o=v1,o=utdata adding new entry utname=policy,utname=sray-server,o=v1,o=utdata adding new entry utname=resDefs,utname=sray-server,o=v1,o=utdata adding new entry utname=prefs,utname=sray-server,o=v1,o=utdata adding new entry utPrefType=resolution,utname=prefs,utname=sray-server,o=v1,o=utdata adding new entry utPrefClass=advisory,utPrefType=resolution,utname=prefs,utname=sray-server, o=v1,o=utdata Added 18 new LDAP entries. Creating Sun Ray Server Software Configuration ... Adding user account for 'utwww' (ut admin web server user) ...done Sun Ray Web Administration enabled to start at system boot. Starting Sun Ray Web Administration... See /var/opt/SUNWut/log/utwebadmin.log for server logging information. Unique "/etc/opt/SUNWut/gmSignature" has been generated. Restarting Sun Ray Data Store ... .. Thu Dec 29 09:52 : utdsd starting Adding user admin ... User(s) added successfully! Creating new Sun Ray Kiosk Mode configuration ... Validating new user ids. Validating new user accounts. Creating kiosk group utkiosk Configuring new kiosk user accounts: ......................... 25 users configured *********************************************************** The current policy has been modified. You must restart the authentication manager to activate the changes. *********************************************************** Enter groupname for Windows Connector [utwc] The group 'utwc' already exists. A dedicated group should be used for SRWC. Use existing group anyway (Y/N) [Y] Creating required LDAP schema ... adding new entry utname=remoteclient,utname=sray-server,o=v1,o=utdata adding new entry utname=users,utname=remoteclient,utname=sray-server,o=v1,o=utdata Done. ***************************************************************************** A restart of Sun Ray services is required before the Sun Ray Connector for Windows Operating Systems is used. Please run : /opt/SUNWut/sbin/utstart Note that this will *NOT* terminate any sessions. ***************************************************************************** Configuration of Sun Ray Server Software has completed. Please check the log file, /var/adm/log/utconfig.2011_12_29_09:47:26.log, for errors. ================================================================== === Configuring access policy - utpolicy Enter policy specification as if on utpolicy command line: [-a -g -z both -M] The authentication manager must be restarted for changes to take effect. If a significant policy change has been made then a cold restart must be initiated with the following command, note that all existing sessions will be terminated: /opt/SUNWut/sbin/utstart -c If a minor policy change was made then it is not necessary to terminate existing sessions and a warm restart is sufficient by executing the following command: /opt/SUNWut/sbin/utstart ================================================================== === Configuring firmware downloads - utfwadm Do you want to configure Firmware downloads for Sun Ray clients? (Y/N) [Y] ================================================================== === Enabling LAN access - utadm Do you want to enable LAN access for Sun Ray clients at this time? (Y/N) [N] ### Turning on Sun Ray LAN connection NOTE: utstart must be run before LAN connections will be allowed ================================================================== === Starting Sun Ray Software - utstart A cold restart has been initiated... messages will be logged to /var/opt/SUNWut/log/messages.
The Windows connector feature enables you to provide Windows remote desktop services on Sun Ray Clients. Sun Ray Software provides a number of Windows connector components that you should install on a Windows system to improve the performance and functionality of the remote desktop services.
By default, remote desktop services is not enabled on a Windows system, so you must specifically enable it. See the Windows documentation for details.
This procedure provides the steps to install the Windows connector components on a Windows system:
USB redirection - Enables access to USB devices connected to a Sun Ray Client from a Windows session.
Multimedia redirection - Enhanced performance for Windows Media Player.
Adobe Flash acceleration - Enhanced playback capabilities for Adobe Flash content.
Audio/video synchronization - Enhanced audio and video synchronization for multimedia content.
Audio input - Enables audio recording on a Sun Ray Client from a Windows session.
Client Information Agent - Enables the client name to be updated across hotdesking and to provide the ability to execute actions on disconnects and reconnects of a Windows session.
If you want to install the Sun Ray Connector Windows components
by using the *.msi
files, you can use a
srs-winstaller.exe /S
/D=c:path
to extract the
*.msi
files from the
srs-wininstaller.exe
executable.
To bypass the installation UI, you can run srs-winstaller /S from the command line.
The Adobe Flash acceleration and Audio/video synchronization components require hardware that supports the Windows Performance Counter API. If the Windows Performance Counter API is not working properly, the components might fail to load or behave unexpectedly. In one known example, this problem occurs when a computer has the AMD Cool'n'Quiet technology enabled in the BIOS, which is documented in http://support.microsoft.com/kb/895980.
Log in to the Windows system as Administrator.
If you plan to install the USB redirection component on a Virtual Machine (VM), you must add USB drivers on some VMs if they do not provide drivers by default. See Section 18.6.5, “How to Add USB Drivers to a Virtual Machine” for details.
Make sure the Windows system has access to the Sun Ray Connector Windows Components installer in the unzipped Sun Ray Software media pack.
media_pack_image
/Components/20-SRWC/Content/Sun_Ray_Connector_Windows_Components_2.5
Copy the srs-winstaller.exe
file to the
Windows system.
Double-click the srs-winstaller
icon to
start the Sun Ray Connector Windows Components Setup Wizard.
Review the License Agreement and click I
Agree
.
Choose which components you want to install and click
Install
.
Click Finish
once the installation
has finished.
Restart the Windows system if instructed.
Go to the following sections (next steps) based on the features you installed.
The multimedia redirection component does not include an audio/video demuxer for MPEG-2 and H.264 video streams. To ensure that video is accelerated, download and install a third-party or freeware solution, such as the MatroskaSplitter freeware.
For Adobe Flash videos, users must enable the "Third party browser extensions" option in Internet Explorer, which is located in the Advanced tab of Tools->Internet Options.
For audio to work properly, the Sun Ray audio driver must be set as the default. If users have changed their default audio driver, they must perform the following procedure to make the Sun Ray audio driver the default.
From the Windows Desktop, choose
Settings->Control Panel
.
Click Sounds & Audio Devices
.
Click the Audio
tab.
If the Sun Ray RDP Audio Driver is not the default,
select it and click Apply
.
Close your browser and reopen it.
Under MyComputer
, choose
Properties->Hardware->Device Manager
to check if the utSrServerBus
entry is
displayed under the System devices
section.
See Figure 3.2, “Verifying USB Redirection Installation” for
an example.
For information about how to verify that USB redirection is working from a new Windows session, see Section 18.6.6.1, “How to Verify that USB Redirection is Active”.
The srs-winstaller.exe executable is an
archive, which extracts two .msi
files
into a temporary directory and then transfers control to the
Microsoft Windows installer. If the installed Windows
Connector Components software needs to be repaired, the
.msi
files may no longer be available.
There are two ways to repair the Windows Connector Components software. The easiest method is to uninstall the software using the add/remove interface and then reinstall using the procedure above.
The other repair method is to select the Windows Connector
Components in the add/remove interface and click Repair. If
the repair process requests the location of the
.msi
files, use the following procedure
to extract the files from the
srs-winstaller.exe executable:
Create a new directory with no blanks in the path or name.
The example in this procedure uses
c:\srwc
).
In a command shell window, run the following command:
srs-winstaller.exe /S /D=c:\srwc
The .msi
files are now available in
the c:\srwc
directory.
The utsetup command enables you to install and configure a Sun Ray server with the Sun Ray Software. You can then use the created response files to install and configure other servers. See Section 3.2.3, “Automating Sun Ray Software Installations” for more information about automating Sun Ray Software installations.
Figure 3.3, “Cloning a Sun Ray Server” shows how you can use the utsetup command to clone Sun Ray servers.
The *.utdialog_responses.props
files may
contain passwords that a malicious user could potentially
decode if read, so make sure to use sufficient security
precautions when copying them. For example, the files should
have secure permissions (not readable by group or "other"),
and you should remove the files from their temporary locations
after you complete the configuration.
From the unzipped Sun Ray Software media pack, run the utsetup command to install and configure a Sun Ray server.
The responses you provide are saved in the
/var/opt/SUNWut/utdialog.d/*.utdialog_responses.props
files.
Copy the response files to another server. In this example,
the files are copied to Server B's /tmp
directory.
From the unzipped Sun Ray Software media pack, run the utsetup -a -D /tmp command to clone the installation and configuration on the server that you created in Step 1.
For members of the same failover group, you can typically
apply the configuration without changes. For a new failover
group, you may need to edit the response files to create a
new configuration (for example to specify a new primary and
secondaries for replication). The
utdialog_responses.props(5)
man page
gives detail about the format of the files.
Another way to use the utsetup command is to quickly install and configure a server with the default settings.
Install, configure, and activate the basic Sun Ray Software
product features for standalone use (no failover group
configuration) with a minimum of user interaction required
(JRE 1.6 must be installed at /usr/java
before proceeding).
utsetup -d
Complete the configuration:
Optionally configure the system in a failover group (if you did not specify identical administration passwords with the utsetup command for each system, then you must run the utpw command at this time).
# utgroupsig
# utreplica -psecondary-server1
[secondary-server2
...]
or
# utreplica -s primary-server
Optionally configure the kiosk functionality.
# utconfig -k -d
Optionally configure the browser web administration
interface (Apache Tomcat must be installed at
/opt/apache-tomcat
before
proceeding).
utconfig -w -d
Configure the Sun Ray network services.
# utadm -L on
or
# utadm -A subnet
or
# utadm -a interface
Start the Sun Ray services
# utstart
To remove Sun Ray Software in its entirety, follow this procedure.
Log in as the superuser of the Sun Ray server.
Open a shell window and change to the
/opt/SUNWut/sbin
directory.
# cd /opt/SUNWut/sbin
If you are removing Sun Ray Software from a server in a failover group, disable Sun Ray Client firmware updates.
See Section 14.11, “How to Disable All Sun Ray Client Firmware Updates” for details.
Remove the replication configuration.
# ./utreplica -u
Remove the Sun Ray network interfaces.
# ./utadm -r
Unconfigure Sun Ray Software.
# ./utconfig -u
Answer y to all of the prompts.
Uninstall Sun Ray Software.
# cd / # /opt/SUNWut/sbin/utinstall -u
Answer y to all of the prompts.
Repeat the steps in this procedure for all remaining Sun Ray servers.
If during an installation, upgrade, or uninstall the utinstall script returns an error, refer to the following table for assistance.
Message | Meaning | Resolution |
---|---|---|
|
You called the |
The |
| Might occur for the installation of any application or patch if relevant packages have not been properly installed. | Verify that he component xxxxxx is present in the installation media directory path and has the correct permissions, then run the utinstall script again. |
| Some of the applications provided with Sun Ray Software are compatible only with certain versions of other applications. | Compatible and necessary applications are included with Sun Ray Software. Remove older versions, then run the utinstall script again. |
| None of the Sun Ray components are installed on this system. | No action is required as the product is not installed. |
| Some files were not properly replaced as part of the upgrade. | Manually copy the listed files from the directory, overwriting the newer files if applicable. |
Partition Name Space Required Space Available -------------- -------------- --------------- partition xxx yyy | Not enough disk space was allocated for partition. Repartition the disk and run utinstall again. |
Message | Meaning | Resolution |
---|---|---|
| The packages listed have not been properly removed. | Use the rpm -e command to remove each listed rpm manually, then run utinstall -u again. |
| Removal of Sun Ray Software was incomplete. | Check the log file for the package that started the problem and manually remove it with the rpm -e command, then run utinstall -u again. |
Message | Meaning | Resolution |
---|---|---|
|
The |
Verify that the installation administration file
exists ( |
For SPARC platforms: | You are attempting to install Sun Ray Software onto an Oracle Solaris version that does not support the Sun Ray Software release. | Upgrade to the supported version 10 of the Oracle Solaris OS before installing Sun Ray Software. |
For x86 platforms: | You are not running a valid OS release for this platform. | Upgrade to the supported version 10 of the Oracle Solaris OS before installing Sun Ray Software. |
|
Other unrelated files were found in the
| Remove unrelated files from the directory. |
| You decided not to restore from the indicated tar file. | Remove the tar file before running utinstall again. |
| The utinstall script failed to preserve existing configuration files. | Either exit and manually preserve these files or just continue. |
| The packages listed have not been properly removed. | Use the pkgrm command to remove each listed package manually, then run utinstall -u again. |
| Removal of Sun Ray Software was incomplete. | Check the log file for the package that started the problem and manually remove it with the pkgrm command, then run utinstall -u again. |
The following files are modified during utadm:
/etc/inet/hosts
/etc/inet/networks
/etc/inet/netmasks
/etc/inet/dhcpsvc.conf
# including
all DHCP-related files
/etc/nsswitch.conf
/etc/hostname.
intf
The following files are modified during Sun Ray service startup:
/etc/inet/services
/etc/inet/inetd.conf
The following files are modified during utconfig:
/etc/passwd
/etc/shadow
/etc/group
After installation, the following files are updated upon reboot:
/etc/syslog.conf
/etc/pam.conf
The following files are modified during utadm:
/etc/dhcpd.conf
/etc/nsswitch.conf
/etc/opt/SUNWut/net/dhcp/SunRay-options
/etc/opt/SUNWut/net/dhcp/SunRay-interface-eth1
/etc/opt/SUNWut/net/hostname.eth1
/etc/opt/SUNWut/net/networks
/etc/opt/SUNWut/net/netmasks
/etc/hosts
The following files are modified during utconfig:
/etc/passwd
/etc/shadow
/etc/group
In addition, display files are created for each Sun Ray Client in the following directories:
/etc/gdm/PreSession
/etc/gdm/PostSession
/etc/gdm/Init
/etc/gdm/PostLogin