I'm saying if you don't want a user to delete/remove a VM, the permissions is the way.
Regarding your 'custom process' ... if the operation is something that would prevent someone from deleting an entity, it'll be implemented by VMware by default internally... I don't think you have control over that.
If you can describe what you're doing, perhaps we can help shed more light. Again, in the simplest scenario if you perform say a CloneVM_Task() operation using the SDK, then the VM object will be locked and no one will be able to delete/remove until it's completed. You don't need to do anything extra ... it would be the same if you were performing a ReconfigVM_Task(), the VM entity would be lock until the change has completed. Do you get what I'm saying? So I'm not exactly clear on what operation you're performing that would allow a user to delete the object, again this is handled internally
=========================================================================
William Lam
VMware vExpert 2009
VMware ESX/ESXi scripts and resources at:
VMware Code Central - Scripts/Sample code for Developers and Administrators
If you find this information useful, please award points for "correct" or "helpful".
