To provision and present a Windows 8.1 (or Windows 8/7) virtual desktop via VMware View, there are a couple of VMware components that need to be installed on the master image and a number of steps performed.
In this part I will guide you through the steps to build a Windows 8.1 master image which will used to provision a desktop pool with View Composer linked clones.
Summary of Steps:
So far in this Horizon View 6.0 how to series, we have installed a single View Connection Server and installed View Composer on the vCenter server.
We are now going to proceed configuring the service accounts for View to connect to vCenter and join desktops to the domain followed by the events database. Additionally we need to create an OU and delegate permissions on this OU.
VMware View Composer is a component of VMware Horizon View (all editions).
Horizon View Composer offers features such as storage reduction, improved OS management and rapid desktop deployment.
VMware Horizon View Composer uses linked clones to provide a 50% to 90% reduction in storage requirements for virtual desktops. If View Composer is not used, 100's or 1,000's of desktops 25GB+ in size would exhaust expensive SAN storage.
Horizon View Composer does this by using creating linked clones from a parent disk, instead of full clones. This creates what is known as a "diff disk" of the differences between the parent disk and itself once the virtual desktop is powered on. Without the parent disk the linked clones will not work.
The different could be instead of each desktop requiring 25GB+ of space each, the linked clone may only be around 5GB in size. This varies depending on the amount of changes in the desktop during the day, memory/pagefile size and also if the virtual desktop is refresh or deleted after each logoff.
Firstly, what is VMware Horizon? It's a collection of products which covers both virtual desktops, physical desktops, RDS hosts and virtual applications.
There are 3 editions of VMware Horizon;
Standard, Advanced and Enterprise (Feature comparison: http://www.vmware.com/products/horizon-view/compare.html)
Horizon View Standard simply provides virtual desktops via View like it always used to. However it also includes View Composer, licensing for vSphere/vCenter Desktop and ThinApp (like was the case with the old View Premier edition).
The Advanced and Enterprise editions add features such as RDS hosted applications, VSAN and vCOps monitoring amongst other features such as physical desktop image management (aka Mirage).
When trying to remove a vCenter Server from VMware Horizon View Administrator, all pools and desktops managed via that vCenter server must be deleted first.
If they are not, you will get the following warning message and the vCenter server will not be removed:
"The pools and transfer servers associated with this vCenter must be deleted before this vCenter can be removed"
Share this blog post on social media:
TweetAll advice, installation/configuration how to guides, troubleshooting and other information on this website are provided as-is with no warranty or guarantee. Whilst the information provided is correct to the best of my knowledge, I am not reponsible for any issues that may arise using this information, and you do so at your own risk. As always before performing anything; check, double check, test and always ensure you have a backup.