This information describes how to install, configure, and maintain the Connector. The Connector software is the interface between Application Manager and your Microsoft Active Directory server. The Connector can also provide users access to Windows applications captured as VMware ThinApp packages.

This information is intended for organization administrators. The information is written for experienced Windows and Linux system administrators who are familiar with VMware virtual machine technology, identity management, entitlement, and directory services. SUSE Linux is the underlying operating system for the Connector virtual appliance. Knowledge of Linux is essential to configure the Connector directly and to perform system-level functions, such as configuring network settings, time settings, and log files. Knowledge of other technologies, such as VMware ThinApp and RSA SecurID, is helpful if you plan to implement those features.

Before you can install the Connector, an operator creates your account and provides you with the authentication code. If you are using Application Manager as an on-premise appliance, you or someone else in your enterprise is fulfilling the operator role. If you are using Application Manager as a hosted service, someone outside your enterprise is fulfilling the operator role. Regardless of the Application Manager version, you must obtain the Connector virtual appliance in order to install and configure the Connector. The process involves a variety of tasks and you can deploy Application Manager in several different ways. A key distinction in deployments is in the mode of authentication you choose. See Introduction to Application Manager. An important deployment factor depends on if you choose to provide users with access to Windows applications captured as ThinApp packages. The flowcharts that follow illustrate two Application Manager deployments at different levels of specificity. Together, the flowcharts provide a sense of the variety involved in deploying Application Manager.

The Connector Installation and Configuration Flowchart: The installation and configuration flow of a generalized deployment of the Connector

The Connector with ThinApp Installation and Configuration Flowchart: The installation and configuration flow of a deployment of the Connector integrated with ThinApp

See Installation and Configuration Flow of the Connector Integrated with ThinApp for information about installing and configuring the Connector integrated with ThinApp.

The Connector Installation and Configuration Flowchart provides a broad overview of the tasks involved in installing and configuring the Connector. Early in the installation process, you must choose to install the Connector in Service Authentication mode or Connector Authentication mode. Choose Connector Authentication mode if you want Kerberos to authenticate interactions between users' browsers and the User Portal.

In the Connector Web interface, you can make most configurations using the setup wizard as indicated in the flowchart. However, you have the option of skipping many of those configurations, such as for Kerberos, until after you have completed the setup wizard. Then, on the Advanced tab of the Connector Web interface, you can configure the features you skipped and you can edit configurations you made previously.

The Connector Installation and Configuration Flowchart
Flowchart of the connector installation and configuration process from receiving the account information to installing the connector, to accessing the service, and to returning to the connector to post-installation configuration.

The Connector with ThinApp Installation and Configuration Flowchart provides an overview of the tasks involved in integrating the Connector with ThinApp. Review this flow if you want to provide users with access to Windows applications captured as ThinApp packages. See ThinApp Packages for an introduction to integrating an Application Manager deployment with ThinApp.

In the Connector Web interface, you can make most configurations using the setup wizard as indicated in the flowchart. However, you have the option of skipping many of those configurations, such as for Kerberos, until after you have completed the setup wizard. Then, on the Advanced tab of the Connector Web interface, you can configure the features you skipped and you can edit configurations you made previously.

Providing Application Manager users with access to ThinApp packages requires a variety of configurations. Some of those configurations do not directly involve the Connector. The following configurations are required to integrate an Application Manager deployment with ThinApp:

Capture Windows applications as ThinApp packages. See ThinApp 4.7 or later documentation, such as Using VMware Horizon Application Manager to Manage Deployment and Entitlement of ThinApp Packages (ThinApp Horizon Integration Guide) and ThinApp User's Guide.

Create the Windows applications network share to store the ThinApp packages. See Create a Windows Applications Network Share for ThinApp Packages

Configure the Join Domain page of the Connector Web interface. See Configure Join Domain

Configure the Windows Authentication page in the Connector Web interface. See Overview of Configuring Windows Authentication (Kerberos) for the Connector and Enabling Windows Authentication.

Configure the Windows Apps page of the Connector Web interface. See Configure Windows Apps

Enable IdP Discovery by configuring IP address ranges for the Connector instance using the Application Manager Administrator Web interface. See Application Manager Administrator Help.

Verify that the Horizon Agent is properly configured on users' Windows system. See Application Manager User Help.

The Connector with ThinApp Installation and Configuration Flowchart
Flowchart of the connector integrated with ThinApp installation and configuration process from receiving the account information to installing the connector, to accessing the service, and to returning to the connector to post-installation configuration.