3.1. Product Requirements

3.1.1. Operating System Requirements
3.1.2. Sun Ray Operating Software
3.1.3. Windows Remote Desktop Support
3.1.4. Feature Differences Between Oracle Solaris and Oracle Linux Platforms
3.1.5. Differences Between Oracle Solaris 10 and Oracle Solaris 11 Platforms
3.1.6. Disk Space Requirements
3.1.7. Oracle Solaris 10 Prerequisites
3.1.8. Oracle Solaris 11 Prerequisites
3.1.9. Oracle Linux Prerequisites
3.1.10. Java Runtime Environment (JRE) Requirements
3.1.11. Sun Ray Admin GUI Web Server Requirements
3.1.12. Sun Ray Admin GUI Web Browser Requirements
3.1.13. Sun Ray Data Store Port Requirements
3.1.14. Ports and Protocols

This section provides the product requirements for the Sun Ray Software 5.4 release.

3.1.1. Operating System Requirements

Table 3.1, “Supported Sun Ray Software Operating Systems” lists the supported Sun Ray Software operating systems for the Sun Ray Software 5.4 release.

Table 3.1. Supported Sun Ray Software Operating Systems

Operating System

Supported Releases

Oracle Solaris 10 on SPARC and x86 platforms

  • Oracle Solaris 10 8/11 or later

  • Oracle Solaris 10 8/11 or later with Trusted Extensions

Oracle Solaris 11 on SPARC and x86 platforms

  • Oracle Solaris 11.1 or later

  • Oracle Solaris 11.1 or later with Trusted Extensions

Oracle Linux on x86 platform (64-bit)

  • Oracle Linux 5.8

  • Oracle Linux 6.3


Sun Ray Software is supported and can be installed in an Oracle virtualized environment. If you encounter a problem when using an unsupported virtualization environment, you may be asked to demonstrate the issue on a non-virtualized operating system to ensure the problem is not related to the virtualization product.

Both Oracle Solaris and Oracle Solaris with Trusted Extensions can use zones to permit multiple virtualized operating system environments to coexist in a single instance of Oracle Solaris, allowing processes to run in isolation from other activity on the system for added security and control. Sun Ray Software is supported only in the global zone.

Note

Oracle products certified on Oracle Linux are also certified and supported on Red Hat Enterprise Linux due to implicit compatibility between both distributions. Oracle does not run any additional testing on Red Hat Enterprise Linux products.

To prepare the servers before installing the Sun Ray Software, see Section 3.1.7, “Oracle Solaris 10 Prerequisites”, Section 3.1.8, “Oracle Solaris 11 Prerequisites”, and Section 3.1.9, “Oracle Linux Prerequisites”.

3.1.2. Sun Ray Operating Software

The Sun Ray Operating Software 11.1.1 for Sun Ray Clients is required for many of the new Sun Ray Software 5.4 features. Sun Ray Operating Software is the official name of the Sun Ray Client firmware.

See Section 3.2.4, “Installing Firmware Before Sun Ray Software Installation” for details on how to install the Sun Ray Operating Software on Sun Ray Clients.

3.1.3. Windows Remote Desktop Support

The following Windows remote desktops are supported with Sun Ray Software:

  • Windows XP Professional with SP2 (64-bit)

  • Windows XP Professional with SP3 (32-bit)

  • Windows Server 2003 R2 SP2 Enterprise Edition (32-bit and 64-bit)

  • Windows 7 SP1 Enterprise Edition (32-bit and 64-bit)

    Sun Ray Software is tested on and supports Windows 7 SP1 Enterprise Edition. Windows 7 Professional, Ultimate, or other Enterprise editions can be used, but in the event of an issue, you must be able to reproduce the issue in Windows 7 SP1 Enterprise Edition.

    Multiple monitor and audio recording (input audio) are only available in Windows 7 Ultimate and Enterprise editions. Windows 7 Professional does support a single desktop spanned across multiple monitors (spanned mode).

  • Windows Server 2008 R2 SP1 Enterprise Edition (64-bit)

  • Windows 8 Enterprise Edition (32-bit and 64-bit)

    Sun Ray Software is tested on and supports Windows 8 Enterprise Edition. Windows 8 Professional can be used, but in the event of an issue, you must be able to reproduce the issue in Windows 8 Enterprise Edition.

  • Windows Server 2012 (64-bit)

