The following procedure describes how to configure a Sun Ray server using the Sun Ray Software Admin GUI to automatically provide users direct access to their Windows desktops through the Citrix XenDesktop connector. This configuration is done through the kiosk mode feature and the Citrix XenDesktop session type.
This Citrix XenDesktop connector session type is provided through the following files:
/etc/opt/SUNWkio/sessions/srxc.conf
-
Session descriptor file
/opt/SUNWsrxc/bin/srxc
- Session script
file
/opt/SUNWsrxc/etc/services.csv
- Sample file for
the custom service menu
/opt/SUNWsrxc/lib/srxc.jar
- Sun Ray
Connector for Citrix XenDesktop Java archive
For more details about configuring Sun Ray Software, refer to the Sun Ray Software Administration Guide.
Install the Citrix XenDesktop connector on all the Sun Ray servers in the failover group.
See Section 2.1, “How to Install the Citrix XenDesktop Connector”.
Configure the Citrix XenDesktop environment for the Citrix XenDesktop connector.
See Chapter 3, Configuring the Citrix XenDesktop Environment
Log in to the Admin GUI.
Click the Advanced tab and Kiosk Mode sub-tab. Then click
Edit
.
Choose Citrix XenDesktop Session
from the
Session
(Session Type) menu.
(Optional) Modify the session parameters.
Add the required and any optional session type arguments to the
Arguments
field as follows:
session-type-arguments
[--uttsc-arguments
]
For a list of examples, see Section 4.1.1, “Example Citrix XenDesktop Session Arguments for Sun Ray Software”.
Table 4.1, “Required Kiosk Session Arguments for Citrix XenDesktop Connector” lists the required session arguments:
Table 4.1. Required Kiosk Session Arguments for Citrix XenDesktop Connector
Argument | Description |
---|---|
| Specifies the Windows domain of the virtual desktops, which is preselected in the login screen. You can provide a comma separated list, which displays a pull-down menu to the user. |
|
The URL of the Citrix XenDesktop Web Interface Server, either the IP address
or hostname. For example,
|
Table 4.2, “Optional Kiosk Session Arguments for Citrix XenDesktop Connector” lists the optional session arguments:
Table 4.2. Optional Kiosk Session Arguments for Citrix XenDesktop Connector
Argument | Description |
---|---|
| A URL to an image file used as the background for the Available Desktops and Desktop Login
dialog screens. Supported file formats are |
| Background color (RGB value) for the Citrix XenDesktop connector screen. When this option is
used with the The default background color is a gradient from 143,158,170 to 95,108,120. |
| Bottom color of background gradient (RGB value) for the Citrix XenDesktop connector screen.
This option requires the |
| Enable the custom service menu. See Section 4.1.3, “Custom Service Menu” for more information. |
| Proxy port number. Default value is |
| Proxy host. The value can be either a host name or an IP address, without the
|
| Screen resolution options for the Options menu. Format is
|
| Text color (RGB value). Example value is |
| An alternative for the Citrix Web Interface base URL. The default is
|
| A URL to an image file used as the wallpaper for the Citrix XenDesktop connector screen. Supported file
formats are |
Add any Windows connector (uttsc) arguments after the double dash (--
) to the
Arguments
field.
session-type-arguments
[--uttsc-arguments
]
All options located after the double dash (--
) are passed to the
Windows connector (uttsc command). Some uttsc
options are sent automatically and should not be specified. Do not include the following
uttsc options: -i
, -u
,
-d
, -p
, and -m
.
Click OK
.
Configure the server to use kiosk mode for card and non-card users.
Click the System Policy sub-tab on the Advanced menu.
Enable Kiosk Mode
for both card and
non-card users.
Make sure to disable the Mobile Sessions
(NCSM)
policy.
Click Save.
If you configured the server to use kiosk mode in the System Policy page, perform a cold restart of the Sun Ray server.
All new or restarted sessions matching the policy configuration to use kiosk mode will access the new session type.
This example connects to a Citrix XenDesktop Web Interface
Server with an IP address of 192.168.10.1
located in the desktop.local
domain:
-d desktop.local -s http://192.168.10.1
This example enables the audio input and USB redirection features of the Windows connector:
-d desktop.local -s http://192.168.10.1 -- -r soundin:high -r usb:on
Here are some additional notes about using graphics to customize the Citrix XenDesktop connector screen:
Instead of specifying the -B
or -W
options, you can place
images in the server's /opt/SUNWsrxc/custom
directory. The image
files must be named banner.png
or logo.png
,
respectively. Using the -B
or -W
options overrides
these defaults.
Graphics do not autoscale. You must provide graphics with the correct sizes.
Using graphics for the background and wallpaper may increase the load time of the Citrix XenDesktop connector interface.
When configuring the Citrix XenDesktop connector, you can use the -M
option to add menu items to the existing Options menu. New menu items can provide users
access to important applications, such as a web browser or a support tool.
You can customize the service menu through the server's
/opt/SUNWsrxc/etc/services.csv
file, where you need to provide a
single line of three arguments for each additional menu items. An example for providing a
Firefox menu item is show below:
# "App Name","App Exec","App Icon” "Firefox","/opt/firefox/firefox","file:///opt/firefox/chrome/icon/default/default16.png"
Here are descriptions for the three arguments. All arguments must be enclosed in parentheses and separated by a comma.
"App Name
" - The name of the menu item.
"App Exec
" - The absolute path to the executable file on the Sun Ray server.
"App Icon
" - (Optional) The URL to an image file used as an icon
for the menu item. The supported file format is png
and the image
size must have a resolution of 16x16. The URL can be either http://
or file://
. You may need to set a proxy for the kiosk session (using
the -P
option) if you specify an external URL.
Some applications require a window manager to operate properly, which means you must
create an additional script to run the application. You then need to point the
"
field to the script instead of
the application executable. The following example shows a script to run Firefox in a window
manager, which enables the user to enter text into the browser:App Name
"
# !/bin/sh # Start a window manager metacity & # Start Firefox /opt/firefox/firefox # Kill window manager once Firefox exits pkill -9 -u $USER metacity