Several months ago I wrote a blog on how Home Sites work with VMware Horizon 6 Cloud Pod Architecture (CPA), you can find the blog here.
With the release of VMware Horizon 7 the way CPA handles Home Sites has been updated so the users with a Home Site will always receive a Desktop or App even if their Home Site is down.
Lets first review what would happen if a users Home Site was down. As you can see in the diagram below the Connection Brokers would return an issue that their Home Site was not available and the user would not be connected to a desktop.
Just as with Horizon 6 with Horizon 7 when the users Home Site is available then the user will always receive the desktop from the Home Site as the diagram below shows.
Here is where we see a change. Now with Horizon 7 if a users Home Site is off-line then the user will still receive a desktop this time from one of the other sites within the Global Pool. As shown below.
Once the Home Site comes back on-line the next time the user logs back in they will automatically be given a desktop from the Home Site once again.
With the release of VMware User Environment Manager 8.7 VMware added a number of new feature, all of which you will find in the VMware User Environment Manager Release Notes.
However, in this blog, I would like to call out two new features that help when deploying User Environment Manager alongside VMware Horizon 6.2. VMware’s EUC teams did a great job in my opinion getting these two great features added or enhanced to work with Horizon 6.2 in the latest releases.
You can read the rest of my post and find out what I will be doing on VMware.com. Click Here
This week at VMworld VMware announced the latest version of Horizon, 6.2, with this release comes a number of new features. Here are 3 new features that were added I feel will make a big difference when deploying hosted applications.
View Composer for RDSH Servers
The View Composer has been around for a number of years now with great effect when deploying linked clone desktops. Well now this technology is available for RDS hosts. Using the composer to deploy your RDS host will give you the following benefits
- Automated built out of RDS server farms
- Faster deployment of RDS Hosts using the View Composer technology
- Storage savings due to the sharing of the base OS disk by the RDSH clones in a farm
Load Balancing RDSH Pools based on Usage
New load balancing enhancements have been added to make sure the users are being assigned to the best available RDS Hosts in the application farm. The load balancing can be configured to utilize either CPU utilization or Memory utilization. Horizon View administrators will able to configure the Application Farms to utilize either the CPU or Memory option depending on the applications in the Farm.
Cloud Pod Architecture support for RDS Applications
Hosted applications are now supported using Cloud Pod Architecture (CPA), this will greatly help when deploying large scale Horizon deployments and across multiple sites.
CPA hosted applications will also support HTML Blast access giving users the options to access there application through there web browser.
These are just a few of the new features of Horizon 6.2, other new features include. One way AD Trusts, FIPS/CC support, 4K Monitor Support and Streamline Pool Creation to name a few.
For more information go and check out the Horizon page on VMware.com Here
Now that VMware App Volumes is live and a number of customers have deployed App Volumes or are thinking of deploying App Volumes, one of the questions that I constantly get asked is, “is ThinApp Dead?” Or “is App Volumes replacing ThinApp?”
Well I want to say this once and for all that ThinApp is not dead and App Volumes is not replacing ThinApp.
ThinApp still has a purpose in the EUC stack and is still the leader in Application Virtualization. In fact, App Volumes and ThinApp can work together happily and App Volumes is a great tool for delivering ThinApped applications to the End User.
App Volumes makes it very easy to deliver your ThinApp application quickly and instantly to your End Users.
Another use case for App Volumes and ThinApp is to deliver your ThinApped applications to RDSH servers so that you can stream your ThinApped applications to your End User devices such as iOS and Android devices. This can even improve your XenApp environment.
App Volumes and ThinApp working together make it very easy to quickly spin up a RDSH host and publish applications through VMware Horizon View or through Citrix XenApp.
I hope that this quick post puts the question to bed for the foreseeable future.
As a ThinApp fan I am happy that there is still life in this great solution!!!
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