Table 3.2, “Supported Features for Windows Remote Desktops” shows what features are supported for each Windows remote desktop. Some Windows releases require a Windows connector component to be installed for specific feature support. For detailed information, see Section 3.2.7, “How to Install the Windows Connector Components on a Windows System”.

Table 3.2. Supported Features for Windows Remote Desktops

 

Windows XP SP2 (64-bit)

Windows XP SP3 (32-bit)

Windows Server 2003 R2 SP2 (32-bit/64-bit)

Windows 7 SP1 (32-bit/64-bit)

Windows Server 2008 R2 SP1 (64-bit)

Windows 8 (32-bit/64-bit)

Windows Server 2012 (64-bit)

Video Acceleration

USB Redirection

Audio Input

Enhanced Network Security

Session Directory/Session Broker

n/a

n/a

n/a

n/a

Smart Card Services


Note

Video acceleration support is dependent on the Windows desktop version, the application being used, and the client used to connect to the desktop. See Section 17.5, “Video Acceleration” for details.

3.1.4. Feature Differences Between Oracle Solaris and Oracle Linux Platforms

The following Sun Ray Software features are not supported on a Sun Ray server running the Oracle Linux platform.

  • Using mass storage devices without the USB redirection Windows component provides much lower performance on Oracle Linux than Oracle Solaris due to the design of the Oracle Linux mass storage subsystem. Use USB redirection for optimum performance with mass storage devices.

  • Predefined kiosk session types are not available, which provide a desktop, a window manager, and the ability to configure a set of applications. Sun Java Desktop (JDS), Release 3, is an example of a predefined session type provided for Oracle Solaris 10. See Section 10.1, “Kiosk Overview” for more information.

  • The CCID IFD handler, which provides access to external CCID-compliant USB smart card readers connected to desktop clients, is not supported on Sun Ray servers running Oracle Linux.

  • The scbus v1 smart card protocol is not supported on Sun Ray servers running Oracle Linux.

  • When hotdesking without smart cards, the Options menu in the NSCM login screen is not available for Oracle Linux. This includes both the QuickLogin and Exit options. See Section 9.2.3, “How to Log in to an NSCM Session” for details.

3.1.5. Differences Between Oracle Solaris 10 and Oracle Solaris 11 Platforms

The following list describes the differences between a Sun Ray server running the Oracle Solaris 10 and Oracle Solaris 11 platforms.

  • Predefined kiosk session types are available only for Oracle Solaris 10. There are no predefined kiosk session types for Oracle Solaris 11.

  • IP MultiPathing (IPMP) is supported only on Sun Ray servers running Oracle Solaris 10 in a shared network configuration (LAN with fully-routed subnets).

3.1.6. Disk Space Requirements

Table 3.3, “Disk Space Requirements” lists the disk space requirements for specific directories.

Table 3.3. Disk Space Requirements

Default Installation Path

Requirements

/

1 Mbyte

/etc/opt/SUNWut/srds

0.1 Mbytes

/opt

70 Mbytes

/opt/SUNWut/srds

4.6 Mbytes

/var/adm/log (Oracle Solaris)

5 Mbytes

/var/log (Oracle Linux)

2.5 Mbytes

/var/opt/SUNWut

Allow enough disk space for the data store and log files. For 1,000 entries, allocate roughly 1.5 Mbytes of disk space, 64 Mbytes of RAM, and 528 Mbytes of swap space.

/var/tmp

5 Mbytes


3.1.7. Oracle Solaris 10 Prerequisites

