Upgrading To Horizon View 5.3 – Step 4 – View Agent

In the last blog post we upgraded our Security Server which had a couple of issues which we resolved.  We did experience some downtime for remote access, but this was to be expected. Upgrading the Horizon View Agent consists of two parts:

  1. View Agent
  2. View 5.3 Remote Experience Agent

Upgrade Process

It is assumed that you have access to your existing ‘golden template’ for your Horizon View Desktops and that the recompose operation will be undertaken out of hours.

View Agent

In my lab, I have two ‘golden template’ images for Horizon View desktops, one which is a Windows 7 32 Bit and the other which is Windows 8 64 Bit. For this upgrade, I’m going to concentrate on the Windows 7 32 Bit desktop. The first thing we are going to do is download the correct installation which is at the time of writing is  VMware-viewagent-5.3.0-1427931 Launch the installer and hit ‘Next’

View Agent 01

Accept the EULA and hit ‘Next’

View Agent 02

Select the components you wish to install, I have ensured that Persona Management and vCenter Operations Manager are selected.

View Agent 03

Click Install

View Agent 04

After the install completes, you will need to reboot the ‘golden template’.

View 5.3 Remote Experience Agent

Next up is the View 5.3 Remote Experience Agent, with the latest version being VMware-Horizon-View-5.3-Remote-Experience-Agent-1.0-1404669 Launch the installer and accept the EULA

View Agent 05 Select your installation options

View Agent 06

Next hit Install

View Agent 07

Now this is done, you will need to do the following:

  1. Ipconfig /release on the ‘golden image’ desktop
  2. Shutdown the ‘golden image’ desktop
  3. Create a new snapshot
  4. Perform a recompose of the desktop pool
  5. Upgrade your View Client to 5.3

I’m sure you can appreciate the above are out of scope for this post, however I did want to give you a high level overview.

Final Thoughts

The upgrade process has been fairly straight forward.  VMware have made some drastic improvements to HTML access via Blast, it is now a usable method for accessing a desktop and makes using Horizon Workspace much more appealing.

I have yet to do more thorough testing, but so far so good.

Upgrading To Horizon View 5.3 – Step 3 – Security Server

In the last blog post we upgraded our Connection Server which was straight forward (great job VMware).  Next we need to upgrade the Security Server.

To make things slightly harder, I’m performing a ‘twist test’ which means that the upgrade is being performed using a Horizon View 5.2 dedicated desktop.  Any issues to the usability of the desktop will be in the table at the end of the post.

Upgrade Process

Before we embark on this upgrade process, the number one rule is to get a good backup.  Plus I recommend you check that everything is in good working order in your Horizon View 5.2 environment.

View Upgrade 01

View Security Server 

In my lab, I have a single View Security server called VMF-VSEC01.  Before we can start the upgrade, we need to make sure we have no Remote Sessions as these will be effected.

View Upgrade 22

The first thing we are going to do is download the correct installation which is at the time of writing is VMware-viewconnectionserver-x86_64-5.3.0-1427931

Launch the installer and hit ‘Next’

View Upgrade 10

Accept the EULA and hit ‘Next’

View Upgrade 11

Select Paired Connection Server and hit ‘Next’

View Upgrade 20

I then received an error message ‘Unable to connect to the server VMF-VCON01.vmfocus.com on TCP port 8009.  Please check that the specified Connection Server is running and that this TCP port is not being blocked by a firewall’

View Upgrade 23

A telnet to VMF-VCON01 on 8009 shows that the Connection Server is listening correctly.

I was unable to select ‘Prepare for Upgrade or Re installation’ of my View Security Server as this was ‘greyed out’.

To resolve this, go into Windows Advanced Firewall on both your View Connection and Security Server > Connection Security Rules > Delete > VMware View Security Pairing

View Upgrade 24

A quick re try and we are now able to enter a Security Server Pairing Password.  This needs to be set in View Administrator by going to View Configuration > Servers > Connection Servers > More Commands > Specify Security Server Pairing Password

View Upgrade 25

We can now enter the Security Server Pairing Password in our installation screen

View Upgrade 26

Check your External URL, PCoIP External URL and Blast External URL to ensure these are correct and hit ‘Next’

View Upgrade 27

Select Configure Windows Firewall Automatically and hit ‘Next’

View Upgrade 28

Then hit ‘Install’

View Upgrade 29

A quick check of the vmfocus.com Horizon View environment shows everything is working, so onto the next step!

View Upgrade 30

Twist Test

Question Answer
Did the installation cause any disruption to existing internal Horizon View 5.3 desktop connections? No
Able to connect to existing composed desktops after installation? Yes
Recompose tasks work on Horizon View 5.2 desktops? Yes
Did the View Security Server require a reboot? No
Did external remote access work during installation? No
HTML 5.3 Access via Blast working after installation? Yes
External remote access working after installation? Yes

Upgrading To Horizon View 5.3 – Step 2 – Connection Server

In the last blog post we upgraded our Composer Server which was straight forward (great job VMware).  Next we need to upgrade the Connection Server.

The upgrade process is in two parts, first of all we need to upgrade the Connection Server and then install HTML Access.

To make things slightly harder, I’m performing a ‘twist test’ which means that the upgrade is being performed using a Horizon View 5.2 dedicated desktop.  Any issues to the usability of the desktop will be in the table at the end of the post.

Upgrade Process

Before we embark on this upgrade process, the number one rule is to get a good backup.  Plus I recommend you check that everything is in good working order in your Horizon View 5.2 environment.

View Upgrade 01

The Connection Server upgrade forms two parts:

  1. Connection Server
  2. View HTML Access

