Posted on 08. Apr, 2013 by in View Install Guide, Virtual Desktops.



So far we’ve been going down the journey of updating a VMware View 5.1 environment to VMware Horizon View 5.2.  Let’s review what we’ve done so far:

We’ve updated our Connection Broker

We’ve added in the new End User Experience Pack

In this blog post I’m going to take you step by step through the process of taking an older version of VMware View Composer to VMware View Composer 5.2.0-xxxxx  which is now part of the rebranded VMware Horizon View bundle.

By the way, I think this changed in View 5.0 (Thanks Mr @TheSanzone for pointing this out to me – VDI rockstar !) , but you no longer have to install Composer on your vCenter server if you don’t want.  I do, simply because this is a home lab and I don’t need yet another 2GB – 4GB Windows VM running ! 

First things first, lets verify what version we are currently running.  To do this RDP into your VMware vCenter server, then click on Start – Control Panel – Programs and Features and scroll down until you see VMware View Composer.  In this case, I’m running

version of vCenter and Composer


So lets get this install party going !

1. Download from the – Horizon View Suite – VMware Horizon View 5.2 Area – Scroll down until you see the following VMware-ViewComposer5.2.XXXXX and download it to your vCenter Server.

. 1 - download VMware View Composer 5.2 horizon suite

2. Surf to the folder you downloaded the file to and double click the icon:

3 Composer Executable

3. You should see a splash screen showing you that you are installing/upgrading View Composer 5.2

4 - away it goes

4. Go ahead and click Next on the Installation Wizard screen

5 - Click next on the Installation Wizard

5. The next box asks you to either accept or not the VMware End User License Agreement.  Click next.

6 - accept the EULA or not

6.Take the defaults on what folder to install this to.

7 - take the defaults on the folder location

7. Here you will need the password you used when you setup your View5 Database.  If you don’t remember, see if this blog post will jog your memory (Creating View 5 Database in SQL 2008 R2)

8 - enter in the password for the composer DB

8. Keep the default port settings and default SSL certificate (unless you need to change them for your environment)

9 - take the defaults on the port settings

9. If everything worked fine, you should get the Ready to Install box – click Install

10 - looks like its ready to install - click install

10. Watch it gooooooooo

11 - and away it goes


11. Again, if everything goes well you should see the following “Installer Completed” message.

12 - Installer Completed

12. The next thing you will see is the vCenter server needs to be rebooted.  Click Yes.

13 - View Composer Installer Needs to reboot

13.Once vCenter comes back online, go to Control Panel, Programs and Features and verify that it’s been updated to 5.2.  BOOOOM.  We are done with this.

14 - after reboot go into controll panel programs and features and verify you are at 5.2

That was EASY PEASY !  Lets move on to the next step in our upgrade process.  It’s time to tackle the Agents inside the master image and then recompose, or in my case create a new Pool to take advantage of the new features !

<Link to Blog post on Updating Agents>.  (Coming soon)


Facebook Twitter Linkedin Email Snailmail

2 Responses to “Upgrading VMware View Composer”

  1. Anonymous says:

    […] Upgrading VMware View Composer Popular postsHow to setup your first Desktop Pool in VMware View 5How to install configure and deploy VMware View 5 on vSphere 5 […]

  2. I was going through some similar stuff for my home lab and kept running in to issues processing the upgrade. What I found was the install process didn’t get elevated permissions earlier enough to change the firewall configs that it needed. The MSI errors were very vague.

    After about two hours I figured out I just needed to right click the .exe and launch as Administrator…

    Hopefully this doesn’t bite anyone else. GL!

Leave a Reply


wordpress visitors
The opinions expressed here are my personal opinions. Content published here is not read or approved in advance by EMC and does not necessarily reflect the views and opinions of EMC nor does it constitute any official communication of EMC.