This section describes the prerequisites when using Oracle Solaris 10 for a Sun Ray server:

  • The Entire Distribution software cluster is required and must be installed.

  • The latest Recommended Patchset must be installed prior to the Sun Ray Software installation, which you can download from My Oracle Support.

  • The Common Desktop Environment (CDE) might not be available in a future Oracle Solaris 10 release. Users should migrate to the Java Desktop System. CDE will not be supported on future versions of Sun Ray Software when CDE is officially removed from the Oracle Solaris 10 release.

  • To increase the performance of the Sun Ray Clients, make the following configuration update:

    1. Add the following line to the Sun Ray server's /etc/system file.

      set hires_tick=1

      For more information about this setting, see Section 20.3, “How to Improve Sun Ray Client Performance by Decreasing Buffering on the Network Switch (Oracle Solaris)”.

    2. Reboot the Sun Ray server.

3.1.8. Oracle Solaris 11 Prerequisites

This section describes the prerequisites when using Oracle Solaris 11 for a Sun Ray server:

3.1.9. Oracle Linux Prerequisites

This section describes the prerequisites when using Oracle Linux for a Sun Ray server:

  • For Oracle Linux 5, the default package set is required for Sun Ray Software and must be installed on the Sun Ray server.

  • For Oracle Linux 6, the Desktop package set is required for Sun Ray Software and must be installed on the Sun Ray server.

  • Additional packages are required, which you can install using the utpkgcheck command provided in the Sun Ray Software media pack. See Section 3.1.9.1, “How to Install Required Packages Using utpkgcheck for details.

  • The firewall and SELinux services must be disabled.

    For Oracle Linux 6, you must disable these services after installing the operating system. To disable firewall services, use the Firewall Configuration dialog (System > Administration > Firewall). To disable SELinux services, edit the /etc/selinux/config file as follows and restart the server:

    SELINUX=disabled
  • For Oracle Linux 6, optimize the shared memory used by PulseAudio. Add the following line to the /etc/pulse/client.conf file on the Sun Ray server:

    shm-size-bytes = 131072

    See Section 13.1.8, “Audio Output Troubleshooting (Oracle Solaris 11 and Oracle Linux 6)” for details about PulseAudio.

3.1.9.1. How to Install Required Packages Using utpkgcheck

The utpkgcheck command uses the yum command to retrieve and install the required packages for Sun Ray Software, which relies on the server being configured with Oracle Unbreakable Linux Network (ULN) or the Oracle Public Yum Server. For servers running Oracle 6, you must also configure yum to include the multiseat GDM repository, which is an enhanced version of GDM that supports multi-seat capability required in Sun Ray environments.

If the server does not have the ULN or Public Yum Server configured, utpkgcheck will try to install the necessary packages from the automounted Oracle Linux DVD if available. This option is useful only for servers running Oracle Linux 5, because the multiseat GDM channel is not required.

Use the following steps to install the required packages:

  1. Make sure yum is configured properly on the server, as described in Section 3.1.9.2, “Configuring ULN Channels for utpkgcheck and Section 3.1.9.3, “Configuring Public Yum Repositories for utpkgcheck.

    Note

    Make sure to unsubscribe from the specified *_latest ULN channels or disable the specified *_latest yum repositories as instructed. Otherwise, the server will update to a later version of Oracle Linux that is not supported by this version of Sun Ray Software. If there are any Oracle Linux bugs affecting Sun Ray Software that have been fixed through an Oracle Linux patch, you must use ULN to get those fixes.

  2. Install the required packages on the Oracle Linux server:

    # utpkgcheck -i

    In some instances, you must reboot the system if the following warning message is displayed:

    WARNING: System must be rebooted in order to complete installation.
  3. Update the server with the latest package versions.

    # yum update
  4. Reboot the system.

    # reboot
  5. (Oracle Linux 6 only). To enable root login to GDM, comment out or remove the following line from the /etc/pam.d/gdm file.

    auth required pam_succeed_if.so user != root quiet

    The multiseat GDM repository disables root login by default.

