One of the observed features of Instant clone pools is that when a VM is logged off it deletes the VM so that any changes are gone. This makes troubleshooting tricky and you cannot set the do not delete at refresh like you can with Full VM and Linked Clones.
What is a View admin to do? Thanks to the folks at VMware GSS we have an option, with a caveat.
You can go into the Adam Database through ADSIEDIT and change a setting so that the VM’s do not delete, allowing you to logoff and reboot them while retaining the VM’s settings.
The caveat* is that when you change this setting you cannot edit the provisioning details or other attributes of this pool. You will have to change it back to ‘deleteonuse’ in the ADAM ADSIEDIT before you can make changes.
How do we do this:
Login with a Domain Admin account to a View Connection server and launch ADSIEDIT and enter these details exactly. The name can be different but copy the rest verbatim
- Name: View ADAM DB
- Connection point: dc=vdi,dc=vmware,dc=int
- Computer: localhost
Click ok and select Server Group. You will see your Pools there. Right click the pool you want and select properties.
Scroll down until you find pae-VMDeletePolicy (Default = deleteonuse)
Change this to ‘never’ and click ok.
You can leave ADSIEDIT open or come back at a later time to revert your changes after testing is complete.
*- When you change the pae-VmDeletePolicy setting to ‘never’ you will not be able to edit the pool settings. If you try a popup will let you know. If you want/need to edit the pool revert the setting to ‘deleteonuse’
Joe Graziano is a Senior Consultant with the End User Computing Group – East. Joe has over 20 years’ experience working in IT having started his career in application development before moving on to Software/Networking support and currently Virtualization with a focus on End User Computing. In addition to being an avid home beer brewer, Joe also holds a number of certifications including VCP6-DV and VCP6-DT.