Monday Feb 23, 2009

Keyboard layout problems with Sun Ray Connector for VMware VDM

[originally posted by Sarah Fortune 24-Feb-09]

There have been a couple of problems reported with international keyboards and the Sun Ray Connector for VMware VDM.

Some of the issues are:

  • Inability to enter characters that require Alt Gr combinations
  • When numlock is enabled the Enter, backspace and arrow keys don't work
  • In the Windows session, the keyboard is mapped as US

The first two are caused by a problem with Java and xkb. The solution is either to turn of the xkb extensions using this command '/opt/SUNWut/bin/utxconfig -k off' in the kiosk script: /etc/opt/SUNWkio/sessions/vdm/vdm. Using Java 6 also solves these problems, (you will need the Java 6 update 12 JDK, other versions can cause problems). You may need to change the kiosk script to point to the correct Java install. Change the line 'theJavaExec=/usr/java/bin/java' to point to the new location.

The third problem is due to the locale not being set for the windows session. You can set it in two ways. In the Sun Ray web administration go to Advanced > Kiosk Mode > Edit and enter the correct value for Locale. Or you can pass the locale as an argument to the kiosk script. On the same page add the argument -l <locale> after the double dashes.

The names of the locales can be found here. These solutions assume that everyone on the site is using the same keyboard layout. Other configurations will require some extra changes to the kiosk script, that's left as an exercise to the reader.

Thanks to Tomas O'Connor for the solutions.

Original Comments:

The issue with numlock is not limited to international keyboards. We have the described behavior with type 6 (on Ray 1) and type 7 (on Ray 2) keyboards, with SRSS 4.1 and 4.2 early access on Solaris/x86. We have not tested java 6 jdk, but the problem exists in jre 1.6.0_13-b03 shipped with early access.

Thanks for the note on this issue.

Posted by Darrel Hankerson on August 21, 2009 at 12:12 PM GMT

My mistake, jre 1.6.0_13-b03 does indeed fix the issue. says "some minor bug fixes, e.g. the Java 5/6 issue to solve some keyboard issues ( is gone" but this doesn't include the numlock issue in my earlier post.

Posted by Darrel Hankerson on August 21, 2009 at 01:55 PM GMT

Hi I've configurated the locale settings in the advanced tab of srss web interfaces but nothing happen

srss 4.2 srvc 1.2 locale = it_IT

what do you mean with " after double dashes" where?


Posted by Daniele on July 29, 2010 at 01:17 PM GMT 

Monday Feb 02, 2009

VirtualCenter unable to decrypt passwords

[originally posted by Sarah Fortune 3-Feb-09]

There is a long standing problem in VirtualCenter 2.5 where cloning fails with this error:

The VirtualCenter server is unable to decrypt passwords stored in the customization specification.

It happens apparently randomly, but can be caused by installing Internet Explorer 7 on the VirtualCenter host. There is an ongoing thread in VMware communities about it: There were rumours that the problem was going to be fixed in update 3, but it shows up in update 1, 2 and 3.

One of the solutions is to export the customisation spec, edit it so that the password is stored in plain text, and import it back into VirtualCenter.

If storing the password in plaintext isn't acceptable, replacing the SSL certificate in VirtualCenter can also fix the problem, provided the new certificate uses the password that is hardcoded into VirtualCenter.

Fix the problem by using plain text passwords
  1. Export the customisation spec, and edit the saved XML file.
  2. Locate the password section:
  3. Change the value <plainText>false</plainText> to <plainText>true</plainText>
    And <value>MJwe3zWdcKeAfZIB ... etc... </value> to the actual password, e.g. <value>Password01</value>.
    So the password section should look like this:
  4. Import the XML back into VirtualCenter as a new customisation spec.

Fix the problem by replacing the SSL ceritificate
  1. Follow these instructions to generate and install a new certificate. Be warned it a pretty long process and requires you to install software your VirtualCenter server.
  2. There is one step in the instructions needs to be modified, you have to change the password to the one that VirtualCenter expects.This command:
         openssl pkcs12 -export -in rui.crt -inkey rui.key -name rui -passout pass:vmware -out rui.pfx
    Should be replaced with:
        openssl pkcs12 -export -in rui.crt -inkey rui.key -name rui -passout pass:testpassword -out rui.pfx
  3. After you have replaced the certificate you will have to reconnect the ESX servers in VirtualCenter, and recreate the customisation specs. At this point it is safe to install Internet Explorer 7 on the server.

Wednesday Jan 07, 2009

Sun VDI: How to use virtual machines with multiple network adapters

[originally posted by Sarah Fortune 8-Jan-2009, last updated 04-Feb-2009. Latest update by Stephanie, Feb 2011, at]

Using virtual machines with more than one network interface can be problematic.  Sun VDI expects RDP to be available on the primary interface. If RDP is actually running on a different interface, then the machine may not be prepared successfully or assigned to users.

The problem arises in determining which exactly is the primary interface. The VMware documentation would lead us to believe that it is the primary interface listed in Windows. But, this is not the case. In fact, the primary interface is determined by the order of the network adapters in VirtualCenter. The network adapter with the highest number, usually the one which was added most recently, is the primary network adapter.

