Before you have end users access their virtual desktops, test that you can log in to a virtual desktop from a client device. You can start View Client from the Start menu or a desktop shortcut on the client system.

In environments where a network connection is available, the user session is authenticated by View Connection Server.

Obtain the credentials you need to log in, such as a user name and password, RSA SecurID user name and passcode, RADIUS authentication user name and passcode, or smart card personal identification number (PIN).

Obtain the domain name for logging in.

Perform the administrative tasks described in Preparing View Connection Server for View Client.

If you are outside the corporate network and are not using a security server to access the virtual desktop, verify that your client device is set up to use a VPN connection and turn that connection on.

Important

VMware recommends using a security server rather than a VPN.

Verify that you have the fully qualified domain name (FQDN) of the server that provides access to the virtual desktop. You also need the port number if the port is not 443.

If you plan to use the RDP display protocol to connect to a View desktop, verify that the AllowDirectRDP View Agent group policy setting is enabled.

If your administrator has allowed it, you can configure the certificate checking mode for the SSL certificate presented by View Connection Server.

To determine which mode to use, see Configuring Certificate Checking in View Client for Windows.

1

Double-click the VMware View Client desktop shortcut or click Start > Programs > VMware > VMware View Client.

2

In the Connection Server drop-down menu, enter the host name of View Connection Server or a security server.

3

Verify that the other optional settings in the dialog box appear as you configured them.

Option

Description

Log in as current user

This check box is displayed or hidden according to the global setting in View Administrator. Do not select this check box if you plan to check out the View desktop for use in local mode.

Port

If you leave this field blank, the default port 443 is used.

Autoconnect

If you select this check box, the next time you start View Client, the Connection Server field is disabled and you are connected to the server specified when you selected the Autoconnect check box. To deselect this check box, cancel the next dialog box that appears and click Options to display and change this setting.

Configure SSL

If your View administrator has allowed it, you can set the certificate checking mode by clicking this link, as mentioned in the prerequisites to this procedure.

4

Click Connect.

You might see a message that you must confirm before the login dialog box appears.

5

If you are prompted for RSA SecurID credentials or RADIUS authentication credentials, enter the user name and passcode and click Continue.

6

Enter the credentials of a user who is entitled to use at least one desktop pool, select the domain, and click Login.

If you type the user name using the format user@domain, the name is treated as a user principal name (UPN) because of the @ sign, and the domain drop-down menu is disabled.

For information about creating desktop pools and entitling users to pools, see VMware View Administration document.

7

In the list of desktops that appears, select a desktop.

a

(Optional) In the Display drop-down menu, select the window size for displaying the View desktop.

The display setting is retained as the default the next time you open the desktop.

b

(Optional) To select a display protocol, click the down-arrow next to a desktop in the list, click Display Protocol, and select the protocol.

This choice is available only if your View administrator has enabled it. PCoIP provides an optimized PC experience for the delivery of images, audio, and video content on the LAN or across the WAN.

Note

If you are using smart card credentials to log in and you want to switch protocols, you must log off and log on again.

The protocol setting is retained as the default the next time you open the desktop.

8

Click Connect.

You are connected to the desktop.

After you are connected, the client window appears.

If authentication to View Connection Server fails or if View Client cannot connect to a desktop, perform the following tasks:

Determine whether View Connection Server is configured not to use SSL. View Client requires SSL connections. Check whether the global setting in View Administrator for the Use SSL for client connections check box is deselected. If so, you must either select the check box, so that SSL is used, or set up your environment so that clients can connect to an HTTPS enabled load balancer or other intermediate device that is configured to make an HTTP connection to View Connection Server.

Verify that the security certificate for View Connection Server is working properly. If it is not, in View Administrator, you might also see that the View Agent on desktops is unreachable and the Transfer Server status shows that it is not ready. These are symptoms of additional connection problems caused by certificate problems.

Verify that the tags set on the View Connection Server instance allow connections from this user. See the VMware View Administration document.

Verify that the user is entitled to access this desktop. See the VMware View Administration document.

If you are using the RDP display protocol to connect to a View desktop, verify that the client computer allows remote desktop connections.

Configure startup options.

If you do not want to require end users to provide the host name of View Connection Server, or if you want to configure other startup options, use the View Client command-line options to create a desktop shortcut.

See the VMware View Administration document.

Check out a desktop that can be used in local mode.

End users can determine if a desktop is eligible for checkout by clicking the down-arrow next to the desktop in the list provided by View Client with Local Mode. If the desktop can be used in local mode, the Check out option appears in the context menu. Only the user who checks out the desktop can access it, even if a group is entitled to access the desktop.