
A few weeks ago I started building my first Visual Basic 2005 application. What I wanted to do is talk to the VMware Virtual Center API. I published a PDF document that describes how to connect to this API and I released some code fragments. In this process Robert Baumstark helped me a lot with great tips and suggestions. He even shared the source code of his viclient.dll which can be used to get properties from VM’s and logon to the Virtual Center server. After a lot of late hours of coding I finally can release the vmCDConnected application. What’s so special about this application ? Well it scans all the Virtual Machines and shows if they have a CD connected to it. After scanning the VM’s you can disconnect all the CD’s with a click of a button. Why do we need it ? Imagine you have a DRS cluster with 80 VM’s, when one of those VM’s is connected to a CD it will stay on the same ESX server because V-Motion doesn’t work in combination with a connected CD. During beta release of this application some people reported a failure message after login in. I tested this application during several VI-3 Install and Configure classes I delivered but never have seen that error myself. When you encounter problems please report them. I'm also open to suggestions that might be implemented in the next version.