Removing a vm from a linked-clone pool. Is it possible?

[Yikes1232011101]

I want to remove a vm from a linked clone pool.  The user needs too many different programs than the others and I just want to remove that 1 vm from the pool so when I recompose the pool he isn't affected.

Has anyone tried doing this and how does it affect the naming convention of the pool.  Ie, the vm I want to remove is vm3 out of 10vms.  Will the next vm created in the pool still be vm11?

thanks for you help.

[pizaro]

are these dedicated or floating virtual desktops?  perhaps you could use thinapp so recompse will not affect the end user, and you have one less master image to maintain?

i don't believe view mgr would pick the ID of the removed VM.  is there a reason why this is important for you?  just curious.

-wen

@wensteryu

www.supersonicdog.com

[Linjo]

One option is to use VMware Converter to convert the linked-clone to a full vm and add that one to a pool.

// Linjo

[Yikes1232011101]

They are dedicated desktops in a linked clone pool.  We currently don't have thin-app licenses so am unable to do it that way.  Although it DOES sound like a good investment!

The Id is not a big deal, just wondering what would happen.  Acutally, the more I read about it, in the View help it says I cannot remove the vm.  If I do it will just delete it.  I may have to convert it to a real vm out of the pool first like the other response said.

Thanks.

[bhamm]

This might be of interest:

http://kb.vmware.com/kb/1026753

One concern I had about reading the info above was that it didn't mention the 'internal disk' that holds the machine's AD account info.  If you do this, I'd recommend making sure you can log into the VM with a local account to re-add it to the domain if necessary.

Also, don't forget that when you delete the original linked clone, view manager is going to delete that VM's AD account.  If you create a copy & don't change the account info, the copy will lose its link to the domain.