Hi,
We're currently on View 7.2 and are looking to upgrade to 7.3.3 in the near future. There's been interest in getting to this version sooner since it'll support dedicated instant clone pools. I'm trying to understand if utilizing a dedicated Instant Clone pool will utilize any more or any less resources than a floating pool. Per the link below, it says that when a user logs off, a resync operation on the master image retains the VM name.... etc. Where as in the floating pool, it specifies that it's deleted and a new one is created. If someone has any experience with this and could answer a couple general questions it'll be a huge help, since I'm a bit unclear on the explanation below.
1. What happens to the machine after the user logs off? Does the machine get deleted and recreated from the master, but it's still assigned to that user?
- If the machines don't get deleted, will it retain all of the data specific to the user? Just like a persistent machine?
2. Will these machines always be powered on, or only powered on when that user logs in?
Thanks very much,
Mike
Hi Mike,
to make it short:
1. Instant Clones are ALWAYS powered off, deleted and recreated once a user logs off. So if you reboot... its getting deleted, always. If you want to retain user settings or data, you need to use UEM, folder redirections etc. and keep it out of the desktop or sync in and out automatically (like UEM would do).
Only difference with dedicated ICs in comparison to floating ones - dedicated ones retain their hostname/machine account and MAC address when they get recreated. So VM resp. hostname 123 will always be assigned to user ABC, unless you as an Admin do forcibly change this. It's a dedicated, INSTANT Clone, not a persistent one .
2. Should answer itself now. There cannot be a powered off IC (only shortly during a vSphere HA event, but HA would restart the failed ICs then).
Hope that clears it up for you!
BR
Steffen