LINKED CLONE PROVISIONING IN VMWARE HORIZON

LINKED CLONE PROVISIONING IN VMWARE HORIZON


Creating Golden or Master Image:

I have explained the process of creating an optimized golden image in “Instant Clone Provisioning in VMware Horizon” blog.

You can check the blog by clicking on the below mentioned link

https://virtualfeelers.blogspot.com/2020/06/instant-clone-provisioning-in-vmware.html

However, there is one thing that need to be taken into consideration. To deploy View Composer linked-clone desktops, select the VMware Horizon View Composer Agent option. During the installation of Horizon Agent on Golden Image, please make sure to check VMware Horizon View Composer and uncheck VMware Horizon Instant Clone option

Note: you cannot install both view composer and Instant clone part of the agent.

 

 

Snapshot:  Take a snapshot of the optimized Golden Image.  We will use that snapshot while creating Desktop Pools.

For more information about creating and managing snapshots in vSphere Web Client, please refer to this link: https://kb.vmware.com/s/article/2032907

 

Snapshots are the building blocks for the Replica.

CREATING DESKTOP POOL

A desktop pool is a collection of desktops that users select when they log in using the View client

There are two main types of virtual desktop pools: automated and manual.

Automated desktop pools use a vCenter Server virtual machine template or snapshot to create a pool of identical virtual machines.

Manual desktop pools are a collection of Server virtual machines, physical computers, or third-party virtual machines. In automated or manual pools, each machine is available for one user to access remotely at a time

For more information on creating Instant-Clone Desktop Pools visit:

https://docs.vmware.com/en/VMware-Horizon-7/7.9/horizon-console-administration/GUID-C450DD3D-AB0B-4B24-8981-ED6C4D1B9148.html

 

Enabling the provisioning for Desktop Pool marks the process of creating a replica VM which will be used to build linked clones. Replica VM is the combination of golden image and snapshot.  The size of the Replica VM is the same as the Master Image VM..

Before building any linked clones, replica creates a stub. Only about 16k in size, with this stub, replica tests itself if it is capable of creating linked clones or not. This amazing features save a lot of time and resources. If in case the test fails, it rolls back, generating an error for the pool.  Only if it is successful, it will go on and create the linked clones at that point

Linked Clone building:

 The process starts with creation of linked clone state for the environment.  This linked clone state is created by linked clone itself according to the requirements which includes any customization like quickprep or sysprep. After the customization is done, it goes on and creates an active state or the user state. This is where the     end-user logs into. Any personalization added to active state can be cleared by doing a refresh. Refresh actually makes the active state revert back to its original state.

In addition to the active state, we have the option to create other disks. As an optional choice, we can add a disposable disk. That’s where the local profile and temporary files go into.

In case of dedicated pools, we can also have a persistent disk which retains the user data.

No comments:

Post a Comment

Understanding the chaos: VCF by "VMware by Broadcom"

  Being in and around the VMware space for around 7 years, I believe it is my inherent responsibility to give “VMware by Broadcom” a chance ...