Last year with the release of Horizon 7 I wrote a blog on the new features of Cloud Pod Architecture (CPA) this included the new scale numbers. You can find that blog here.
This week VMware released Horizon 7.1 and with this release VMware has increased the scale numbers yet again for Cloud Pod Architecture.
Now with Horizon 7.1 Cloud Pod Architecture can support a maximum of 75k sessions across 5 sites.
The table below shows the new update compared with Horizon 7.0
|Total Number of Sessions
|Total Number of Sites
|Total Number of Pods
This is yet another great update to VMware’s Horizon and Cloud Pod Architecture.
With the release of VMware Horizon 7.1 this week, VMware has made a significant update to the way Horizon supports Multi-VLAN for Instant Clones.
Multi-VLAN support, if you are not aware of this feature allows you to assign Multiple VLANs to a single Horizon View Pool. For example if you have a Horizon View Pool with 1000 desktops these desktops could be spread across 4 different VLANs rather than all sitting on one very large VLAN.
Multi-VLAN support has been around in Horizon View for some time now, however the catch was that it needed to be configured from the command line using a PowerShell script and this wasn’t always the easiest and was not that easy to go back and change.
With the release of Horizon 7.1 when you create an Instant Clone Pool you can now configure Multi-VLANs right from the GUI.
When you get to the vCenter settings page you will now see a new option for Networks.
Once you click on Browse you will see the new screen to choose what VLANs you want to use for your new Instant Clone pool.
You will first need to uncheck the box “Use network from current parent VM image”
Once this box is unchecked you can choose just what networks you would like to use for the newly created Instant Clone Pool.
NOTE: This feature is only available for Instant Clones Pools Desktops or RDSH servers. For Linked Clones you would need to use the old way using the PowerShell script.
Recently, I have been working with Instant Clones in my lab. Although I have found this easy to get up and running (for more information, see my blog here), it hasn’t been easy to find best practices around configuring Instant Clones, as they are so new.
I reached out to the engineering team, and they provided me with the following best practices for using Instant Clones in VMware Horizon 7.0.2.
Check OS Support for Instant Clones
The following table shows what desktop operating systems are supported when using Instant Clones.
|Guest Operating System
||64-Bit and 32-Bit
||64-Bit and 32-Bit
||Enterprise and Professional
For more information, see the architecture planning guide.
To read the rest of this blog please check it out on VMware.com here
Earlier this Month VMware released the latest update to the Horizon Client for the iPad. Version 4.2 can be downloaded here
This brought a number of great updates but my favorite is the ability to use a Mouse with my iPad, yes that’s right when connected to a Horizon desktop or application I can now use a Bluetooth connected mouse.
The mouse that is supported is the SwiftPoint GT mouse, this is a great mouse and fantastic from people that travel with an iPad Pro
This mouse is extremely small but works really well, I have been using the iPad for travel for a few months now and it has been working well but when connected to a virtual desktop there is definitely something missing and that’s the mouse. I have tried to use the Apple Pencil and that works OK but it’s not as good as a mouse. The SwiftPoint GT fixes that problem and now I feel that when traveling with my iPad I have everything I need to do my job as if I was at my desk.
If you would like more details on the SwiftPoint GT mouse you can find it here.