3.1.9.2. Configuring ULN Channels for utpkgcheck

Before running utpkgcheck, make sure the server is subscribed to the required channels on ULN. For information about ULN, see the Oracle Linux Unbreakable Linux Network User's Guide.

After you have enabled and disabled repositories, use the yum clean all command to clear the yum cache, and then use the yum repolist command to check that you have enabled the correct repositories.

ULN Channel Subscriptions for Oracle Linux 6 Platforms

  • Unsubscribe from the following channels:

    Channel Label

    Channel Name

    ol6_x86_64_latest

    Oracle Linux 6 Latest (x86_64)

    ol6_x86_64_UEK_latest

    Latest Unbreakable Enterprise Kernel for Oracle Linux 6 (x86_64)

  • Subscribe to the following channels:

    Channel Label

    Channel Name

    ol6_u3_x86_64_patch

    Oracle Linux 6 Update 3 Patch (x86_64)

    ol6_u3_x86_64_base

    Oracle Linux 6 Update 3 installation media copy (x86_64)

    ol6_x86_64_UEK_base

    Unbreakable Enterprise Kernel for Oracle Linux 6 (x86_64)

    ol6_x86_64_gdm_multiseat

    Oracle Linux 6 GDM Multiseat

ULN Channel Subscriptions for Oracle Linux 5 Platforms

  • Unsubscribe from the following channels:

    Channel Label

    Channel Name

    el5_x86_64_latest

    Enterprise Linux 5 Latest (x86_64)

    ol5_x86_64_latest

    Oracle Linux 5 Latest (x86_64)

    ol5_x86_64_UEK_latest

    Latest Unbreakable Enterprise Kernel for Oracle Linux 5 (x86_64)

  • Subscribe to the following channels:

    Channel Label

    Channel Name

    ol5_u8_x86_64_patch

    Oracle Linux 5 Update 8 Patch (x86_64)

    ol5_u8_x86_64_base

    Oracle Linux 5 Update 8 installation media copy (x86_64)

    ol5_x86_64_UEK_base

    Unbreakable Enterprise Kernel for Oracle Linux 5 (x86_64)

3.1.9.3. Configuring Public Yum Repositories for utpkgcheck

Before running utpkgcheck, make sure the server has the appropriate repositories configured for the Public Yum Server. For information about the Public Yum Server, see http://public-yum.oracle.com. For Oracle Linux 6, see the Oracle Linux Administrator's Solutions Guide for Release 6.

Note

