After connecting to a View server, you can use the remote desktops and applications that you are authorized to use.

Before you have end users access their remote desktops and applications, test that you can connect to a remote desktop or application from a client device. You must specify a server and supply credentials for your user account.

To use remote applications, you must connect to View Connection Server 6.0 or later.


  • Obtain credentials 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 NETBIOS domain name for logging in. For example, you might use mycompany rather than
  • Perform the administrative tasks described in Preparing Connection Server for Horizon Client.
  • If you are outside the corporate network and are not using a security server to access the remote desktop, verify that your client device is set up to use a VPN connection and turn on that connection.
    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 remote desktop or application. Underscores (_) are not supported in server names. 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 remote desktop, verify that the AllowDirectRDP agent group policy setting is enabled.


  1. Either open a terminal window and enter vmware-view or search the applications for VMware Horizon Client, and double-click the icon.
  2. Double-click the + Add Server button if no servers have yet been added, or click the + New Server button in the menu bar, and enter the name of View Connection Server or a security server, and click Connect.
    Connections between Horizon Client and View Connection Server always use SSL. The default port for SSL connections is 443. If View Connection Server is not configured to use the default port, use the format shown in this example:
    You might see a message that you must confirm before the login dialog box appears.
    Note: After a successful connection is made, an icon for this server is saved to the Horizon Client home screen. The next time you open Horizon Client to connect to this server, you can double-click the icon, or, if you use only this one server, you can right-click the icon for the server and select Autoconnect to this Server from the context menu.
  3. If you are prompted for RSA SecurID credentials or RADIUS authentication credentials, enter the user name and passcode and click OK.
  4. Enter your user name and password, select a domain, and click OK.
    You might see a message that you must confirm before the login dialog box appears.
  5. If the desktop security indicator turns red and a warning message appears, respond to the prompt.
    Usually, this warning means that Connection Server did not send a certificate thumbprint to the client. The thumbprint is a hash of the certificate public key and is used as an abbreviation of the public key.
  6. (Optional) To configure display settings for remote desktops, either right-click a desktop icon or select a desktop icon and click the Settings (gear-shaped) icon next to the server name in the upper portion of the screen.
    Option Description
    Display protocol If your administrator has allowed it, you can use the Connect Via list to select the display protocol. VMware Blast requires Horizon Agent 7.0 or later.
    Display layout Use the Display list to select a window size or to use multiple monitors.
  7. (Optional) To mark the remote desktop or application as a favorite, right-click the desktop or application icon and select Mark as Favorite from the context menu that appears.

    A star icon appears in the upper-right corner of the desktop or application name. The next time you log in, you can click the Show Favorites button to find this application or desktop quickly.

  8. Double-click a remote desktop or application to connect.
    If you are connecting to a session-based remote desktop, which is hosted on a Microsoft RDS host, and if the desktop is already set to use a different display protocol, you will not be able to connect immediately. You will be prompted to either use the protocol that is currently set or have the system log you off of the remote operating system so that a connection can be made with the protocol you selected.


After you are connected, the client window appears.

If authentication to View Connection Server fails or if the client cannot connect to the remote desktop or application, perform the following tasks:

  • Determine whether View Connection Server is configured not to use SSL. The client software 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. 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 View Administration document.
  • Verify that the user is entitled to access this desktop or application. See the Setting Up Desktop and Application Pools in View document.
  • If you are using the RDP display protocol to connect to a remote desktop, verify that the remote operating system allows remote desktop connections.