by Joe Graziano
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.
by Julienne Pham
Things can be difficult when you don’t know where a network issue may be.
In today’s datacentre, the rapid need to deploy business applications in minutes is necessary to keep the business ahead of the game. It is even more crucial to keep security and rapid networking configuration in control. So, how can a network administrator get to the bottom of a network issue in a matter of seconds in this new cloud era?
Network Virtualization brings operational and management flexibility and simplicity, but adds a complexity to troubleshooting and pinpointing the root cause of a network issue.
The traditional way would be to check the network activity from vCenter on the ESX level on the physical nic card, and check the packet going on as you run the test. It is also necessary to check the physical network activities and compare with the virtual network traffic and deduce where the bottleneck is.
If now you need to cross check between VCs and multiple sites, how long will it take to figure out the configuration issue? The required information can be gathered on one search on vRealize Network Insight.