Posted on 16. Apr, 2013 by in Home VMware Lab, View Install Guide, Virtual Desktops.


Over the last few blog posts we’ve taken our existing VMware View 5.1 environment and upgraded it to VMware Horizon View 5.2.  Along the way we did the following:

Updated the VMware Connection Broker

Added the new End User Experience Pack to the Broker

We’ve updated VMware View Composer

Updated the View Agent & Installed the Remote Experience Pack into the desktop

Now, we want to take advantage of all of that work and create a pool that supports these new features.  Normally, you could just recompose with the updated Golden Image (with 5.2 and the Remote Experience Pack add on) and make adjustments in the pool settings but since I’m on a home lab, I’m just going to create it from scratch.

So lets log into the new Horizon View Console and get ready:

1. Go to “https:\\YouViewConnectionBroker.FQDN\Admin and log in.


2. Notice everything is green, green is good ! – Click on Pools

2 - all green - lets click on pools

3. Now lets create our first pool – click on Add

3 - click on Add

4. I’m going to select Automated Pool and click next

4 - select Automated and click next

5. What fun is having a dedicated desktop in a lab !?! Lets choose Floating

5 - change to floating and click next

6. Again, what’s the fun of full virtual machines, lets do View Composer Linked Clones !

6 - check to View Composer LInked clones and click next

7. Now it’s time to name the Pool – pick a good one because you can’t rename it once you are done.

7 - Name the Pool

8. Just one thing I want to point out on this screen, first feel free to make the changes you want to, but at the very least make sure you check the box on HTML Access for this desktop pool

8 - Pool Settings - Notice the new HTML option

9. For the naming pattern, I kept it really simple.  Just keep in mind, if you are interested in fancy you can try Desktop={n:fixed=2} which will cause the desktop names to be Desktop01, Desktop02 etc.  If you want it to say Test_Pool then just type Test_Pool={n:fixed=2} etc.  If you want 3 digits, change the =2 to =3 etc etc etc.  I’m sure you get the idea.  Either way, lets move on.

9 - Pool Settings - naming pattern and pool sizing questions

10.I selected to not redirect the disposable files – you can keep the default if you want.

10 - change to do not redirect disposable files

11. Depending on how you have you lab setup, you can choose to separate out your Replica’s and LinkedClones on to separate Datastores.  For instance, I happen to have 2(ea) SSD’s in my Iomega PX6-300D that I setup as a Datastore.  I normally put my replica’s on it because Replica’s are mostly reads and that works well with SSD.  For this I’m just taking the default of keeping it all on the same datastore.

11a - lets not seperate the replica and os disk

12. So this screen is where you make most of your choices on desktop images, which cluster and folders you want the desktops to deploy to etc.  The Parent VM is the one we installed the updated View 5.2 agent as well as the remote experience pack.  You should have shut down that VM and made a snapshot of it.  Once you did that, it will show up in the Browse section of the ParentVM area.  If not, go make sure its powered down and with a snapshot.

12 - select your parent VM snapshot folder location

13. here are some new advanced options in View 5 as well as a tech preview of some NFS VAAI features.  Sadly, my Iomega doesn’t support it so I’m going to move on.

13 - Advanced Storage Options Selections

14. On this screen, I’m changing my AD container to one I setup a while back for my View5 Desktops.  This is also where you can choose QuickPrep or SysPrep.  I chose QuickPrep

14 - Guest customization

15. We are just about done, the last thing I’m going to do is check the box to entitle the users after the wizard is done.  You can do it then, or wait for the desktops to be provisioned and then go in and entitle the users.

15 - select Entitle users and click finish

16. The next window asks you to pick users or groups to entitle.  I simply chose the Admin group.  Click okay and lets go watch it go – move over to vCenter and check the logs

16 - Choose the entitlements

17. In vCenter you can start to see it creating the Virtual Desktops machines.

17 - watch it go in vcenter

18. Once that is complete, you should be able to click in the Pools area and see that the desktops have completed.  Don’t forget to hit the refresh button on the right side if you don’t see any changes.

18 - hit refresh on the pools screen

Boom – We are done creating the pool and now we are ready to play around with our new desktops !  Make sure you have updated your VMware View Client to the latest and greatest – if you need to download it, just surf over to https:\\ViewConnectionServer-FQDN\ (no admin at the end) and you will see a screen that will allow you to download the client, and if you did everything right you should also see a new option to launch an HTML Browser version !  W0OT !

Lets move on to the next part, playing around with HTML Blast and Unity Touch.




Facebook Twitter Linkedin Email Snailmail

6 Responses to “Creating a New Desktop Pool in Horizon View 5.2”

  1. Chris Nichols says:

    Your website is great. I’ve been using it since I first installed View 5.1, and am now on 5.1.3, and getting ready to go to 5.2. Two questions:

    1. How does 5.2 affect licensing? We currently have the Premier version. I know they changed the way bundles work in 5.2 so I wasn’t sure how that changes things if you are upgrading.

    2. I’ve been having issues with repeating keys within View – both on 5.1 and 5.1.3. Basically at random a users keyboard will appear stuck, but its not the keyboard and a character keeps repeating. I can’t find anyone else having this issue with View, but I have seem similar issues with VMware Workstation. I wasn’t sure if maybe you had send this before.

    Thanks for the great work!

    • vTexan says:

      First and foremost – thanks for the comments !! In regards to your licensing questions – i’d direct you to which is a pretty good overview of any changes.

      As far as repeating keys – i’ve seen this when I console into VM’s (not view specific)- is that what you are seeing? Can you give me an idea as to how / when you woudld see this? Is this when you are in a desktop using the View Client ?

      • Chris Nichols says:

        Thanks for the link!

        I’ve found lots of links to the repeating keys issue with console and vmware workstation. But yes, it is occurring within the VM desktop (Windows 7×64) when using View Client from a Windows 7 based tablet or desktop (using PCoIP, we do not use RDP). If you minimize view the keys don’t repeat on the local workstation, but continue repeating within the view client. It happens randomly, but out of the 40-50 daily concurrent users I have, at least 3-4 individuals report it.

        I have found links such as:

        However they only reference it occurring in remote console through vSphere and I am unsure as to if this change would have any impact on PCoIP connections via View.

        It’s quite strange!

        • vTexan says:

          wow – i’ll keep my ears open but that does sound strange and it would drive me crazy as well !!!

          • Chris Nichols says:

            I appreciate it. I have production support with VMware, I just haven’t had a moment to call them yet. I am prepping to do my View 5.2 upgrade as we speak. Looking forward to the faster recompose. Your walk through’s are great and more thorough than any others I’ve found!

  2. Chris Nichols says:

    So I never did the upgrade; the certificates portion made me apprehensive. I have CA signed certs for my connection and security servers which were pretty easy to generate and install. It looks like for vCenter however its a pretty painful process. I don’t have an internal Microsoft certification server – right now I use a SAN certificate for all of my needs. It appears from documentation that a cert is absolutely required for vcenter/composer? Right now, my certificate is self-signed but the thumbprint is accepted so it functions fine – but that’s on View 5.1.3.

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.