You can use the silent installation feature of the Microsoft Windows Installer (MSI) to install a replicated instance of View Connection Server on several Windows computers. In a silent installation, you use the command line and do not have to respond to wizard prompts.
About this task
With silent installation, you can efficiently deploy View components in a large enterprise.
Verify that at least one View Connection Server instance is installed and configured on the network.
To install the replicated instance, you must log in as a user with credentials to access the View Administrators account. You specify the View Administrators account when you install the first instance of View Connection Server. The account can be the local Administrators group or a domain user or group account. See Install View Connection Server with a New Configuration.
If the existing View Connection Server instance is in a different domain than the replicated instance, the domain user must also have View Administrator privileges on the Windows Server computer where the existing instance is installed.
If you use MIT Kerberos authentication to log in to a Windows Server 2008 R2 computer on which you are installing View Connection Server, install the Microsoft hotfix that is described in KB 978116 at http://support.microsoft.com/kb/978116.
Verify that your installation satisfies the requirements described in View Connection Server Requirements.
Verify that the computers on which you install replicated View Connection Server instances are connected over a high-performance LAN. See Network Requirements for Replicated View Connection Server Instances.
Prepare your environment for the installation. See Installation Prerequisites for View Connection Server.
Familiarize yourself with the network ports that must be opened on the Windows Firewall for View Connection Server instances. See Firewall Rules for View Connection Server.
If you plan to pair a security server with this View Connection Server instance, verify that Windows Firewall with Advanced Security is set to on in the active profiles. It is recommended that you turn this setting to on for all profiles. By default, IPsec rules govern connections between security server and View Connection Server and require Windows Firewall with Advanced Security to be enabled.
If your network topology includes a back-end firewall between a security server and the View Connection Server instance, you must configure the firewall to support IPsec. See Configuring a Back-End Firewall to Support IPsec.
Familiarize yourself with the MSI installer command-line options. See Microsoft Windows Installer Command-Line Options.
Familiarize yourself with the silent installation properties available with a replica installation of View Connection Server. See Silent Installation Properties for a Replicated Instance of View Connection Server.
- Download the View Connection Server installer file from the VMware download site at https://my.vmware.com/web/vmware/downloads.
Under Desktop & End-User Computing, select the VMware Horizon 6 download, which includes View Connection Server.
The installer filename is VMware-viewconnectionserver-x86_64-y.y.y-xxxxxx.exe, where xxxxxx is the build number and y.y.y is the version number.
- Open a command prompt on the Windows Server computer.
- Type the installation command on one line.
VMware-viewconnectionserver-y.y.y-xxxxxx.exe /s /v"/qn VDM_SERVER_INSTANCE_TYPE=2 ADAM_PRIMARY_NAME=cs1.companydomain.com VDM_INITIAL_ADMIN_SID=S-1-5-32-544"
If you install a replicated View Connection Server instance that is View 5.1 or later, and the existing View Connection Server instance you are replicating is View 5.0.x or earlier, you must specify a data recovery password, and you can add a password reminder. For example:
VMware-viewconnectionserver-y.y.y-xxxxxx.exe /s /v"/qn VDM_SERVER_INSTANCE_TYPE=2 ADAM_PRIMARY_NAME=cs1.companydomain.com VDM_INITIAL_ADMIN_SID=S-1-5-32-544 VDM_SERVER_RECOVERY_PWD=mini VDM_SERVER_RECOVERY_PWD_REMINDER=""First car"""Important:
When you perform a silent installation, the full command line, including the data recovery password, is logged in the installer's vminst.log file. After the installation is complete, either delete this log file or change the data recovery password by using View Administrator.
- Check for new patches on the Windows Server computer and run Windows Update as needed.
Even if you fully patched the Windows Server computer before you installed View Connection Server, the installation might have enabled operating system features for the first time. Additional patches might now be required.
The View services are installed on the Windows Server computer:
VMware Horizon View Connection Server
VMware Horizon View Framework Component
VMware Horizon View Message Bus Component
VMware Horizon View Script Host
VMware Horizon View Security Gateway Component
VMware Horizon View PCoIP Secure Gateway
VMware Horizon View Blast Secure Gateway
VMware Horizon View Web Component
VMware VDMDS, which provides View LDAP directory services
For information about these services, see the View Administration document.
If the Install HTML Access setting was selected during the installation, the HTML Access component is installed on the Windows Server computer. This component configures the HTML Access icon in the View user portal page and enables the VMware Horizon View Connection Server (Blast-In) rule in the Windows Firewall. This firewall rule allows Web browsers on client devices to connect to the View Connection Server on TCP port 8443.
What to do next
Configure an SSL server certificate for the View Connection Server instance. See Configuring SSL Certificates for View Servers.
You do not have to perform an initial View configuration on a replicated instance of View Connection Server. The replicated instance inherits its configuration from the existing View Connection Server instance.
However, you might have to configure client connection settings for this View Connection Server instance, and you can tune Windows Server settings to support a large deployment. See Configuring Horizon Client Connections and Sizing Windows Server Settings to Support Your Deployment.