Installation and Configuration

Configuring VMware View Connection Server

Some additional configuration of the VMware View Connection server may be required in order for SRVC to serve users their desktops.

Disabling Connection Tunneling

SRVC does not support tunneled connections to VMware provided virtual machines. To switch off connection tunneling:

  1. On the Configuration tab in the VMware View Connection Server web administration, select the server, and click Edit.

  2. Click on Direct Connection to Desktop in the pop-up screen.

Secure Sockets Layer (SSL)

If SSL is not required, the following steps describe how to configure VMware View Manager so that SRVC can connect to it without using SSL.

  1. Configure VMware View Manager to accept non-SSL connections.

    1. Log into your VMware View Connection Server web administration, and click the Configurations tab.

    2. Edit the global settings to set Require SSL to Off.

    3. Deselect Require SSL on the pop-up screen.

Enabling SSL

The default SSL certificate that results from the VMware View Manager installation must be replaced in order to enable SRVC to connect to the system. The following steps assume that you have generated and stored a new certificate on the VMware View Connection server. Refer to VMware View Manager documentation for more details.

  1. Export the certificate from the keystore on the VMware View Connection server, using the command:


    # keytool -export -keystore keys.p12 -storetype pkcs12 -file vmware.cer
    
  2. Copy the vmware.cer file to the Sun Ray server.

  3. Import the certificate into a keystore on your Sun Ray server:


    # keytool -import -file vmware.cer -trustcacerts -v -keystore 
    /etc/opt/SUNWkio/sessions/vdm/keystore
    
  4. Edit the kiosk script (/etc/opt/SUNWkio/sessions/vdm/vdm) and modify the line that begins with javaKeyStorePass= to include the password for the keystore.

  5. Restart the Sun Ray server via the Admin GUI.


Note –

The administrator may choose to import the certificate into the default keystore of the server's Java installation instead of following steps 3 and 4. If this is done, the kiosk script must be modified and all references to javaKeyStore and javaKeyStorePass should be removed.