For Oracle Linux 6 platforms, you must download the latest yum configuration file (http://public-yum.oracle.com/public-yum-ol6.repo) and copy it to the /etc/yum.repos.d directory on the server. The latest yum configuration file contains entries for the required Oracle Linux 6 GDM Multiseat repository.

After you have enabled and disabled repositories, use the yum clean all command to clear the yum cache, and then use the yum repolist command to check that you have enabled the correct repositories.

Repository Configuration for Oracle Linux 6 Platforms

  • Disable the following repositories:

    Repository

    Name

    [ol6_latest]

    Oracle Linux 6 Latest (x86_64)

    [ol6_UEK_latest]

    Latest Unbreakable Enterprise Kernel for Oracle Linux 6 (x86_64)

  • Enable the following repositories:

    Repository

    Name

    [ol6_u3_base]

    Oracle Linux 6 Update 3 installation media copy (x86_64)

    [ol6_UEK_base]

    Unbreakable Enterprise Kernel for Oracle Linux 6 (x86_64)

    [ol6_gdm_multiseat]

    Oracle Linux 6 GDM Multiseat (x86_64)

Repository Configuration for Oracle Linux 5 Platforms

  • Disable the following repositories:

    Repository

    Name

    [ol5_latest]

    Oracle Linux 5 Latest (x86_64)

    [ol5_UEK_latest]

    Latest Unbreakable Enterprise Kernel for Oracle Linux 5 (x86_64)

  • Enable the following repositories:

    Repository

    Name

    [ol5_u8_base]

    Oracle Linux 5 Update 8 installation media copy (x86_64)

    [ol5_UEK_base]

    Unbreakable Enterprise Kernel for Oracle Linux 5 (x86_64)

3.1.10. Java Runtime Environment (JRE) Requirements

Sun Ray Software 5.4 Admin GUI requires a 32-bit implementation of a Java(TM) 2 Platform, Standard Edition JRE(TM) of at least 1.6. To check what JRE version is installed on your system, use the following command:

# java -version

It is recommended that you install the latest Java release, which is available at http://www.oracle.com/technetwork/java/javase/downloads. A supported version of JRE is bundled in the unzipped Sun Ray Software media pack in the Supplemental directory.

The Sun Ray Software installation script assumes JRE is installed in the /usr/java directory by default. For example, if you want to accept the default when installing the Sun Ray Software on an Oracle Linux server, install JRE 1.6 or later on the server and then create a symlink from /usr/java to the newly created jre directory. The following sequence of commands installs the JRE in the /usr directory and creates a symbolic link from /usr/java to the new jrel.6.0_version directory.

# cd /usr
# Supplemental-dir/Java_Runtime_Environment/Linux/jre-6uversion-linux-i586.bin
# ln -s jre1.6.0_version /usr/java
Note

A 64-bit JRE is not suitable for use with Sun Ray Software. The 32-bit JRE is required, even when the platform is capable of supporting a 64-bit JRE.

Note

If you are using JRE version 1.6 on a server running Oracle Solaris 11, a Secure Connection Failed error may occur when launching the Admin GUI through a secure URL. To resolve this problem, either update the JRE version to 1.7 or disable TLS 1.0 encryption in the browser's preferences.

3.1.11. Sun Ray Admin GUI Web Server Requirements

The Sun Ray Administration Tool (Admin GUI) requires that a Web server be installed and running on each Sun Ray server. The Admin GUI must be hosted in a web container that supports the JavaServlet 2.4 and JavaServer Pages 2.0 specification. The Apache Tomcat 5.5 Web container implements these standards and runs on any operating system that has a Java Runtime Environment (JRE).

The utconfig script prompts for the location of an Apache Tomcat HTTP Server and asks whether it should be configured automatically.

  • To configure the server automatically, supply the path and answer Yes.

  • To configure the HTTP server later by using the utconfig -w command, answer No.

The Sun Ray configuration script uses port 1660 for the Sun Ray Administration Tool (Admin GUI) by default. If this port is unavailable, you can configure a new port while running the utconfig command.

An Apache Tomcat 5.5 archive is included in the Sun Ray Software media pack under Supplemental/Apache_Tomcat. The most recent version of Tomcat 5.5 can be downloaded from http://tomcat.apache.org.

See How to Install Apache Tomcat for details.

3.1.11.1. How to Install Apache Tomcat

If Tomcat 5.5 is already installed on your system, you can omit the steps below and specify the path, if necessary, during the Sun Ray Software configuration.

  1. As superuser, open a shell window on the Sun Ray server.

    % su -
  2. Change to the Apache_Tomcat directory. For example:

    # cd media_pack_dir/Supplemental/Apache_Tomcat
    
  3. Extract the Tomcat archive into a suitable directory, such as /opt.

    For Oracle Solaris

    The Tomcat archive uses GNU tar extensions and must be untarred with a GNU-compatible version of the tar command, such as gtar.

    # /usr/sfw/bin/gtar -xvz -C /opt -f apache-tomcat-5.5.36.tar.gz

    For Oracle Linux

    # tar -xvz -C /opt -f apache-tomcat-5.5.36.tar.gz

    (Optional) Create a symbolic link to the default location for the Sun Ray Software installation script.

    # ln -s apache-tomcat-5.5.36 /opt/apache-tomcat

3.1.12. Sun Ray Admin GUI Web Browser Requirements

The Sun Ray Administration Tool (Admin GUI) has been tested and works with the default browsers provided by the operating systems listed in Table 3.1, “Supported Sun Ray Software Operating Systems”.

3.1.13. Sun Ray Data Store Port Requirements

When you configure a new Sun Ray server in a failover environment that uses Sun Ray Software 5.4 only, service port 7012 is used by default.

If you already have an LDAP (Lightweight Data Access Protocol) server configured on the Sun Ray server, it can coexist with the Sun Ray data store. However, it must not use port 7012, which is reserved for use by the Sun Ray data store.

If you configure a new Sun Ray server in a failover group with mixed versions of Sun Ray Software, you must make sure that the primary server is running Sun Ray Software 5.4.

If the secondary server is running Sun Ray Software 5.4, no special care is required. The utreplica utility automatically synchronizes with the port number on the primary.

Note

Although configuring mixed failover groups consisting of servers running various versions of Sun Ray Server Software is possible, this practice is discouraged. For more information, see Chapter 6, Failover Groups.

3.1.14. Ports and Protocols

The following section summarize Sun Ray system port and protocol usage.

The range of dynamic/UDP and dynamic/TCP ports on the server is constrained to the range defined by the utservices-low and utservices-high UDP service definitions, whose default values in /etc/services are 40000 and 42000 respectively. This range should not be redefined to constrain ports too tightly. The range of ports must be sufficient to provide several ports per connected Sun Ray Client.

Ranges used by the client include the following:

  • Dynamic/TCP ports on the client are in the range 32768-65535.

  • Dynamic/UDP ports on the client are in the range 4096-65535.

  • ALP rendering traffic (ALP-RENDER) always uses a UDP port number greater than 32767 at the client.

3.1.14.1. Sun Ray Client-to-Server Ports and Protocols

Table 3.4, “Sun Ray Client-to-Server Ports and Protocols” lists the Sun Ray Client-to-server ports and protocols. In the table, a double-headed arrow in the Flow column indicates the direction of the initial packet. In most cases, the client (a Sun Ray Client or Oracle Virtual Desktop Client) initiates the interaction.

Table 3.4. Sun Ray Client-to-Server Ports and Protocols

Client Port / Flow

Protocol

Server Port / Flow

Peer

Importance/Comments

66/UDP (BOOTPC/DHCPC)

broadcast=>>

unicast=>>

DHCP

67/UDP (BOOTPS/DHCPS)

<=broadcast

<=unicast

DHCP Service

Mandatory.

Network and configuration parameter discovery.

Dynamic/UDP

unicast=>>

TFTP

69/UDP (TFTP)

<=unicast

TFTP Service

Recommended.

Firmware download (Configuration parameter download).

Dynamic/UDP

unicast=>>

DNS

53/UDP (domain)

<=unicast

DNS Service

Optional.

For server name lookups.

514/UDP (syslog)

unicast=>>

Syslog

514/UDP (syslog)

Syslog Service

Optional.

Event reporting.

Dynamic/TCP

unicast=>>

pcscd

4120/TCP (pcscd)

<=unicast

Sun Ray Server

Mandatory.

PC/SC-lite smart card service.

Used to be TCP port 5999.

Dynamic/UDP

broadcast=>>

ALP-DISCOVERY

7009/UDP (utauthd-gm)

<=unicast

Sun Ray Server

Optional.

On-subnet Sun Ray server discovery.

Dynamic/TCP

unicast=>>

ALP-AUTH

7009/TCP (utauthd)

<=unicast

Sun Ray Server

Mandatory.

Presence, control, status.

Dynamic/UDP with port number >= 32768

unicast=> or unicast=>> when NAT is in use

ALP-RENDER

Dynamic/UDP constrained by utservices-low and utservices-high

<<=unicast or <=unicast when NAT is in use

Sun Ray Server

Mandatory.

On-screen drawing, user input, audio.

5498/UDP

unicast=>>

ALP-AUDIO-IN

Dynamic/UDP constrained by utservices-low and utservices-high

Sun Ray Server

Optional.

Inbound audio.

Dynamic/TCP

unicast=>>

ALP-DEVMGR

7011/TCP (utdevmgr)

<=unicast

Sun Ray Server

Optional.

Device management.

Dynamic/TCP with port number >= 32768

unicast=>

ALP-DEVDATA

Dynamic/TCP constrained by utservices-low and utservices-high

<<=unicast

Sun Ray Server

Optional.

Device communication when accessing external device, including USB redirection.

7777/TCP

unicast=>

ALP-DEVDATA

Dynamic/TCP

<<=unicast

Sun Ray Server

Optional.

Device communication when accessing external devices connected to Sun Ray Clients running older firmware. Not used with USB redirection.

7013/UDP (utquery)

unicast=>

ALP-QUERY

Dynamic/UDP

<<=unicast

<<=broadcast

Any

Optional.

utquery support.


Note

Due to CR 12301209, the keyboard may become unresponsive to input. To work around this issue, allow ICMP messages to flow from the Sun Ray server to the client.

3.1.14.2. Sun Ray Server-to-Server Protocols

Table 3.5, “Sun Ray Server-to-Server Ports” lists the Sun Ray server-to-server ports. In the table, a double-headed arrow indicates the direction of the initial packet.

Table 3.5. Sun Ray Server-to-Server Ports

Sun Ray Server Port

Protocol

Port

Peer

Notes

<<=ARP=>>

All on subnet

IP-to-MAC mapping.

<<=ICMP ECHO=>

Any

Admin: presence.

Transient

SYSLOG/UDP unicast=>>

514 (SYSLOG)

Syslog Server

Status reporting, if required.

1660 (HTTP)

<<=HTTP/TCP=>

Transient

Localhost

Admin GUI, if configured.

1661 (HTTPS)

<<=HTTPS/TCP=>

Transient

Localhost

Admin GUI, if configured.

7007 (UTSESSIOND)

<<=UTSESSION/TCP=>

Transient

Any

Session members.

7007 (UTSESSIOND)

<<=UTSESSION/TCP=>

Privileged

Localhost

Session management.

7008 (UTRCMD)

<<=UTRCMD/TCP=>

Privileged

Sun Ray Group Member

Remote execution.

7009 (UTAUTHD)

<<=UTAUTHD-GM/UDP=>>

broadcast or multicast

7009 (UTAUTHD)

Sun Ray Server

Group discovery, if required.

7010 (UTAUTH-CB)

<<=UTAUTH-CB/TCP=>

Transient

Any

Admin: control and status.

7011 (UTDEVMGRD)

<<=UTDEVMGRD/TCP=>>

7011 (UTDEVMGR)

Sun Ray Group Member

Device control and status.

7011 (UTDEVMGR)

<<=UTDEVMGR/TCP=>

Transient

Any

Device clients.

7012 (UTDS)

<<=UTDS/TCP=>

Transient

Any

Data store, if required.

7014 (UTTSCPD)

<<=UTTSCPD/TCP=>

Privileged

Sun Ray Windows Connector from Localhost

Bridge/Proxy between Windows connector and the Sun Ray server.


3.1.14.3. Windows Connector

For basic Windows connector operations (RDP port access), the Windows server firewall needs TCP port 3389 open for inbound connections. The Sun Ray server (where the Windows connector is running) firewall needs TCP port 3389 open for outbound connections.

3.1.14.4. Multimedia Redirection

For multimedia redirection on Windows XP and Windows Server 2003 R2, the Windows server firewall must have a TCP port between 6000 and 10000 open for inbound connections. The Sun Ray server (where the Windows connector is running) firewall must have a TCP port between 6000 and 10000 open for outbound connections.