Hi Cyril,  I can answer some of your questions.   You can use a linked clone as a persistent desktop, it does work.  After a while though, the Linked Clone will be so different from the parent image it will become very bloated (Eg, Windows Updates from that point onwards would get applied to each linked clone, User installed Apps, etc)  I know some customers like to capture the profiles on persistent desktops so that they can periodically update the Parent image and redeploy the linked clones from there. This works well for keeping the machine up to date and the bloat under control. The obvious drawback being any User installed apps would vanish but that all depends if you allow them that level of customisation.    Thanks, Andrew.
Dear all,  I'm currently working on a proposal where customer insist on using VMware hypervisor as the compute note. I did some research in Linked Clones and fundamentally, its similar to what VHD differencing disk got to offer. Hence, my main concern here is can we use VMware Linked Clones technology to deploy persistent desktops or is this only for non-persistent desktop mode? How about the storage savings if compared to vhd differencing disk? What's the estimate of delta disk usage of a typical user based on your experience? Thanks for any advice given!   Regards, Cyril
VMware Linked Clones in vWorkspace