View Connection Server 

In my lab, I have a single View Connection server called VMF-VCON01.

The first thing we are going to do is download the correct installation which is at the time of writing is VMware-viewconnectionserver-x86_64-5.3.0-1427931

Launch the installer and hit ‘Next’

View Upgrade 10

Accept the EULA and hit ‘Next’

View Upgrade 11

Click Install

View Upgrade 12

A quick check of the vmfocus.com Horizon View environment shows everything is working, so onto the next step!

View Upgrade 13

Twist Test

Question Answer
Did the installation cause any disruption to existing external Horizon View 5.2 desktop connections? No
Able to connect to existing composed desktops after installation? Yes
Recompose tasks work on Horizon View 5.2 desktops? Yes
Did the View Connection Server require a reboot? No
HTML 5.2 Access via Blast working after installation? No

View Connection Server HTML Access

Download the correct installed which is at the time of writing is VMware-Horizon-View-HTML-Access_x64-2.2.0-1404668

Launch the installer and hit ‘Next’

View Upgrade 14

Access the License Agreement and hit ‘Next’

View Upgrade 15

Select install location

View Upgrade 16

Hit Install

View Upgrade 17

Twist Test

Question Answer
Did the installation cause any disruption to existing external Horizon View 5.2 desktop connections? No
Able to connect to existing composed desktops after installation? Yes
Recompose tasks work on Horizon View 5.2 desktops? Yes
Did the View Connection Server require a reboot? No
HTML 5.3 Access via Blast working after installation? Yes

Upgrading To Horizon View 5.3 – Step 1 – Composer Server

Horizon View 5.3, brings with it a host of new features.  The one which I’m most excited about is being able to use Windows Server 2008 R2 as a desktop operating system.  A list of enhancements is shown below (source VMware Horizon View 5.3 release notes)

What’s New?

  • Windows Server 2008 R2 Desktop Operating System Support
  • Windows 8.1 Desktop Operating System Support
  • VMware Horizon Mirage Support
  • VMware Virtual SAN Support
  • vDGA Support
  • VMware Horizon View Agent Direct-Connection

TOP TIP: Horizon View does not support Windows 2012 Active Directory

Upgrade Process

Before we embark on this upgrade process, the number one rule is to get a good backup.  Plus I recommend you check that everything is in good working order in your Horizon View 5.2 environment.

View Upgrade 01

Twist

To make things a little more interesting, I’m going to do the upgrade whilst using a Horizon View 5.2 dedicated desktop to see if any part of the upgrade effects my experience or the ability to work.

Upgrade Order

The order in which I’m going to tackle the upgrade is as follows:

  1. View Composer
  2. View Connection Server including HTML Access
  3. View Security Server
  4. View Transfer Server (I don’t have one of these in my environment)
  5. View Agent including Remote Experience Agent
  6. View Client

View Composer

In my lab, View Composer is on a seperate Windows 2008 R2 Server called VMF-VCOM01.

The first thing we are going to do is download the correct installation which is at the time of writing is VMware-viewcomposer-5.3.0-1427647

Launch the installer and hit ‘Next’

View Upgrade 02

Accept the EULA and hit ‘Next’

View Upgrade 03

Select install location and hit ‘next’

View Upgrade 04

Enter your ODBC Password

View Upgrade 05

In my environment, I’m using an existing SSL certificate.

View Upgrade 06

Hit Install

View Upgrade 07

Once finished a reboot is required.

A quick check of the vmfocus.com Horizon View environment and we can see everything is ‘tickety boo’.

View Upgrade 08

Twist Test

Question Answer
Did the installation cause any disruption to existing Horizon View 5.2 desktop connections? No
Able to connect to existing composed desktops after installation? Yes
Recompose tasks work on Horizon View 5.2 desktops? Yes
Did the View Composer Server require a reboot? No
HTML 5.2 Access via Blast working after installation? Yes

Upgrade To vCenter 5.1: Unable To Authenticate Directly To ESXi Host Using Active Directory

Problem Statement

After upgrading to vCenter 5.1 and ESXi 5.1 U1, Active Directory authentication to an ESXi Host no longer works.  Using the vSphere Client error message ‘cannot complete login due to incorrect user name or password’ is received.

Authenticate 01

Quick Checks

1. Single Sign On checked, LDAP Active Directory authentication source working for vCenter and another ESXi Host.

2. Permissions checked, ‘Administrators’ Active Directory Security Group applied to vCenter and permissions propagated to child objects.

3. Authentication Services Services, Active Directory being used and Computer Object is valid.

Troubleshooting Steps

I tried to remove the host from Active Directory and re-authenticate.  Hosts and Clusters > Host > Settings > Manage > Authentication Services

Authenticate 02

An error message appeared stating that ‘the user or group named VMFOCUSdomain^admins does not exist’.

Authenticate 03

The Permissions tab on the affected ESXi Host didn’t show a VMFOCUSdomain^admins group

Authenticate 04

I added the VMFOCUSDomain Admins group to the top level and inherited permissions.  Another quick try and I wasn’t able to login to the ESXi Host using the vSphere Client.

This time the Leave Domain setting worked.  Plus I also deleted the Computer Object for my ESXi Host from Active Directory.

Next, I rejoined the Domain and tried to login  directly to the ESXi Host directly using Active Directory credentials, which again failed.

Resolution

I added the Domain Admins group directly to the ESXi Host

Authenticate 05

When using the vSphere Client I deselected ‘Use Windows session credentials’ and manually entered Administrator and was able to login successfully!

Authenticate 06

Simple when you know what is causing the issue.