How to change the network of the primary adapter

  1. Edit the virtual machine settings in VirtualCenter.
  2. Select the network adapter with the highest number, e.g Network Adapter 3.
  3. This is the primary network interface. Change the network label to the appropriate network for RDP.
  4. You may need to adjust the other network adapters so that the virtual machine is assigned to all the correct networks.

VirtualCenter edit settings

Tuesday Dec 02, 2008

Troubleshooting Sun Ray Connector for VMware VDM

[originally posted by Sarah Fortune 3-Dec-2008, updated 26-May-2009]

This page is updated as more solutions become available, also see this page for keyboard issues.

Log messages

The log messages for the VDM connector are located in /var/opt/SUNWut/log/messages
Look for messages beginning with 'kiosk:vdm'.

It may also be helpful to look at the VDM Connection Broker log messages, they can be found in the VDM web administration under Events.

Error connecting to VDM server: java.lang.RuntimeException

Error message: 

Error: Error connecting to VDM server:
Unexpected error: the trustAnchors parameter must be non-empty 


The SSL certificate is not set up correctly on the Sun Ray server. Follow the instruction here:

This desktop is currently not available. Please try connecting to this desktop again later or contact your system administrator. 

The desktop sources for this desktop are not responding.  Please try connecting to the desktop again later, or contact your system administrator

There are several causes for these error messages. They usually means the desktop is not set up properly, or is already in use. 

Some of the possibilities are:

  •  Some one is already logged in that machine (over remote desktop or via the console in VirtualCenter).
  • The machine is powering on/off or suspending.
  • There are no free desktops for that user.
  • The VDM tools are not installed on the desktop, or are not working correctly. Check that the desktop status is available in the VDM web administration.
  • Active Directory and/or DNS is not setup properly on the desktop.
  • There is a network communication problem between the VDM server and the desktop.
  • Windows firewall is blocking connections to the desktop.

There may be more details in the VDM event log in the web administration. You can get help with the VDM configuration on the VMware communities site.

Connection tunneling is required to connect to the desktop but it is not supported by this client

Connection tunneling provides security across a WAN. It allows an encrypted connection from the client to the desktop, by tunneling it through the VDM server. To use the Sun Ray VDM connector, you need to disable connection tunneling.

VDM 2/2.1: 

Open the VDM web administration, go to Configuration and enable

     "Direct Connect to virtual desktop"


Open the VDM web administration, go to Configuration > VDM Servers > Edit, and enable

     "Direct connection to desktop"

Exception in thread "main" java.lang.NoClassDefFoundError

