For who is approaching Horizion for the first time, it’s important to know that Horizon View provides a great desktop pool feature known as linked-clone desktops: in short a linked-clone is small efficient desktop made from a snapshot of a parent VM known as a gold image. All the files and software on the gold image at the point of a snapshot are available on each linked-clone desktop at a fraction of the size of a full desktop image. Changes made the gold image do not affect the linked-clones unless a new snapshot is taken and the linked-clone desktops are recomposed.
To provide this function a Composer server is required, this provides the automation and database required to deploy linked-clone desktop pools. Its worth noting that starting from Horizon 7 instant-clone desktop pools are available with the correct Horizon View license which doesn’t require a Composer Server.
The following post will illustrate the deployment steps for Horizon Composer
The Composer Server requires a database, see the documentation for what databases are supported. I am using a remote SQL Server 2012 instance. First create a new database and add a logon account. I set up a Windows service account in AD and added that as the owner of the database.
- Create a new ODBC connection and point to the relevant SQL instance. Remember to install SQL native client.
- On the System DSN tab, click Add
- Enter the name ViewComposer for the DSN and enter the SQL server name. Click Nex
- I am logged in as the service account so I will be using Windows Authentication
- Change the default database to the newly created composer database and complete the wizard
- Test the connection and hopefully it should connect successfully.
Don’t install on Horizon Connection Server: View Composer cannot be installed on the Horizon Connection Server. They must be separate machines. View Composer is typically installed on vCenter server if less than 1,000 linked clones.
Extra Memory for vCenter: If you install View Composer on a vCenter server, VMware recommends adding 8 GB of RAM to the server.
vCenter Service Account: if you install View Composer on a vCenter server, login as the same account that was used to install vCenter.
Internet access for CRL checking: If the View Composer server does not have Internet access, see VMware 2081888 Installing Horizon View Composer fails with the error: Error 1920 Service VMware Horizon View Composer (svid) failed to start
If you will install View Composer on a standalone server (not on vCenter), Horizon 7 Connection Server will need a service account with administrator permissions on the View Composer server. Add your View Composer Service Account to the local Administrators group.
- Run VMware-viewcomposer-7.0.1.exe
- In the Welcome to the Installation Wizard for VMware Horizon 7 Composer page, click Next.
- In the License Agreement page, select I accept the terms and click Next.
- In the Destination Folder page, click Next
- In the Database Information page, enter the name of the ODBC DSN.
- Choose the SOAP port and leave the certificates for now; I will show you how to change them at the end. You can install the certificate now and the installer will use the one you install or change it post deployment
- In the Ready to Install the Program page, click Install
- In the Installer Completed page, click Finish.
- Click Yes when asked to restart the computer.
Replacing Composer Certificate
- Stop the VMware Horizon 7 Composer service.
- Open the MMC Certificates snap-in. Open your Certificate Authority-signed certificate and on the Detailstab note the Thumbprint.
- Run an elevated Command Prompt
- Go to the directory to C:\Program Files (x86)\VMware\VMware View Composer.
- Run the following command: sviconfig -operation=ReplaceCertificate -Delete=false
- Select your Certificate Authority-signed certificate. Use the thumbprint to verify
- Start the VMware Horizon 7 Composer service