Link Horizon Deployments Together with Cloud Pod Architecture

VMware has just made life easier for VMware Horizon administrators. With the release of VMware Horizon 6.1, VMware has added a popular feature—from the Horizon 6 release—to the web interface. Using Cloud Pod Architecture you can now link a number of Horizon deployments together to create a larger global pool – and these pools can span two different locations.

Cloud Pod Architecture in Horizon 6 was sometimes difficult to configure because you had to use a command line interface on the connection brokers. Now, with Horizon 6.1, you can configure and manage Cloud Pod Architecture via the Web Admin Portal, and this greatly improves the Cloud Pod Architecture feature.

You can read the rest of my post on VMware.com  Click Here

VMware App Volumes™ with F5′s Local Traffic Manager

App Volumes, a result of VMware’s recent acquisition of CloudVolumes, provides an alternative, just-in-time method for integrating and delivering applications to virtualized desktop and Remote Desktop Services (RDS)-based computing environments. With this real-time application delivery system, applications are delivered by attaching virtual disks (VMDK’s) to the virtual machine without modifying the VM or applications themselves. Applications can be scaled out with superior performance, at lower costs, and without compromising end-user experience.

For this blog post, I have colluded with Justin Venezia – one of my good friends and former colleague working over at F5. Justin and I will discuss ways to build resiliency and scalability within the App Volumes architecture using F5’s Local Traffic Manager (LTM).

App Volumes Nitty-Gritty

For the full blog please see my blog on VMware .com  http://blogs.vmware.com/consulting/2015/02/vmware-appvolumes-f5.html

Upgrading VMware Horizon View with Zero Downtime

Over the last few years working with VMware Horizon View and doing many upgrades, one of the biggest issues I would hear from customers when planning for an upgrade was, Why do we have to have so much downtime and why with 7 connection brokers do we have to take all 7 down at once.

These questions and issues came up when I was speaking to Engineering about the upgrade process and making it smoother for the customer.

I was told that this in fact was not the case and you did not have to take all connection brokers down during the upgrade process and you could simply upgrade 1 connection broker at a time while the other servers were happily running.

For the full blog please see my blog on VMware.com  http://blogs.vmware.com/consulting/2015/02/upgrading-vmware-horizon-view-zero-downtime.html

Horizon View: RDS PCoIP Design Tips

With the release of VMware Horizon View has come the ability to not only configure virtual desktops but also virtual applications hosted on Windows RDS servers.

In this post, I will cover a couple of things that you should take in to consideration when configuring virtual applications and how they might affect the sizing of your View Cluster and the number of connection servers you will need.

There many different papers and posts on how to configure RDS servers themselves, so I will not be touching on that in this post. I want to discuss the effects of how the PCoIP connections connect to RDS servers and what you should look out for.

For the full blog please see my post on VMware.com  http://blogs.vmware.com/consulting/2014/06/horizon-view-rds-pcoip-design-tips.html