The only caveat to this is that typically, the arguments passed to the kiosk session are defined in the Sun Ray Admin GUI setup for the system-wide kiosk mode you choose, but since Meta Kiosk calls upon a large number of kiosks itself, this is no longer useful. To work around this, the script assumes that the parameteres you want for a specific kiosk mode are actually contained in the relevant "kiosk.
If username is present, then this name will appear in the login box where possible. If "target system" is specified this field will be stripped from the uttsc. Note that when you configure the uttsc kiosk mode, it is expected that you enter a system name at the end of the string. As such, Meta Kiosk expects this too. VDA: In case you need or want to register it. If this is used with VDA, then a default pool called VDA can be setup, unless you have already assigned the username a permanent virtual machine.
The next options are not not defined typically as kiosks. Their code is contained within the Meta Kiosk script itself:. Password will get written to a file and then the argument passed through, and although this is not dramatically secure, it allows for a quick demo of a MAC on a Sun Ray. A good VNC server to use is Vine. You may need to pass the port to the VNC service on the server as part of the system name, e. This is it! X An Xsession. This will run Xnest within the Sun Ray X session canvas.
Good for testing! Just good to have Meta Kiosk Workflow - how does a kiosk mode get chosen? The following diagram depicts the default actions chosen by the script based on the token conditions, i. Token registered or not and "Other Info" field contents:. Using the connector from Solaris is pretty easy as the client program utssc is basically an RDP client. Actually, rdesktop could also be used from Solaris in the same way.
However, I had to set up kiosk mode so the Sun Ray would go directly to a Windows server. I followed the docs on setting up kiosk mode utconfig -k, it kept failing until I ran it under truss then it succeeded….
Most of the docs talk about using a GUI, which I do not use and setting up kiosk for smart cards or non smart card users, etc. What I need to do was set up one specific Sun Ray to use kiosk mode, which was a little harder to find.
To do that I ran the following:. This took me a little while to get used to, but it worked well. Click on the advanced tab 2. Click on the kiosk mode tab 3.
Click on the edit button. We need to create our kiosk mode as the windows connector. Click on Ok. At this point you will have a kiosk mode defined and then you will need to tell the server when to use it. This is accomplished by using the the System Policy to turn Kiosk Mode on. See the Examples section below for an example of the utsetup output. 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 4. Repeat steps 2 through 4 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 file to each secondary server and use the utsetup command to replicate the failover group configuration.
This strategy reduces the time needed to re-enter the same configuration information and can minimize configuration errors.
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. Reboot the Sun Ray clients to download and install the new firmware provided by the Sun Ray server. Sun Ray Connector for Windows OS 3 Note — Data encryption is bidirectional except at the Low setting, which encrypts data only from the client to the server.
Typically, this feature is used to provide two-factor authentication with digital certificates or to permit the use of electronic signatures or other information stored page 23 Session Directory The Sun Ray Connector supports server session reconnection based on Session Directory, a database that keeps track of which users are running which sessions on which Windows Terminal Servers, and load balancing information.
Session Directory functionality enables Sun Ray Connector users to reconnect not only to an existing Sun Ray session but also to be reconnected automatically to the right Windows session.
Both IP address-based and token-based reconnection are supported; however, token based redirection requires the use of a hardware-based load balancer for Windows Terminal Servers configured as a server farm. Session Directory is an optional component that can be configured to use Microsoft proprietary or third-party load balancing products. Any file can be mounted and mapped from the Sun Ray environment to the Windows environment. Make sure that redirected UNIX folders do not contain any files that use these characters in their names.
Audio Support Users can play sound files on their Sun Ray desktops downstream audio with audio applications located on the Windows Terminal Server; however, recording from the Sun Ray desktop unit to the Windows Terminal Server upstream audio is not supported by the RDP Protocol and has therefore not been implemented. Serial devices can be connected either directly to the serial ports on a Sun Ray DTU or by means of a serial adapter.
Clipboard The Sun Ray Connector enables cut-and-paste text functionality between Windows applications and applications running on the Sun Ray desktop, whether Linux or Solaris versions. Licensing information is stored in the Sun Ray data store and can be retrieved and presented each time a Windows connection is made. For information on administering licenses, see the utlicenseadm man page.
See man also the Note on Note on page 8. Limitations Certain limitations, listed below, are caused by dependencies on other products. Cut-and-paste operations do not work from dtpad to Windows applications.
Cut-and-paste menu options do not work correctly in transfers from StarOffice applications. ThisTerminal is the case evenlicenses if the primary data store server is not used to host Sun Ray sessions.
Please confirm that OpenSSL is installed before proceeding. Consult the license agreements for the Microsoft operating system products you are using to determine which licenses you must acquire. The first character of the name must be alphabetic.
Do not add users to this group. Once you have created and named the group, follow the steps below to install the Sun Ray Connector. Open a shell shell window as superuser on the Sun Ray Ray server. If a File Manager window opens, close it. Enter the name name of the group you created created for this purpose purpose at the beginning beginning of this procedure, as below, then Continue: group-name 6.
Run the the automatic automatic configuration configuration script. Restart Sun Sun Ray services services if the the script asks you to to do so. Run the automatic automatic configuration configuration script. Accept the default default path, path, or supply a different different path, if applicable. Restart Sun Ray services if the script asks you to do so.
Uninstallation Procedure 1. Do you want to uninstall it and install Sun Ray Connector 2. Answer N to leave the existing installation in place. Answer Y to un uninstall install the the old version of Sun Ray Connector Connector software software and install the newer version. The existing Sun Ray data store is not removed or touched by the upgrade procedure. Run the automatic configuration configuration script again. The default screen size is x pixels. To display a session in full screen mode or to modify it in other ways, see the command line options listed in the uttsc man page.
For details on how to set up launchers, please consult the desktop documentation for your operating system.
Per-user Mode The user logs into a Sun Ray session with a smart card and opens a connection to a Windows session. The user removes removes the smart smart card card and reinserts reinserts it in the same DTU. The user removes the smart card and inserts it in a different DTU. In both cases, the user is instantly reconnected to the existing Windows session, and other features and services are unaffected.
Per-device Mode The user logs into a Sun Ray session with a smart card and opens a connection to a Windows session. The user is instantly reconnected to the existing Windows session. The Windows login screen prompts the user for username and password, after which the user is reconnected to the existing Windows session. Other features and services are similarly affected.
0コメント