Error message: 

 Nov 14 07:14:02 host kiosk:vdm[12464]: [ID 702911 user.error] Error: Could not locate Virtual Machine for 'pseudo.0836f860ab8': exit code: 1 Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/java/help/impl/SwingWorker
 Nov 14 07:14:02 host   at com.sun.ut.vdm.VdmClient.<init>(
 Nov 14 07:14:02 host   at com.sun.ut.vdm.VdmClient.main(
 Nov 14 07:14:02 host Caused by: java.lang.ClassNotFoundException:
 Nov 14 07:14:02 host   at$
 Nov 14 07:14:02 host   at Method)
 Nov 14 07:14:02 host   at
 Nov 14 07:14:02 host   at java.lang.ClassLoader.loadClass(
 Nov 14 07:14:02 host   at sun.misc.Launcher$AppClassLoader.loadClass(
 Nov 14 07:14:02 host   at java.lang.ClassLoader.loadClass(
 Nov 14 07:14:02 host   at java.lang.ClassLoader.loadClassInternal(
 Nov 14 07:14:02 host   ... 2 more 


This error occurs if you are using an incorrect version of Java, Java 1.5 is the supported version. If you want to use Java 6 you will need the Java 1.6 update 12 JDK.

Desktop tries to open but immediately disconnects

Error message:

Dec  3 12:41:17 host kiosk:vdm[12656]: [ID 702911 user.error] uttsc exited with errorcode: 1


There are several reasons why this error message can occur. To diagnose the problem further, try to connect to the desktop manually from the Sun Ray Server using:

    /opt/SUNWuttsc/bin/uttsc <desktop IP>

It should open a remote desktop connection to the virtual machine. If it fails, it can give you an error message with some further information.

This desktop is not currently available

Hotdesking is not enabled in the Sun Ray VDM Connector 1.0, so if your desktop session is already in use, it will be unavailable if you try to use it from a Sun Ray client.  Yes, this is contradicatory to the behaviour of other clients, but it has been fixed in version 1.1.

Usernames containing spaces are not correctly detected


If the user name assigned to a token contains spaces, then only part of the name will be automatically entered in the login window.


There is a problem with how spaces in the user name are handled in the kiosk scripts. You can get versions of the scripts containing the fix here: vdm and You will need to replace the files:


It is necessary to restart any existing kiosk sessions for the changes to be applied.

Original Comments:


- Having a user already connected to a desktop via Sun Thin client, if the same user tries to connect to the same desktop from a second thin client, the system doesn't allow him to connect and send the following error: " All available desktops source for this desktop are currently busy"

- Performing the same same test but using Wyse client, View Client or RDP will not give any error and works as designed (the first session is disconnected and user can login).

Posted by Jose on March 05, 2009 at 11:24 PM GMT 

Desktop tries to open but immediately disconnects

Running SRSS 4.1 with SRVDM 1.1

getting error:
ay 20 13:43:35 <server> kiosk:vdm[29861]: [ID 702911 user.error] Error: Could not locate Virtual Machine for 'username': exit code: 2 Java Accessibility Bridge for GNOME loaded.
May 20 13:43:35 <server> [Fatal Error] :-1:-1: Premature end of file.
May 20 13:43:35 <server> Error: Internal error parsing response from VMware View Manager: Premature end of file.

any ideas?

Posted by pcmonkey on May 20, 2009 at 10:57 PM GMT 

Has anyone experienced issues when the username (under &quot;Owner&quot; in token registration) has a space, hence; &quot;lastname firstname&quot;. It fails to pass the full information to the VMView server on logon. Hence when that user inserts the smartcard, it displays only LASTNAME in the User Name field.
Cheers, Ed

Posted by Eduardo on May 21, 2009 at 12:49 PM GMT

I'm using Sun Ray connector for VMWare View...

Posted by Eduardo on May 21, 2009 at 12:51 PM GMT 

Hello all

Jose you can tell the view manager to allow session override, works flawless on our configuration.

The problem we have is if you use Xinerama with two SunRay FS the ViewClient display is splitted betewen two monitors and there is no way to move it. At least we were unable to find it.

Sunray Server 4.2 and Solaris x86 v 10


Posted by Juan Manuel Sende on January 11, 2010 at 08:42 AM GMT 

Thursday Nov 13, 2008

Setting up SSL and Sun Ray Connector for VMware VDM

[originally posted by Sarah Fortune 14-Nov-2008, Last updated 24-Feb-2009]

There is a problem with the certificate that comes with the VDM connector. The VDM server's certificate uses a default host name, which won't match the actual host name, so the SSL authentication will fail.
You'll need to generate one with the correct value and import it into the connection broker.

Here's the full set of instructions for using SSL:

1. Using the Windows command prompt, create a new keystore containing a public‐private key pair (filling in the appropriate password and hostname).

%JAVA_HOME%\\bin\\keytool -genkey -keyalg RSA -keystore keys.p12 -storetype pkcs12 -storepass <keystore_pass> -dname "cn=<hostname>"

To configure the VDM Connection Server to use the new certificate:

1. Place the new certificate file, keys.p12, in the following location on each VDM Connection Server (standard, replica, or security server):

C:\\Program Files\\VMware\\VMware VDM\\Server\\sslgateway\\conf

2. Create or edit the following file on each server:


3. Add the following properties, using the password from the previous step.


4. Restart the VDM service.

    Assuming your environment is configured to use SSL, a message like the following appears in the event log:

13:57:40,676 INFO <Thread-1> (NetHandler) Using SSL certificate store: keys.p12 with password of 6 characters

  This message indicates that the configuration is in use.

(There are more details in the VDM Installation and Administration Guide under 'Installing SSL Certificates')

The new certificate needs to be downloaded from VDM and installed into the keystore on the Sun Ray server.

1. Save the certificate using a web browser.


    To do this in firefox you need the Cert View Plus extension:

    Open the VDM connection broker web interface.
    When you are asked to accept the certificate, choose Examine Certificate and then Export.
    Save the certificate to file.

   Internet Explorer:

     Open the VDM connection broker web interface
     In the security alert, choose View Certificate, open the Details tab, and then Copy to File, and follow the steps in the wizard.

2. Copy the certificate file to the Sun Ray server where the VDM connector is installed.

3. Install the certificate into the keystore for VDM with the following command:

keytool -import -file <VDM_certificate> -trustcacerts -v -keystore /etc/opt/SUNWkio/sessions/vdm/keystore

   If you previously imported a certificate you will get the message:

'Certificate not imported, alias <mykey> already exists'.

   It is safe to delete the old keystore and rerun the command.

4. Edit the file:


  Change the following line, using the password from the previous step:


5. There is a error in the vdm kiosk session, it can be fixed with the following
    set of commands:

    sed 's/trustStore=$javaKeyStorePass /trustStorePassword=$javaKeyStorePass /' /etc/opt/SUNWkio/sessions/vdm/vdm > /tmp/vdm

    cp /tmp/vdm /etc/opt/SUNWkio/sessions/vdm/vdm

6. Restart any existing VDM connector kiosk sessions.

The VDM connector should now be to able to correctly authenticate SSL connections to VDM server.

Original Comments:

Excellent post, suggestion:
Section 1 #1 add the -genkey -validity <days>
Section 1 #4 note where the log is (i.e. Event Viewer - Application log with a Source of 'VMware VDM'

Posted by Ken on December 18, 2008 at 08:06 PM GMT

After enabling SSL on the VDM connector, have your users noticed any performance degradation with their logon process? What is the added resource consumption?

Posted by Andriana on January 06, 2010 at 03:18 AM GMT



« July 2016