License:  There isn't really much of one.  Don't take credit for my work and we'll all be happy.

Warrantee:  Again - there isn't one.  I take no responsibility for anything this program might do.  I use it in my production environment and haven't had a problem yet, but that doesn't mean its problem free.

Usage: Login to it just like you would the VI3 Client.  It will connect to an ESX3 host, or a VirtualCenter 2.  Pick the VM and virtual NIC you want to work with, type in a new MAC, and set it.  Or pick the NIC, and reset it to VirtualCenter control.  Click the 'Report' button to generate an XML report of your VM's.


ChangeLog:

Ver 1.1.0.0

New Features:

1. Ability to return a virtual NIC's MAC address to VirtualCenter control.

2. Update the UI fields with the MAC that was set, if the task is successful.

3. Save last successful login hostname and username.

4. Ability to reload the VM inventory without restarting the program

5. Buttons to expand/collapse the entire VM inventory tree

6. Added ability to output an XML report of every VM, it's NIC's, and it's disks.  Some (most?) information will be empty for powered-off VMs.  This can take a long time if you have a lot of VMs.

Fixed issues:

1. Fixed lag during login.  The VMWare KB Article at the following URL documents the issue and contains the solution
http://kb.vmware.com/vmtnkb/search.do?cmd=displayKC&docType=kc&externalId=87402&sliceId=SAL_Public&dialogID=8411143&stateId=0%200%208405836&doctag=Author,%20KB%20Article

2. Minor status updates so it doesn't look locked up while running tasks.  Still single-threaded though - it won't respond to mouse-clicks or anything while a task is in progress.

3. Send logout event when the application closes.

4. Templates are no longer displayed in the VM inventory.  They would fail the task every time anyways.

Known issues:

1. There are extra lines left behind in the .vmx file after using this tool.  If you set an address to static, a generatedAddress=... line remains in the .vmx.  If you set it back to VirtualCenter control, a .address=... line remains in the .vmx.  These lines don't appear to cause a problem, and there's nothing I can do to get rid of them - it's a flaw in the SDK.

2. There seems to be an issue getting the name of the resource pool that a VM belongs to.  I've got VMs spread across 6 resource pools, as well as a few in "invisible" resource pools (eg. a standalone host), but only 1 of my resource pools (a real/normal one) fills in the name property properly - the other 5 and all "invisible" ones return an empty string for name.


Ver 1.0.0.0


Known issues:

1. It takes forever to login.  Something to do with using the VI3 SDK wrapper in .NET.  Some threads about it in the SDK forums, but it doesn't cause me enough problems to do anything about it yet.

2. It appears to lockup when you set MACs.  The interface runs on the same thread as the reconfigure task for the VM, and I don't feel like getting multi-threaded complicated for a tool this simple.  You can watch the task status in the VI client and when it completes the program will start responding again.


Author/Copyright:  Rob Baumstark - robbaum@nait.ca - 780-491-3092
If you enjoy this little tool, e-mail me and let me know.  If there are a lot of users, it might motivate me to improve it.
This is free (as in beer) software.  But if you feel its worth something and want to donate, you can paypal me at rob@baumstark.ca
