The following earlier versions of View components are supported for upgrading to Horizon 7: (Compatibility Matrix)

Latest maintenance release of Horizon View 5.3

Latest maintenance release of VMware Horizon 6.0 (with View)

Latest maintenance release of VMware Horizon 6 version 6.1

Latest maintenance release of VMware Horizon 6 version 6.2

Upgrade Process:

Login to Composer server and start upgrading.

Right Click on the installer and click on Run as administrator (Image)

Click Next

Accept the VMware EULA and Click Next

Select installation directory and Click Next

Enter you database information and click Next

Select “Use an Exsisting SSL certificate” and click on Choose

Select the appropriate certificate and click OK

Click Install

Click Finish and Reboot the server. You are done with Composer Upgrade!

Now check Composer service and Programs & Features for Horizon 7 Composer

Note: Horizon 7 and later components have the TLSv1.0 security protocol disabled by default. If your deployment includes an older version of vCenter Server that supports only TLSv1.0, you might need to enable TLSv1.0 for View Composer connections after installing or upgrading to View Composer 7.0 or a later release.

Connection server upgrade Procedure:

No you have successfully completed Connection server Upgrade. Please click on Yes to reboot the server.

Once restarted check the services are started then access the Admin console to check upgrade status.

Add new License to View environment after upgrade.

Once you open Admin page you will be redirected to “Product Licensing and Usage” page, Please click on Edit License and enter License serial Number then click Ok.

Note:Horizon 7 and later components have the TLSv1.0 security protocol disabled by default. If your deployment includes an older version of vCenter Server (5.0, 5.1, and 5.5) that supports only TLSv1.0, you might need to enable TLSv1.0 manually for View Connection Server connections after installing or upgrading to View Connection Server 7.0 or a later release.

Procedure:

Start the ADSI Edit utility on your View Connection Server host.

In the console tree, select Connect to

In the Select or type a Distinguished Name or Naming Context text box, type the distinguished name DC=vdi, DC=vmware, DC=int.

In the Computer pane, select or type localhost:389 or the fully qualified domain name (FQDN) of the View Connection Server host followed by port 389.
For example: localhost:389 or mycomputer.example.com:389

Expand the ADSI Edit tree, expand OU=Properties, select OU=Global, and double-click CN=Common in the right pane.
If you are unable to view Global OU after Expanding Properties, Please change the Max number of Items per container to larger number. (Images)

In the Properties dialog box, edit the pae-ClientSSLSecureProtocols attribute to add the following value\LIST:TLSv1.2,TLSv1.1,TLSv1
Be sure to include the back slash at the beginning of the line. and click OK

If this is a fresh installation, to apply the configuration change, restart the VMware Horizon View Connection Server service on each connection server instance.
If you plan to perform an upgrade, you do not need to restart the service because the process of upgrading automatically restarts the service.

“Failed to connect to the Connection Server” when loading HTML access with External VIP, but only from Chrome

Solution: Allow HTML Access Through a Load Balancer

Create or edit the locked.properties file in the SSL gateway configuration folder on the View Connection Server or security server host.
For example: install_directory\VMware\VMware View\Server\sslgateway\conf\locked.properties

Add the portalHost property and set it to the address of the gateway.
For example, if https://view-gateway.example.com is the address that browsers use to access View through the gateway, add portalHost=view-gateway.example.com to the locked.properties file. If the View Connection Server instance or security server is behind multiple gateways, you can specify each gateway by adding a number to the portalHost property, for example:
portalHost.1=view-gateway-1.example.com
portalHost.2=view-gateway-2.example.com
You must also specify multiple portalHost properties if a single gateway machine is known by more than one name.

Save the locked.properties file.

Restart the View Connection Server service or security server service to make your changes take effect.

Categories

Live Stats

Disclaimer:

The information in this blog is provided “AS IS” with no warranties, and confers no rights. This blog does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion.