vmware is odd

I installed the final release of vmware server 2.0 on a server today. Not much has changed since the RC version I had been using. I found some quick fixes and tips in this blog: http://digital.blogsite.org/index.php/2008/10/04/review-vmware-sever-2
The authorization.xml problem was a REAL pain, so I was grateful to find a fix for that. And the tip about the VI Client laying around on the server was priceless (duh, the least they could have done could have been a link in the webinterface). Using the client to access the vmware host is finally not painful anymore. The webinterface is still Ok if I’m not at a computer of mine, or am under linux.

There are still some oddities about vmware that bug me, like the missing option to turn off the DHCP server if you set up networking to use a virtual switch (HostOnly). The VI Client allows me to do some stuff that isn’t possible with the webinterface (like priority for RAM and CPU, or CPU affinity), but it doesn’t allow me to ad virtual machines that are on the server ?!?

The Software is free, so I’m not complaining here. But theese would be a real pain in the rear end if I was using the software in a production environment.