VMware Virtual Infrastructure Client 2.5 Does Not Support 64-Bit Workstations


	Related Products


	Related Articles Using Citrix XenDesktop with VMware ESX VHD vs. NTFS Alignment - Virtualization Storage Using IP-Based Storage with VMware vSphere on Cisco UCS VMware PVSCSI and Low-IO Workloads How to Correctly Size Virtual Machines – Virtualization Webinar


	Additional Resources Ericom Blaze RDP acceleration software – Deliver 10x-25x faster, superior RDP experience and graphics-rich content, while reducing complaints to IT Business Categorization for VMware vSphere Environment-Veeam Business View for ESX & ESXi Free Download A simple and affordable storage software solution for your VMs is now available for under $1000, click here. Download user profile management for Citrix, Terminal Services Remote Desktop, and VMware environments - RTO Virtual Profiles Save days of work managing and documenting your Citrix farm! Have a look at Gourami's Farm Administration Suite! You have a choice! The Alternative to Citrix by Ericom Download PHD Virtual VMware Backup Software - Featuring: Source-Side De-Duplication across ESX farm, Instant File Level Restore and up to 16 concurrent backup streams per host.


	Virtualization Podcasts VKernel VMStats: Virtualization Reporting and Optimization with Christopher Chesley - January 29, 2010 - Episode 112


	DABCC-TV Videos Citrix and AppSense: Desktop Virtualization (VDI) and User Personalization Video Podcast - January 18, 2010 - Episode 26

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"

src=

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 :)

UPDATE - How to work around the VMware 64-Bit problem: How To Install VMware Infrastructure 2.5 Client on a 64-Bit OS

White Paper: Managing Virtualized Systems – Pinpointing performance problems in the virtual infrastructure” White Paper

Sponsored Link: Record RDP and Citrix sessions, low as $49 dollars per server! Download Free Trial Now

Article Tags

VMware Virtualization Support and Training Resources

Trackback this Article

http://www.dabcc.com/trackback.aspx?nCdType=1&nCdContent=6674

Article Comments

posted by Guest - 02/02/2008

25030 - 25030 error can be removed if you will run new msi from administrator, for example start some file manager like FAR with Run As Administrator and then execute msi from it, it will do the trick.

» reply

posted by Guest - 01/03/2008

Work around doesn't work for me... - Followed the instructions, however after I edit the MSI and execute it, I get an error 25030 stating that setup failed to set permissions for registry key HKLM\SOFTWARE\VMware, Inc... Anyone else see this issue? I'm using Vista 64-bit...

» reply

posted by Guest - 01/30/2008
RE: Work around doesn't work for me... - You said I get an error 25030 stating that setup failed to set permissions for registry key HKLM\SOFTWARE\VMware, Inc... Anyone else see this issue? I'm using Vista 64-bit... Same here, no workaround found anywhere yet, sigh. And I'm logged in as an admin when trying to install the modified msi file. Anybody have new ideas?
» reply
posted by Guest - 01/10/2008
RE: Work around doesn't work for me... - please refer to the following article for a detailed answer to the problem: http://www.dabcc.com/article.aspx?id=6826
» reply
posted by Guest - 01/30/2008
RE: RE: Work around doesn't work for me... - There is nothing about error 25030 at the URL you suggested.
» reply
posted by Guest - 02/02/2008
RE: RE: RE: Work around doesn't work for me... - I ran into this error as well. This error caused by the MSI failing to gain administrative priviledges on the system. In order for the newly created MSI to create the proper registry keys and install the COM files properly, it has to run as admin. However, Microsoft does not provide a "Run as Administrator" function for MSI's. Rather, the MSI must have a command in it to envoke the the command. The workaround I used to be able to install properly was after editing the MSI with Orca, open a command promt as admin (you can right-click on the Command Prompt link in the start menu and choose "Run as Administrator"), browse to where the MSI was located, then execute the MSI file from the command prompt.
» reply

posted by Guest - 01/03/2008

Use the following to install on 64bit systems, works fine for me. - # Run the installer. While it is sitting in the error message about needing a 32 bit OS find and copy "VMware Infrastructure Client 2.5.msi" in a subdirectory of the system temporary directory. # Find an MSI table editor. You can get one called Orca from a Microsoft SDK. (Search for orca.msi.) # Using orca, open the .msi file and delete the LaunchConditions steps from InstallUISequence and from InstallExecuteSequence. This new .msi file will install the program. # Trying to connect to a VM will now probably fail. This is because it needs to run in a 32 bit managed environment and the default is 64. You can either change the entire machine state to default to 32 bits using "c:\Windows\Microsoft.NET\Framework64\v2.0.50727\Ldr64.exe setwow" or use corflags.exe from Visual Studio to set the 32 bit env flag on the VI Client binary itself, using "corflags VpxClient.exe /32BIT+" in "C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher". The corflags solution is cleaner since it only has to be done once and affects only VI Client. I assume the ldr64 command would have to be done after each boot and it is a global change.

» reply

posted by Guest - 12/31/2007

How annoying. - Here is a work-around: http://www.p2vd.com/?p=235

» reply

posted by Guest - 12/24/2007

I too also suffer from the same issue, i gave a big explaination on www.vmware.com website in the community section about this issue. - That is just crazy, VMware can't just be narrow minded about this, i mean we are not going backwards here, 64-bit systems are over the horizon and the requirements are just getting bigger, it's not going to get smaller.. and out of respect, they seriously need to step-up to the plate and do something about this issue. My problem is crazy, I do remote from out of the office allot, so.. having to VPN into my network, then RDP into my workstation which is by the way Vista 64-bit then RDP into another server which is 32-bit just to manage my 4 esx 3.5 servers. To me that's of a big concern, i shouldn't have to do all that. That slows down on time and productivity. Oh and the person who posted the first comment, you are not the only one out there who's using 64-bit systems, there's quite a significant of us Administrators out there who is using this.. and i will back you up on that one, cause i am a person who prey on new technology and updates etc. Testing and then implimentations...

» reply

posted by Guest - 12/17/2007

I too suffered this and logged it with VMware who promptly responded back... - with a "says we don't support it here..." in the upgrade guide and suggested I should install a 32-bit OS. :( I replied saying this was unacceptable and asked for an Enhancement request to be logged - I have 20+ ESX licenses + VC and I'm not upgrading any of them until they support Vista 64. One ray of hope that came back said "There is a development issue open about support for 64-bit operating systems, so your request is part of a larger investigation at this stage."

» reply

Submit a Comment

DABCC User: Guest

Subject:

Message:

Image Code: