In this blog post we will see how to configure our Horizon View for the first time. We will configure all the components to work together with vCenter to provision and manage desktop pools.
Log in to the View Administrator:
1. Open your web browser.
2. Navigate to https://view_connection_server_addr/admin
3. Log in with the Administrator Account you designated (or with an account that is a member of the administrator group you selected) when you installed the Connection Server.
Now, you can start setting up the Horizon View environment. In this step, the Connection Server will be configured to talk to vCenter and View Composer.
1. Expand View Configuration and select Servers.
2. Select the vCenter Servers tab and select Add…
3, Enter your vCenter server information. The service account that you use in this section should be the vCenter Service Account that you created in Part 3.
Note: If you are using vCenter 5.5 or later, the username should be entered in User Principal Name format – username@fqdn.
4. If you have not updated the certificates on your vCenter Server, you will receive an Invalid Certificate Warning. Click View Certificate to view and accept the certificate.
5. Select the View Composer option that you plan to use with this vCenter. The options are:
- Do not use View Composer – View Composer and Linked Clones will not be available for desktop pools that use this vCenter.
- View Composer is co-installed with vCenter Server – View Composer is installed on the vCenter Server, and the vCenter Server credentials entered on the previous screen will be used for connecting. This option is only available with the Windows vCenter Server.
- Standalone View Composer Server – View Composer is installed on a standalone Windows Server, and credentials will be required to connect to the Composer instance. This option will work with both the Windows vCenter Server and the vCenter Server virtual appliance.
Note: The account credentials used to connect to the View Composer server must have local administrator rights on the machine where Composer is installed. If the account does not have local administrator rights, you will get an error that you cannot connect.
6. If Composer is using an untrusted SSL certificate, you will receive a prompt that the certificate is invalid. Click View Certificate and then accept.
7. The next step is to set up the Active Directory domains that Composer will connect to when provisioning desktops. Click Add to add a new domain.
8. Enter the domain name, a user account with rights on the Active Directory, and its password, then click OK. The user account used for this step should be the account that was set up in Part 3.
Once all the domains have been added, click Next to continue.
9. The next step is to configure the advanced storage settings used by Horizon. The two options to select on this screen are:
- Reclaim VM Disk Space – Allows Horizon to reclaim disk space allocated to linked-clone virtual machines.
- Enable View Storage Accelerator – View Storage Accelerator is a RAMDISK cache that can be used to offload some storage requests to the local system. Regenerating the cache can impact IO operations on the storage array. The max cache size is 2GB.
After you done your selections, click Next to continue.
10. Review the settings and click finish.
The last thing that we need to configure is the Horizon View Events Database. As the name implies, the Events Database is a repository for events that happen with the View environment. Some examples of events that are recorded include logon and logoff activity and Composer errors.
1. In the View Configuration section, select Event Configuration.
2. In the Event Database section, click Edit.
3. Enter the following information to set upthe connection:
- Database Server (if not installed to the default instance, enter as servername\instance)
- Database Type
- Database name
- Table Prefix (not needed unless you have multiple Connection Server environments that use the same events database)
Note: The only SQL Server instance that uses port 1433 is the default instance. Named instances use dynamic port assignment that assigns a random port number to the service upon startup. If the Events database is installed to a named instance, it will need to have a static port number.
5. If setup is successful, you should see a screen similar to the one below. At this point, you can change your event retention settings by editing the event settings.