As like most of us in the virtualization world, I was excited about the release of VMware ESX 3.5 and Virtual Center 2.5! As soon as I could, I went out and downloaded the code and upgraded my lab’s servers only to find that I had a problem. When I installed the upgrade, the VMware Virtual Infrastructure Client required for ESX 3.5, it popped up the most distressing message box,
"This product can be installed only on 32-bit operating systems"
Now, I understand that not everyone out there runs a 64-bit OS. However those of us who like to run large amounts of RAM for the single purpose of running virtual machines through VMware Workstation are required to run 64-bit Vista or XP, unless of course we run Linux. (But that is just not me. ;) This being said, I would imagine I'm not the only one out there who will run into this problem so I thought I would blog it.
I also want you to know that I did not run into this problem with the 2.0 version of the VMware Virtual Infrastructure Client. Now I'm left with running the 2.5 version of the VMware Virtual Infrastructure Client through Citrix or an RDP connection to a Terminal Services box.
I know the typical response to asking for vendors to support 64-bit clients is that there are just not enough of us out there to warrant the extra development and test time, but I just think the type of person who will run the VMware Virtual Infrastructure Client is NOT the typical employee but the administrator who needs to run with as much RAM as possible!
So, VMware, if you are listening, will you please do something about this. I DO NOT want to remotely connect to a client that should be natively supported on this power user’s workstation!!! If not, give us the reason and it better be a good one :)