VMware Communities: Message List - VI Client 2.5 only supports 32bit OS?

Re: VI Client 2.5 only supports 32bit OS?

southpaw — Mon, 07 Jul 2008 22:13:11 GMT

3.5 update 1 (and VC 2.5 update 1)

Re: VI Client 2.5 only supports 32bit OS?

Meatwad — Mon, 07 Jul 2008 21:14:54 GMT

The latest builds of the 2.5 Virtual Center client install on x64 (at least Vista) with no issues. It was the original release of the 2.5 client that refused to install on x64 and required the jumping of hoops. It runs a bit sluggishly on x64, but at least it will install now natively.

Of course, there are some that will tell you that unless you're running a server you have no reason to use x64 on the desktop, and that nothing will run on x64. Glad to see there are others out there who are using x64 on the desktop besides me!

Re: VI Client 2.5 only supports 32bit OS?

Texiwill — Mon, 07 Jul 2008 20:04:49 GMT

Hello,

It does install and work on a 64 bit host... check out http://www.astroarch.com/wiki/index.php/Installing_VMware_Virtual_Infrastructure_Client_within_64-Bit_Vista for how to do this.

Best regards,
Edward L. Haletky
VMware Communities User Moderator
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354
As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

Re: VI Client 2.5 only supports 32bit OS?

John Bergin — Mon, 07 Jul 2008 19:52:38 GMT

I need to chime in here that two of my users are part of a pilot program to roll x64 out to the masses on all corp desktops. This wall hit me very hard. Now I have the guys running workstation and using VIC from within that.

edit
Looks like I need to scroll to the bottom before hitting reply in a hurry.

Re: VI Client 2.5 only supports 32bit OS?

akemp — Fri, 18 Apr 2008 13:18:07 GMT

I don't have that information. Please contact your local SE for a NDA roadmap session for detailed description.

Andre
Sr. Product Marketing Manager - Asia Pacific

Re: VI Client 2.5 only supports 32bit OS?

Engelsman — Fri, 18 Apr 2008 12:15:07 GMT

Hi Andre,

Do you have any idea if and when Virtual Center (server) will be supported on a 64-bit Windows Platform?

Regards

Re: VI Client 2.5 only supports 32bit OS?

jprior — Mon, 14 Apr 2008 13:49:39 GMT

Andre,

Thank you very much for your attention and follow up on this issue. I appreciate it!

Re: VI Client 2.5 only supports 32bit OS?

llacas — Mon, 14 Apr 2008 12:36:54 GMT

That's great! Thank you for making our lives easier! We also have 2 out of 4 admins with 64-bit (and i'm one of them).

Re: VI Client 2.5 only supports 32bit OS?

akemp — Fri, 11 Apr 2008 14:20:06 GMT

All,

As I mentioned a few months back, we now have support for running the VC Client 2.5 U1 on a 64-bit Windows platform.

"Starting with VirtualCenter 2.5 Update 1, installation of the VI Client is supported on 64-bit operating systems of Windows that already have the .NET Framework 2.0.

If the .NET Framework 2.0 is not installed on the 64-bit operating system, the VI Client installation fails with a message similar to:

Setup has detected that the Microsoft .NET Framework 2.0 pre-requisite is not installed on this system. Please install this pre-requisite and try again.

You can download the .NET Framework 2.0 from http://www.microsoft.com/downloads/details.aspx?FamilyID=B44A0000-ACF8-4FA1-AFFB-40E78D788B00&displaylang=en <http://www.microsoft.com/downloads/details.aspx?FamilyID=B44A0000-ACF8-4FA1-AFFB-40E78D788B00&displaylang=en>

We hope that this helps all administrators and users who work in a 64-bit environment and thank you for your patience.

Regards,

Andre Kemp
Sr. Product Marketing Manager - Asia Pacific

Re: VI Client 2.5 only supports 32bit OS?

pj101 — Fri, 11 Apr 2008 12:55:37 GMT

Actually i was asking about VMWare ESX+VirtualCenter infrastracture (VI3.5)

Re: VI Client 2.5 only supports 32bit OS?

mcadler — Fri, 11 Apr 2008 12:27:53 GMT

I installed the version of VI client that comes with VMWare Server 2 beta 2 on Vista 64 bit with no problems.

-Michael

Re: VI Client 2.5 only supports 32bit OS?

pj101 — Fri, 11 Apr 2008 08:28:16 GMT

So, has anyone tested it? Does the VC2.5 Update1 version of VI Client REALLY install and work on XP/Vista 64bit?

Re: VI Client 2.5 only supports 32bit OS?

mcwill — Fri, 11 Apr 2008 06:52:34 GMT

Just a heads up, the new VI Client (2.5 Update 1) released yesterday, is now supported on 64bit machines.

KB Entry

Re: VI Client 2.5 only supports 32bit OS?

Meatwad — Fri, 04 Apr 2008 20:40:49 GMT

RParker wrote:
Supporting guest OS (servers) that have a NEED to run SQL, Oracle, 3rd party Apps as 64-bit is MORE important that you running 64-bit (by choice) on your desktop/laptop workstation. You are not a production server, you don't have a NEED to run 64-bit.

And just because you run 64-bit (I am a tech, and I know this as well) that there are VERY very few apps that even run, optimized or otherwise on 64-bit platforms. Even the newly release Office 2007 just now supports 64-bit.

So tell me which apps you have a SPECIFIC need to run 64-bit, but you can't. Because there aren't any from a client side. You WANT to run 64-bit and you EXPECT VM Ware to support your WANTS.

Just stumbled onto this thread after spending yesterday hacking the 2.5 client to work on Vista x64, when the 2.0 client worked fine.

That's pretty presumptious of you to assume that because I'm not running a server, I don't need to run 64-bit. I have 8GB of RAM in my desktop. How, pray tell, do you recommend that I utilize this RAM with VMWare Workstation with a 32-bit OS?

I question your "I am a tech" credentials because every single application I need to run, runs fine on Vista x64. Office 2007 has run fine since the day it came out. The VI 2.5 Client is the first application that won't run. We're not asking for a 64-bit version of the VI Client, we're asking for a 32-bit client that will work on a 64-bit OS, just like the 2.0 version did. And like every other 32-bit application I have that works on a 64-bit OS, which is to say, just fine.

Running the VI Client in a VM isn't a particularly good solution, especially when the 2.0 version ran just fine as a 32-bit application on Vista x64. The hack is so simple, I don't know why VMWare won't just release it with a "at your own risk" warning, since it seems to work just fine and is much easier to deal with than running it in a VM.

Re: VI Client 2.5 only supports 32bit OS?

dcbarker19 — Mon, 31 Mar 2008 20:24:48 GMT

On the VMWare.com download page

http://www.vmware.com/download/server/

Dave

Re: VI Client 2.5 only supports 32bit OS?

chansen — Mon, 31 Mar 2008 17:01:04 GMT

Where did you find the beta 2 download?

Chase

Re: VI Client 2.5 only supports 32bit OS?

dcbarker19 — Mon, 31 Mar 2008 16:17:50 GMT

Hello all,

Just an FYI ...

I just downloaded and installed Beta 2 on a Windows 2008 x64 Server and the VI Client that was included installed without modification and worked great.

Dave

Re: VI Client 2.5 only supports 32bit OS?

hullt — Wed, 19 Mar 2008 13:11:58 GMT

This workaround did the trick!! Now running on my 64x Vista laptop.

Main reason I went 64 is running 4 different OS's with Worstation6 and needed every ounce of the 4gb installed.

Thanks for the instructions!!

-Tim

Re: VI Client 2.5 only supports 32bit OS?

Speedbmp — Fri, 14 Mar 2008 17:41:42 GMT

Thank you for posting that link! it works like a charm on windows XP 64bit also not just vista!

Stephen

Re: VI Client 2.5 only supports 32bit OS?

larstr — Fri, 14 Mar 2008 08:37:21 GMT

Did you try this excellent step by step guide? How To Install VMware Infrastructure 2.5 Client on a 64-Bit OS

Lars

Re: VI Client 2.5 only supports 32bit OS?

RMyburgh — Fri, 14 Mar 2008 07:40:05 GMT

Update: Didn't work. Now it installs (with an error at the end of the installer). When I try connect to VirtualCenter, I get:

h4. Class not registered (Exception from HRESULT:0x80040154
(REGDB_E_CLASSNOTREG))

Same error when I try connect to a Virtual Host directly too..

Also to note for others, that to use the above method, you must run cmd.exe as administrator, otherwise corflags.exe will not have write permissions to the vpxclient.exe file.

I tried getting our local account rep to look into it, but nothing yet. Most disappointing.. The server hardware in the middle (between the VMWare and the storage), albiet important, is reasonably agonistic to this whole deployment. Whats kind of sad is, I'm getting more feedback from our account manager at the server hardware vendor than I am from EMC and VMware, and the whole basis of the solution is VMware on EMC Cellera/Clarrion storage.

Clearly the short-falling is on our (the customer's) side, and I should
have put a Windows XP laptop in the project budget for the sole purpose
of "making it work".

Pardon my frustration, but as I said before, Enterprise-grade software is meant to "just work".

Is there likely to be a beta version of the new clients (either the 64bit compatible client or 64bit native client) released anytime soon?

Re: VI Client 2.5 only supports 32bit OS?

RMyburgh — Thu, 06 Mar 2008 17:14:21 GMT

Yep, 8 of the 11 people in the team run the D630s, no issues at all.

I'll give that other solution a go, and hopefully, not too much hackery is involved.. I'm not one for festoring with Enterprise/carrier-class equipment or software - Its meant to "just work" out of the box.

Re: VI Client 2.5 only supports 32bit OS?

chansen — Thu, 06 Mar 2008 16:16:09 GMT

Here is another user running 64-bit edition on my Dell D630 for a while now. Runs great, 4gb of ram. No problems with drivers or anything.

Chase

Chase Hansen

Re: VI Client 2.5 only supports 32bit OS?

southpaw — Thu, 06 Mar 2008 15:45:58 GMT

Even new laptops don't support 64-bit Vista, there may be SOME driver support but not all. I challenge that laptops that come pre-installed with 64-bit don't have support for their hardware. You are in the minority, 32-bit is a VERY large footprint and there is virtually no development in 64-bit. Games drive the market, not apps, not business, not utilities, GAMES.

I have to disagree on this statement... I have been running Vista X64 since around the Beta2/Beta3 stage on an IBM T60p laptop... 4GB ram (only sees 3gb but that is a chipset problem and don't get me started on why IBM sells a laptop with 2x2gb sticks that cannot 'see' or use all of it) but there is not a single device i have on this laptop that does not have a compatible driver... nada, zilch, none... In fact the only problem i have run into is more around Vista's new security model in that installers/applications have a more restricted policy when writing to Program Files than anything.. the only applicatoin that refused to run for me was the Infotriever applet that gets fired up when i want to pull in travel information from our travel folks into Outlook 2007... it has been fixed for a month or so now...

How do those GAMES get to the end users? Developers writing code, Marketing people looking at buying trends, Sales people schilling their product, Manufacturers producing and distributing said product along with stores that sell it and manage the inventory... All of these people have to communicate with each other seamlessly... now, where is the market?

Re: VI Client 2.5 only supports 32bit OS?

clay_combs — Thu, 06 Mar 2008 14:23:43 GMT

Attached are the two tools you will need. Follow the instructions earlier in this thread.

Re: VI Client 2.5 only supports 32bit OS?

chansen — Thu, 06 Mar 2008 14:21:11 GMT

Thanks, I will see if I can give this a try later today.

Chase Hansen

Re: VI Client 2.5 only supports 32bit OS?

akemp — Thu, 06 Mar 2008 14:11:10 GMT

Here is a very quick workaround. Sign up for the Thinstall beta, create a new package inside a clean windows vm. Install the 32 bit client, finish the package. Take package and run it directly on your 64bit host.

Regards,

Andre Kemp
Sr. Product Marketing Manager
--
Pardon the brevity, sent from my handheld

Re: VI Client 2.5 only supports 32bit OS?

chansen — Thu, 06 Mar 2008 13:51:07 GMT

I agree, they should at least post a already hacked version for people that do not want to go through the trouble of doing it. I'm still running VI Client through one of my 32bit Terminal Servers.

Chase

Re: VI Client 2.5 only supports 32bit OS?

RMyburgh — Thu, 06 Mar 2008 13:40:15 GMT

Bump again.. Any update on the 64bit client?

We just purchased a reasonably-sized VI3 deployment, along with Lab Manager, to find out some staff can't install the client... I've read the notes on hacking the installer to work, but one would expect that at least a pre-hacked client would have been made available for download. Not everyone has Visual Studio...

For now, it looks like its RDP to a Windows VM, to run a VI client, to connect to the VirtualCenter server on a different network, which connects to the VHosts.

Re: VI Client 2.5 only supports 32bit OS?

Speedbmp — Wed, 27 Feb 2008 18:11:25 GMT

i hate to bump this but any word on when this will be out? because i have to use it though citrix so i can use it on my desktop. i am running windows xp 64bit and have been running it for quite sometime.

i also read that somebody has repackaged it so it will install on 64bit would you mind posting a link so i can get it?

Stephen

Re: VI Client 2.5 only supports 32bit OS?

mystereman — Fri, 22 Feb 2008 23:19:17 GMT

RParker wrote:

So tell me which apps you have a SPECIFIC need to run 64-bit, but you can't. Because there aren't any from a client side. You WANT to run 64-bit and you EXPECT VM Ware to support your WANTS.

That's easy. VMWare Workstation.

I have about 50 Virtual machines that I run regularly on my desktop. I don't run them all at the same time, but often times I run enough of them at the same time that the 3GB that desktop Windows OS's recognize is too limiting. Also, some of the VM's i run are 64 bit VM's, for example using the 64 bit SQL Server, Sharepoint, Forms Server, and the 64-bit only Groove Server.

I have 8GB of memory in this desktop PC. I don't want to have to boot in to a 32 bit OS just to run the VI client.

What's more, what about the people that manage their VI from 64 bit servers in their server room, rather than their 32 bit desktop client back in their cubicle?

How do you know that? Obviously, you don't because I DO need to run 64-bit on my desktop, because 3GB just isn't enough memory.

RParker wrote:

I'm sorry, but you know a lot less than you think you do. I run 64 bit every day, and to date i've run across about 3 apps that do not work on 64 bit. iTunes, VI Client (works, but won't install), Flash player (though works in the 32 bit browser)

By the way, Office 2007 was release a year and a half ago. That's hardly "newly released" and Office 2003 works just fine on 64 bit as well (I know, I have both installed).

RParker wrote:

The Server based guest OS you support are WAY different than your immediate request to have 64-bit loaded locally.

Actually, they're one in the same, because I run those 64 bit SERVER vm's on my desktop, and I give them more than 4GB of memory. Once their finalized, I then apply all my changes or updates to the ESX server, but I do all my initial rollout and testing on my desktop with VMWare so that I'm not using up server resource for non-production purposes.

I think you seriously need to rethink what you think you know, and stop telling other people what they do and don't need. You don't know my requirements. You don't know my situation. What's worse, is you can't seem to use even a slight bit of imagination to understand why others might need VI support for 64 bit OS's (yes NEED, not WANT).

So please stop telling me that you know better than I do.

Re: VI Client 2.5 only supports 32bit OS?

Schorschi — Fri, 22 Feb 2008 23:16:16 GMT

BOTTOM LINE... VMware should never make this, ah, well I would not call it a mistake, lets call it... a narrow focused decision to ignore 64bit support based on asumption, lack of market research, misunderstanding client needs? Whatever is deemed descriptive to your respective situation or perception. I trust, using the term, explicitly, trust, that VMware learns from this feedback as provided, and never conducts a solution media release that is so narrow in focus again. To repeat in similar manner this narrow decision making scenario would for some, I believe, given the comments in this thread, be the last straw, speaking metaphorically.

Re: VI Client 2.5 only supports 32bit OS?

mcraft — Fri, 22 Feb 2008 22:20:48 GMT

3GB process space for a 32bit java process requires a 64bit MS host.

gg. let this thread die.

Re: VI Client 2.5 only supports 32bit OS?

RParker — Fri, 22 Feb 2008 22:19:03 GMT

Well who made that decision? I bet not ALL your drivers are support for 64-bit, in fact I can pretty much gurantee it.

You made a decision to install a 64-bit Os without testing it.. why? What does 64-bit do for you? Specifically that 32-bit wont...

Re: VI Client 2.5 only supports 32bit OS?

RParker — Fri, 22 Feb 2008 22:16:58 GMT

as well as to avoid purchasing WS2003 Enterprise for systems with 4GB-32GB of RAM

First of all Windows 2003 Enterprise 32-bit supports up to 32-gig of RAM. Nice try. You don't even need 64-bit for that. That's is an archtectural limitation of Microsoft, not a limitation of the 32-bit code.

On the server side, my best practice is to install WS2003 x64 on capable hardware

Secondly if those are truly best practices, then they should be running on server class hardware, not your workstation, right? So ESX FULLY supports 64-bit guests.

Most 32-bit apps we use run fine on x64

Most? No, sorry, have to say nope, nada, nil, not even close. maybe SOME maybe even a significant amount, but not most. Many (such as drivers, namely sound and utilities) won't even have a driver for 64-bit.

Please know that many of us want to move to x64 OS's natively to support the processors we've been purchasing for over 2 years,

And lastly, what's wrong with XP 32-bit? Vista 32-bit supports these Dual Core/Quad Core processors, in fact 32 bit support for these platforms has been around a lot longer than 64-bit OS, so 32-bit is the finaly product and 64-bit is still in testing, which is why you won't find 64-bit drivers... There just isn't a need to support it.

And while we are on the subject, tell me exactly what you think 64-bit support provides that 32-bit support provides. Keep in mind, I am a Systems Administrator/Developer and I already know the answer to this question, but I would like to know what false perception you have that you think 64-bit will do for you?

Performance for one I can tell you is LESS on 64-bit than 32-bit for MOST applications, because of the complexity that 64-bit supports.. but please indulge me.. What does 64-bit bring to the table? Memory limitations are higher than you think for 32-bit.

Re: VI Client 2.5 only supports 32bit OS?

jprior — Fri, 22 Feb 2008 22:10:41 GMT

Stop replying to 2 month old posts, please. This argument has been had already. VMware have agreed to work on a fix, and stated a new client with 64bit support is in development.

Re: VI Client 2.5 only supports 32bit OS?

RParker — Fri, 22 Feb 2008 22:07:19 GMT

Supporting guest OS (servers) that have a NEED to run SQL, Oracle, 3rd party Apps as 64-bit is MORE important that you running 64-bit (by choice) on your desktop/laptop workstation. You are not a production server, you don't have a NEED to run 64-bit.

So tell me which apps you have a SPECIFIC need to run 64-bit, but you can't. Because there aren't any from a client side. You WANT to run 64-bit and you EXPECT VM Ware to support your WANTS.

The Server based guest OS you support are WAY different than your immediate request to have 64-bit loaded locally.

As already stated, VM Ware intended audience is 32-bit, and they have to support their clients just like you have to support your clients/customers which have a NEED to run 64-bit for their server based PRODUCTION apps, you don't have a NEED to run 64-bit from your desktop.

So that's the issue. 32-bit for everything you do, remote desktop, client pieces, VPN, will work 32-bit just fine. Chances are your machine doesn't even go beyond a 4GB limit anyway, so why do you think you need to run 64-bit in the first place?

For those applications you can run a VM, but for a STANDARD desktop/aptop you can run 32-bit just fine.

There aren't even drivers designed for 64-bit on laptops for the most part anyway, maybe SOME but most are still 32-bit and even those won't install in a 64-bit you have to have a specific 64-bit list of drivers.

I can give you a list of apps that will NOT run in a 64-bit client, you want it? So VM Ware isn't the ONLY vendor that isn't onboard with the 64-bit thing. Its going to be a WHILE before we see 64-bit as the standard desktop.

That's what bottom line is. VM Ware has to support you with 64-bit which complicates their support. You dont' have a need to run 64-bit, so why should they be force to support you just because you WANT it?

Re: VI Client 2.5 only supports 32bit OS?

jprior — Fri, 22 Feb 2008 22:01:35 GMT

Note that 64bit supported does not mean 64bit code, just an application that works correctly or even just installs under 64bit OS. I'm having no problems with my VI client on 64bit Vista, now that its running, but I'm also not using each and every feature.

Re: VI Client 2.5 only supports 32bit OS?

RParker — Fri, 22 Feb 2008 21:57:09 GMT

I've done a "straw poll" worldwide, albeit internally - to my peers to gauge the level of interest, complaints etc in regards to not supporting 64-bit client. To date, only the posts listed here are the only customers worldwide who have said they needed this client to be 64-bit. You do have a valid point that the checker has only now kicked in, so maybe there is a "hidden" 64-bit ADMIN workstation community, which has NOT been seen before by VMware

That pretty much sums up my post.. said the same thing, people here are TECHS, meaning they are NOT VM Ware intended audience. Most people run standard OS, 32-bit Windows XP.

I like it!

Re: VI Client 2.5 only supports 32bit OS?

brugh — Fri, 22 Feb 2008 21:50:33 GMT

these are only 4 reasonably small steps to take. why don't you put that in the installer to have that perform these steps when it detects a 64-bit OS in the first place. that way it will run on both and no need to change the codebase at all.

Re: VI Client 2.5 only supports 32bit OS?

jprior — Wed, 23 Jan 2008 15:56:42 GMT

chansen wrote:Does VMware plan to release a fix for this ANYTIME soon?

Yes, Andre gave some timelines early this month:

akemp wrote:All,

Here is the update on this issue. Look for 64-bit client support in Update 1 of our ESX\VC products, which will occur this quarter. A full true 64-bit client will occur later >this year.

Andre Kemp
Sr. Product Marketing Manager - APAC

Re: VI Client 2.5 only supports 32bit OS?

chansen — Wed, 23 Jan 2008 15:09:15 GMT

Does VMware plan to release a fix for this ANYTIME soon?

Re: VI Client 2.5 only supports 32bit OS?

elcapitankyle — Thu, 17 Jan 2008 20:20:02 GMT

This worked perfectly the first time. Thanks for posting this! Here are some hints for others that may need some help finding their way around these instructions:

On Vista 64 try looking for the .msi file in c:\users\<username>\AppData\Local
If you use the Visual Studio command prompt it makes things easier for step 4.

Re: VI Client 2.5 only supports 32bit OS?

Jammrock — Fri, 11 Jan 2008 18:54:27 GMT

Here, here.

Re: VI Client 2.5 only supports 32bit OS?

TheRealJason — Fri, 11 Jan 2008 18:40:32 GMT

I understand the desire for a linux client may be higher at the moment than the 64-bit windows version, but the difference is that we USED to be able to run it on 64-bit windows. So rather than wanting something that never existed, we had it and it was taken away.

Re: VI Client 2.5 only supports 32bit OS?

ejward — Fri, 11 Jan 2008 12:43:58 GMT

lightxx wrote:
if you where to pay 100k$ / year to have your car running, would you still try to jimmy something up in your backyard if it's broken?

its the same with VMWare. sure, with some ugly hacks you somehow could get VIC up and running, but that's just not the point.

You've obviously been in my backyard. I've got several cars back there.

Re: VI Client 2.5 only supports 32bit OS?

lightxx — Fri, 11 Jan 2008 07:39:13 GMT

if you where to pay 100k$ / year to have your car running, would you still try to jimmy something up in your backyard if it's broken?

its the same with VMWare. sure, with some ugly hacks you somehow could get VIC up and running, but that's just not the point.

Re: VI Client 2.5 only supports 32bit OS?

ejward — Thu, 10 Jan 2008 20:27:14 GMT

I work for a fortune 500 company and we have a lot of 64-bit desktops. Most of our high-end graphics worksations are 64-bit. We've been using a lot of 64-bit servers for several years now. Starting this year, it's one of the first questions we ask when a new application comes on line. It just makes financial sense. To get more than 4 GB out of a 32-bit Windows server, you have to buy Enterprise Edition. Roughly 4 times as much. With 64-bit, you can still use standard.

I was disappointed that we couldn't install our Virtual Center server on 64-bit.

Re: VI Client 2.5 only supports 32bit OS?

Thierry Frache — Thu, 10 Jan 2008 19:44:05 GMT

Please! Stop crying! You need a solution not an excuse! I used corflags and the tool is working fine on my vista 64. I understand it's easier to ask here everyday. The update will be available soon. That's all.

Re: VI Client 2.5 only supports 32bit OS?

robert.eckdale — Thu, 10 Jan 2008 16:37:56 GMT

Add me to the list as well. 3 Enterprise admins and a handfull of operators are now out of luck.

Re: VI Client 2.5 only supports 32bit OS?

Schorschi — Thu, 10 Jan 2008 15:46:59 GMT

At the risk of being labelled anti-VMware (again, LOL, just kidding)... yes, in a word... "Sucks" Like a Hoover!

Re: VI Client 2.5 only supports 32bit OS?

lightxx — Thu, 10 Jan 2008 11:10:11 GMT

quite frankly and honestly and humbly, there's no reason to calm down.

even with a medium sized VMware data center people pay tens of thousands of $$$ for support / year, and yet we have to mess around and hack msi files to get VIC to run on a 64bit platform.

this is 2008, is not like 64 bit OSes are all new and appeared just yesterday and cought VMware by surprise.

the entire situation, friendly worded, just plain sucks.

Re: VI Client 2.5 only supports 32bit OS?

larstr — Wed, 09 Jan 2008 23:12:27 GMT

Please calm down mcraft,
If you're gonna shell out a certain amount of money it would probably be wise to check these things first. Repackaging the install file is a hack, and not something they would force you to do.

Now we know that the 64 bit windows client is on it's way. And I would guess it'll be at least a month before we can download it, so we just need to use some patience.

I believe the number of people that would like to see a linux client is currently much higher, than the people requesting a 64 bit windows client. Still, that demand isn't high enough (obviously).

Lars

Re: VI Client 2.5 only supports 32bit OS?

mcraft — Wed, 09 Jan 2008 23:04:38 GMT

This is, quite frankly, inexcusable

We need an official client update or official workaround that doesn't require me to install visual studio. You'd think after spending millions of dollars on your product you would at least ask what we need going forward and not tell us what you think we need.

Re: VI Client 2.5 only supports 32bit OS?

Thierry Frache — Fri, 04 Jan 2008 15:00:26 GMT

OOps. I don't know why everybody is waiting here!

Ping timeout.

Re: VI Client 2.5 only supports 32bit OS?

mcwill — Fri, 04 Jan 2008 14:55:14 GMT

erk - stack overflow

Thierry,

I don't know if you noticed, but the solution referenced in the article you posted came from this very thread.

Regards,
Iain

Re: VI Client 2.5 only supports 32bit OS?

Thierry Frache — Fri, 04 Jan 2008 14:44:26 GMT

A solution has been found here : http://www.dabcc.com/article.aspx?id=6826

I tested it on Vista x64 successfully.

Re: VI Client 2.5 only supports 32bit OS?

Schorschi — Fri, 04 Jan 2008 14:27:15 GMT

While the cat is away, the mice will play... Wait, scratch that... ESX OS does not have any real need for mice... so.

Re: VI Client 2.5 only supports 32bit OS?

akemp — Thu, 03 Jan 2008 23:22:29 GMT

Jprior,

Sorry about the delay - I was waiting for answers and yes a .net compiled 64-bit client. BTW I'm on holiday for the next 3 weeks so won't be watching this forum for awhile.

Cheers,

Andre Kemp
Sr. Product Marketing Manager - APAC

Re: VI Client 2.5 only supports 32bit OS?

Jammrock — Thu, 03 Jan 2008 18:03:50 GMT

Which isn't a big deal if you have a VLK and spare OS licenses hanging around.

Fortunately I have access to Visual Studio so I was able to get the hacked installer and executable working. Though it never should have come to that in the first place...

Re: VI Client 2.5 only supports 32bit OS?

Phudodragon — Thu, 03 Jan 2008 17:52:28 GMT

You could always create another Citrix server that's not 64 Bit. That's
what I did.

There's always a workaround. Its just how much of a level of effort is one
willing to put into a workaround that is the issue!

On Jan 3, 2008 11:33 AM, TheRealJason <communities-emailer@vmware.com

Re: VI Client 2.5 only supports 32bit OS?

TheRealJason — Thu, 03 Jan 2008 16:32:35 GMT

Doesn’t help if you are running 64 bit Windows on your Citrix servers!

Re: VI Client 2.5 only supports 32bit OS?

Phudodragon — Thu, 03 Jan 2008 16:21:56 GMT

Like other techs, I was a bit annoyed that VMware didn't provide us with a 64 bit client. However, they did provide me with the "opportunity" to come up with a temporary workaround. To get around the "64 Bit" issue I installed Virtual Center Client 2.5 on a tools server in our Citrix environment. I now run the client from my desktop using a Citrix published application.

Hopefully, this little work around can help someone.

Phudodragon

http://vmwareworld.blogspot.com/

Re: VI Client 2.5 only supports 32bit OS?

jprior — Thu, 03 Jan 2008 15:58:55 GMT

akemp wrote:All,

Here is the update on this issue. Look for 64-bit client support in Update 1 of our ESX\VC products, which will occur this quarter. A full true 64-bit client will occur later this year.

Andre Kemp
Sr. Product Marketing Manager - APAC

Thanks for the update, though I am disappointed you didn't follow up on the previously mentioned 'Wednesday' ... to be fair you didn't mention a date

By 'Full true 64-bit client' you mean a .NET 2.0 x64 compiled application? .NET 3.0/3.5?

Curse our luck this is a leap year, we now have to wait an extra day to the end of the quarter!

Re: VI Client 2.5 only supports 32bit OS?

TheRealJason — Thu, 03 Jan 2008 13:50:45 GMT

Andre,

Can we expect a patch to be released even sooner? I've got a brand new Dell Precision on my desk, running Vista 64-bit, and would love to be able to run the client from it.

Re: VI Client 2.5 only supports 32bit OS?

Schorschi — Thu, 03 Jan 2008 07:13:08 GMT

Andre, thanks for the update!

Re: VI Client 2.5 only supports 32bit OS?

shurik@peacetech.com — Thu, 13 Dec 2007 06:04:47 GMT

Andre, they are not alone . All our workstations are XP 64 bit as well and have been for over a year.

Please add my vote

Alex

Re: VI Client 2.5 only supports 32bit OS?

akemp — Thu, 03 Jan 2008 00:12:15 GMT

All,

Here is the update on this issue. Look for 64-bit client support in Update 1 of our ESX\VC products, which will occur this quarter. A full true 64-bit client will occur later this year.

Andre Kemp
Sr. Product Marketing Manager - APAC

Re: VI Client 2.5 only supports 32bit OS?

Jammrock — Wed, 02 Jan 2008 22:53:30 GMT

I just wanted to throw in my voice to this discussion.

I think that not releasing a working 64-bit VMware Infrastructure Client was a big snafu on VMware's part. How are you supposed to convince new customers that you can make a solid 64-bit environment when you can't even code a working 64-bit client? And what do you tell 64-bit OS users to appease them? "Sorry, we didn't think there were enough of you so we didn't bother." Come on, that's about as professional as telling your customers to take a "chill-pill."

While there may not be a majority of 64-bit users out there at the moment, there are a lot. For every one of us that voices are complaint on this community there are probably a hundred brooding VMware users angry that they can't use VIC 2.5 on their shiny new Vista laptop or desktop. And when we finally are told how to work around the issue we are told to follow processes that involve installing the Windows SDK and Visual Studio, or to create a 32-bit virtual OS and run it from there. It is, quite honestly, unacceptable for a company of VMware's size and market position.

Do you realize that Hyper-V is breathing down your necks? What do you think people will do if something like this occurs when Hyper-V R2 comes out with every feature of VMware Infrastructure?

I could go on, but I think that covers enough of what I want to say. VMware does make some fantastic products, but I have been very displeased with the lackluster 64-bit application support (besides this, VMware Server 2.0 Beta comes immediately to mind).

Re: VI Client 2.5 only supports 32bit OS?

tfrache — Sat, 29 Dec 2007 07:50:32 GMT

Hi,

on my lab, I removed the condition which disable installation of the VIClient on Vista 64 (using Installshield 2008). The product can now be installed on vista but I cannot test myself because the SSL/VPN we use does not work on Vista 64 and I cannot try to connect to our ESX farm! I'll update the thread next monday (or before If a guy of my team can test himself this week-end).

Actually, I don't understand why the installation is blocked on Vista 64 has the product can be run on this operating system (see the picture I attached). However, I really don't know what it will happend if you able to connect to your ESX (maybe you'll get a blue screen or something like that). So If you want to test it by yourself, be carefull !

Thierry

Re: VI Client 2.5 only supports 32bit OS?

Schorschi — Sat, 29 Dec 2007 02:23:28 GMT

"I thought this had died down, at least over the holidays! Everyone take a chill-pill." Love it... LOL

My point is, has been and will continue to be... VMware is constantly having to react and respond to issues, like this, that should never have gotten out of their QA process. I want VMware to improve their process internally so that we, the clients of their solutions do not have to deal with this type of thing again, and again. This is not to say that VMware does not do honest effort to get something fixed, reactively. VMware does not have a good record on avoiding problems that should not have gotten through the QA process internally. The entire ESX 3.0.0 release window, the weeks/months after its release was such a situation.

As for anti-Microsoft, their actions speak louder than words, or works for that matter. I will leave it to the majority to decide, or future history to define it.

Having an AXE to grid? No, I am 100% behind VMware and have been since ESX 1.5.2. But I expect better of them, they should learn from their mistakes and those that others in past have made, in reference to being better than what customers expect. If an organization beats expectations of quality, scalability, stability, and consistency, then profitability comes by default. Microsoft is only a threat based on quality, scalability, stability, and consistency. Look at Novell Netware, in many ways, it was a better solution Netware 3.x/4.x time frame, with the lead in LDAP, so how did Microsoft catch up? Moreover, any Microsoft coding hobbist that knows Windows Installer 3.1 via the Visual Studio IDE, would not have made this mistake. VMware did, and they should get some heat for it.

As for you last comment... "any other ISV" maybe... valid point. Not withstanding, I have higher expectations for VMware, and I should, they are the best for now and to stay the best, they should not make these types of obvious mistakes, and they have made some big ones in the last 2 years.

We, as a community of customers, have been toooo forgiving for toooo long and I think the comments others have made, beyond my views, support that perspective. If we, did not wish VMware success, we would not have taken the time and effort to provide the feedback we have in this very thread.

Re: VI Client 2.5 only supports 32bit OS?

halr9000 — Fri, 28 Dec 2007 18:32:38 GMT

Look at the perl based VI toolkit, for esxcfg-* and vicfg-* commands, none of these commands are in the VI windows powershell based tool kit?

If you've talked to the VMware devs so much, you would know that this functionality is forthcoming. Don't forget--VMware is one of the very first 3rd party companies to provide a PowerShell interface. That's pretty pro-Microsoft.

Re: VI Client 2.5 only supports 32bit OS?

akemp — Fri, 28 Dec 2007 15:32:25 GMT

All,

I thought this had died down, at least over the holidays! Everyone take a chill-pill.

I'm please to annouce the "fix" is underway. The chap I talked to said he should have it done by Wednesday - before he went on holiday - but he is swamped trying to finish up his priorities. I'll ping him again and see where we are, but it is coming.

On another note, VMware does NOT have an anti-ms position. Frankly, the entire community would be better off if they embraced virtualization rather than hinder it. Gone are the days of dominate OS players - the trend is to run as much as possible regardless of the platform. The whole idea of v-management is moving in that direction as well. Finally VMware wll updoubtedly have competition, which is good for everybody - keeps us humble in my view. But it seems some people may have an axe to grind no matter what we do, so we just try to do the best we can.

I do know one thing, any other ISV probably wouldn't have even tried - so you can take or committment to this issue as genuine.

Regards,

Andre Kemp
Sr. Product Marketing Manager APAC
--
Pardon the brevity, sent from my handheld

Re: VI Client 2.5 only supports 32bit OS?

Schorschi — Fri, 28 Dec 2007 14:54:56 GMT

Bottomline, VMware screwed up. They are so anti-Microsoft, it impacts their thinking. If you do not believe this, talk to the development teams for VC, VMotion, iSCSI, and ESX, and also Workstation. I have, multiple times with each group, I can tell to the individual in meetings I have had that our feedback is listened to, but rarely acted upon, nor does VMware really want any customer input, their actions speak volumes on this point. With the exception of the Workstation team, the under current of anti Microsoft pro anything else is so strong you can almost see it creating the rose-color tint that the eye-glasses of the same name have. The response to customers, asking for better integration to Microsoft environment is in a word horrible.

Look at the perl based VI toolkit, for esxcfg-* and vicfg-* commands, none of these commands are in the VI windows powershell based tool kit? What the hell is VMware thinking? That Windows Admins will lern perl? Our Windows security group is screaming about Tomcat, and lack of ESX AD integration that is an open-source based, now we have to tell them we need another scripting language to support 3i, and perl of all things? Using Tomcat not allow IIS, not integrating VC with AD as an integrated application, etc., etc. We have been asking VMware to stop this crap attitude for years, yes, years. Specific to my experience since late 2002!

To be honest, I hope the next version of SCVMM (Microsoft System Center Virtual Machine Manager) kicks VirtualCenter in the teeth. The only thing at this point that is going to get VMware to respond effectively is to lose money, at a significant level. Unless Microsoft completely screws up, again, cough, no Microsoft-VMotion? VMware is pushing us to look at Microsoft again, and every other virtualization solution out there, frankly we are really getting tired of this junk coding and QA so weak it is a joke VMware keeps pushing on us.

Re: VI Client 2.5 only supports 32bit OS?

david.hittner — Fri, 28 Dec 2007 13:52:42 GMT

They are trying to get a new product out, why complicate the issue with 64-bit support for systems that probably don't even FULLY support it. I bet even your machine was installed BY YOU to install 64-bit OS... I will be willing to bet it didn't come that way.. You are EXACTLY the reason VM Ware is trying to steer you to stay on 32-bit until they can fix their issues.

As a dual-use Developer and Administrator, my company purchased a Dell Precision 490, dual Xeon, 8GB memory, with Windows XP x64 pre-installed specifically so that I could run VMware. I configure and preload VMs on my workstation, then deploy them to the appropriate VMware servers. Please don't speculate when you have no data.

There is only one reason to use a 64-bit workstation, and that is for large memory support.

What is being called into question is VMware's rational in removing support for the VI Client on 64-bit workstations. Their justification is that they want to ensure a high-quality product on the 64-bit platforms, and the previous VI Client had known issues on 64-bit platforms, so they removed and enforced support until they have time to get 64-bit right. This should not have been a significant issue, since they feel that there are very few 64-bit platforms running the VI Client. In opposition, the user community appears to believe that the per-capita use of 64-bit workstations for VMware administration is significantly higher than VMware claims, and that VMware should have not have removed the unofficial 64-bit support from the VI Client.

Speaking as a Developer, 64-bit OS support isn't real hard to put into your programs - you just need to be aware of the differences while coding. It really helps to make your developers use a 64-bit platform during development, where the 64-bit differences become real obvious when they try to run the program

Speaking as a Tester, 64-bit OS support is significantly harder, because you double your test time by adding the 64-bit platform to the test cases.

As a paying customer, I do find fault with VMware's logic. Imagine if the same scenario occured with a new release of Microsoft Exchange, which required a new Outlook, and the new Outlook wouldn't install on your 64-bit workstation, denying you access to corporate Email !

Once again, Kudos to VMware for agreeing to officially support the 64-bit environment in the next release, but a backhand slap for taking the unofficial support away in the meantime. If an interim patch is 'in the works' as Mr Kemp stated, the user community would appreciate hearing a projected release date.

Re: VI Client 2.5 only supports 32bit OS?

mystereman — Thu, 27 Dec 2007 23:13:33 GMT

RParker wrote:I can tell you dont' work for an Enterprise class company, because that statement is so wrong, I don't even know where to begin.

Even if you were correct, how does working for an enterprise class company or not affect whether or not there is a need for a client that runs on 64 bit OS's? Enterprises are not the only ones using VI.

Companies use what works, not what people WANT.

Yes, and if you need more than 4GB of memory, 32 bit OS's don't WORK, regardless of what you WANT. There are many 64 bit OS's being used in enterprise environments, and not just servers either, but even if it was just servers consider that many admins do their work from servers.

Fact is, 64 bit is becoming very popular as memory requirements grow. For instance, many large companies have large drafting and CAD/CAM departments that need 64 bit OS's to access the 8, 16, or even 32 GB they need for their high end CAD/CAM systems. Microsoft makes a number of 32 bit apps now, not just Exchange and SQL. In some cases, they ONLY make 64 bit versions, suc as the Office 2007 Groove Server. There's also 64 bit Sharepoint and Office 2007 Forms server, Visual Studio 2008 has a 64 bit version, etc..

64 bit hardware is NOT buggy. Maybe some drivers are, but my experience has been that they're pretty solid.

The fact of the matter is, many admins run 64 bit systems. A solid reason is because they have VMWare Workstation or Server on their desktops with 8 or 16GB of memory so they can test various configurations and create images for their deployments. And, since we're talking about a piece of software that is primarily an admin tool, the number of 64 bit users are going to be much higher per capita than in general populace.

Re: VI Client 2.5 only supports 32bit OS?

mrudloff — Thu, 27 Dec 2007 22:23:14 GMT

Even if ViC 2.0 wasn't supported on x64 - it worked at least .. 2.5 doesn't even let you install it which is bad practise ..

Vi is an Enterprise product .. no private person will ever use ESX (legally anyway), a company is more likely to use 64 Bit.

We HARDLY install 32 Bit OS' so now we had to install a 32 Bit server so we can remote desktop to it ...

This is just painful .. I have to connect to the Vi environment remotely when I am traveling ... since G3 isn't really highspeed, I had to install a virtual machine on my (64 Bit) laptop so I can use the vi client ..

Its so far pretty much the first "bad" thing I encountered with VM - but by far the most painful one ..

(oh and the webinterface is no option)

Re: VI Client 2.5 only supports 32bit OS?

jprior — Thu, 27 Dec 2007 22:23:14 GMT

Yes, I am quite pleased that the most problematic part of running VI3 for the last 15 months has been this issue. Quite a nice change from some of the other vendors I've worked with, and certainly the VMware employee's participation in this thread has been better than most - instead of 'SOL, do it our way' there is a recognition that there is action they can take, and a plan to work towards it.

Re: VI Client 2.5 only supports 32bit OS?

nathanbach — Thu, 27 Dec 2007 22:09:16 GMT

Actually I do work for an Enterprise company and my guess is you've never seen the inside of a datacenter. 100% of the Fortune 500 run most or all of their infrasturcture with 64-bit OS on their servers. Ever heard of Tru64? It's been around since 1988 not to mention Solaris, HP-UX and on and on. I work with many of these types of companies and ALL of them run 64-bit Linux in some capacity as well as a ton of UNIX.

You're focusing on the client experience. VMware is an infrastructure product.

Re: VI Client 2.5 only supports 32bit OS?

jprior — Thu, 27 Dec 2007 22:05:41 GMT

Wait, you're gonna flame people asking for 64-bit support claiming that its a tiny minority, and then advocate an even smaller group by asking for Linux / Mac support? That seems to be a bit of a double standard.

Though a full java instance sounds interesting, did you mean like the recent Java 'OS-less' webserver?

Re: VI Client 2.5 only supports 32bit OS?

RParker — Thu, 27 Dec 2007 22:05:41 GMT

Personally I think the big issue is that it only runs on Windows.

I'd love to see the client run on Unix/Linux; if VC could at least use MySQL or some other non-Microsoft db, would be awesome (VC on Unix/Linux would be even better); ANY Macintosh support would be fantastic

Hear Hear!!

That's because it supports .NET. The Database part is a non-issue, they could easily use ANY database, they just wrote it to interface with SQL, but the database could be hosted anyplace.

It would be nice to have a Linux (or non-OS) version.. just java based would be lovely. Macintosh would be awesome. I agree, they need to quit being MS only development, and start toward open source.

Re: VI Client 2.5 only supports 32bit OS?

RParker — Thu, 27 Dec 2007 22:02:48 GMT

Yeah, but it didn't prevent install on 64-bit. Now they specifically try to keep you from installing on 64-bit.

So it wasn't supported, but at LEAST it installed and worked...

Re: VI Client 2.5 only supports 32bit OS?

RParker — Thu, 27 Dec 2007 22:01:22 GMT

Admins use the newest stuff, because Technical people like to test and play with new technology. That's a given. That is the exception not the rule. Also Admins have access to a plethora of OTHER machines you can use to connect to a console, not to mention, the web access is accessible...

The general public that will be connecting and use the VI client (even half of this board are probably students or new customers) that don't care about 64-bit. All they want is to connect.

Since 2.5 is a NEW product, I suspect VM Ware is trying to reduce their installations to 32-bit, probably because adding 64-bit to the mix will introduce twice the amount of problems. This 64-bit (or lack thereof) is temporary. They will support it.. eventually, once it's matured more. There is still some issue with many 64-bit drivers, even Adobe has no native 64 bit flash support.. It's not the end of the world, you have to look at it from VM Ware standpoint.

Maybe they have 64-bit VI Client in the works, but it's just too many problems to tackle all at once.. give them a chance....

Re: VI Client 2.5 only supports 32bit OS?

nathanbach — Thu, 27 Dec 2007 21:59:47 GMT

Well actually the shift to 64-bit has been happening over that same 5-year period in all x86 platforms, Linux and Windows, but more so on the Server side than Client. You can't even buy a decent new x86 server without a 64-bit processor so why not use it? And as for your assertation that new laptops don't support it, I'm writing this on a new HP 8710w running Vista Business 64-bit. I will concur that 64-bit CLIENTs are still in the minority, but that's changing. Within the next 1-3 years as companies "refresh" their hardware/software, 32-bit will be phased out on the client side as well.

I would venture a guess that most high performance users/gamers WANT to run 64-bit and are limited by the developers, their applications and hardware more than a desire to stay on 32-bit. The big issue is usually hardware and drivers not applications. VMware just needs to recognize that the VI Client is an Admin tool and a growing number of admins are running 64-bit and don't want to have to RDP to a server evertime they need to do something in VMware.

Re: VI Client 2.5 only supports 32bit OS?

jprior — Thu, 27 Dec 2007 21:53:57 GMT

Check out some of Dell's laptops, they have a line specifically for Vista compatibilty.

As far as 64bit goes, yes - for desktop and portables, the gaming industry is the driving force. For servers, however, then I would think Microsoft would be a major factor (as in fact they are for gaming, as if you're talking PC gaming, you mean Microsoft), with their given statement of intent to move to 64bit only servers in the next iteration (after Server 2008). Already the preferred download for evaluating Server 2008 RC is 64bit; Exchange 2008 is 64bit.

Modern games are starting to tax 2Gb RAM systems, and with most people buying the dual channel ram upgrades, the next steps are 3Gb or 4Gb. With the price of RAM so low these days, a lot of people may consider it an good investment to buy another 2gb, and find out their desktop only shows 3 - 3.5Gb of the total because of the memory mapping limitations of 32bit Windows. About 18 months ago, 2Gb was considered a huge amount of RAM for a gaming desktop. Course, that was before Vista hit...

Additionally, in the enterprise (the largest OEM market), security is going to affect OS deployment decisions. With microsoft's 64bit kernel inherently more secure than the 32bit one, it become more attractive as a base platform to standardize around. Hence why Dell, HP, etc. offer their desktops in 32bit and 64bit preconfigured formats.

Performance increases are documented for true 64bit game executables. Running 32bit games in emulation under 64bit OS is not likely to show an increase in performance, though the all round computing experience may be enhanced through native services and applications performing better. I am unable to find it now, but Microsoft published a case study of how moving to 64-bit Server 2003 on their WSUS clusters decreased load and increased throughput, serving data faster thant their previous 32bit configuration.

Of course, all the above is my opinion and not necesarily fact, so please enjoy a little salt with it

Re: VI Client 2.5 only supports 32bit OS?

RParker — Thu, 27 Dec 2007 21:46:51 GMT

I can tell you dont' work for an Enterprise class company, because that statement is so wrong, I don't even know where to begin.

Companies use what works, not what people WANT. There is NO reason to shift to 64-bit, for one thing SUPPORT. Who is going to support an entirely new hardware platform, not companies to be sure (Fortune 500 anyway).

In fact, ask ANY Fortune 500 company how many 64-bit systems they support (excluding SUN, Linux, and AS/400) and you will NOT find any, laptops, desktops, even servers. There is just no real need. SAP, Oracle, Microsoft even. go to any of those sites, look up their products, now find how many are 64-bit Code devleopment. I can only think of 2 Microsoft Products, SQL and Exchange that are even written for 64-bit. (Besides the obvious OS)

Companies are not going to use something that is new, especially since the 64-bit hardware is still buggy, there are no apps, and availability of applications are not there, so tell me, where did you get this info? It's not even close to accurate.

The ratio of 64-bit to 32-bit is significantly LOWER than general populace. And the statement isn't "We dont' want you to upgrade", no one is forcing you to use 64-bit, its YOUR choice to use it. VM Ware doesn't want to inherit the problems of THEIR app running on a largely unsupported system, that's where the problem is.

They aren't ignoring the customer base, they are trying to streamline their support, so they don't have to deal with 64-bit issues. It's not supported, so why should they use it?

Besides, 64-bit promised performance enhancement.. that promise was never fulfilled, so other than systems with more than 4G of RAM on a machine, why do you think you need 64-bit? It's a perception, not a fact. 64-bit isn't any better realistically than 32-bit.

Re: VI Client 2.5 only supports 32bit OS?

RParker — Thu, 27 Dec 2007 21:41:11 GMT

Hmm... your view of technology is severely skewed and implausible.

First of all, 64-bit Os has been out for what.. 5 years.. what makes you think there is going to a SUDDEN shift to 64-bit? Hmmm?

When GAME developers see a need to embrace 64-bit only THEN will you see a push. GAMES drive the market, because as you say new customers will want 64-bit GAME support. Hardware gets pushed by GAMES.

Re: VI Client 2.5 only supports 32bit OS?

RParker — Thu, 27 Dec 2007 21:36:48 GMT

This doesn't mean VMware doesn't care about our customers, or for being shortsighted, etc - each support effort requires backend processes and testing to provide true support for a product. In this case 64-bit client support would entail full integration with the vendor OS (Windows and the various flavours of Linux) - not just "get it to work". That's a huge effort if you think about the amount of OS changes that need to be vetted properly to ensure a working product, support processes in the back-end and continuous development. I want to be clear - VMware is not saying "it's just not worth it", we are saying "do we need to shift resources right now?"

Now this doesn't mean we are not going to ever have support for a 64-bit client, but to be frank it will most likely will not occur immediately as requested by some people. We have also seen issues with some of the OS components in the 64-bit environment, hence the OS checker has been activated. What I will ask if it is possible to remove the OS checker restriction to allow customers to "go it alone" with no support, but even that has it's own issues as some people would assume support since it installed. Maybe a warning message with a check-box so you could agree to "go it alone" before install?

Finally, the voice of reason. I knew there has to be at LEAST 1.

Re: VI Client 2.5 only supports 32bit OS?

RParker — Thu, 27 Dec 2007 21:34:49 GMT

Oh yeah... that's professional.. <rolling eyes>

So you are going to forego an upgrade, because you can't simply remote desktop to another machine for the console... Web Access supports 64-bit!

Re: VI Client 2.5 only supports 32bit OS?

RParker — Thu, 27 Dec 2007 21:31:57 GMT

x64 workstations are becoming more and more common.

Common yes, accepted.. NOT!

Wondering if there is a command line switch to bypass the OS check....

There is, it's called VM Workstation 6. Run a VM on your box.. just for the console, problem solved. You are not going to win this 64-bit client thing. There must be a good reason they don't support it.. like .NET has issues, there are MANY problems that certain functions don't support yet.. and since VM Ware has to support ALL issues, they opted to eliminate 64-bit all together. We see it as an inconvenience, VM Ware sees it as support, which costs more money supporting OS configurations which have known issues. Since they DID support it, and they pulled it, there is a specific reason they don't WANT you using it.. In time, it will be supported....

I predict by April there will be FULL 64-bit support.

Re: VI Client 2.5 only supports 32bit OS?

RParker — Thu, 27 Dec 2007 21:27:35 GMT

Same here.

I understand about the 64-bit though, it's flaky. MANY apps don't work on 64-bit, and I have 64-bit Server, that I use for many things, but some things just don't work.

I think VM Ware got tired of supporting issues with 64-bit OS, since their app really doesn't support it. On another note, they could just recompile it.. how hard is that? We have a development shop, and noone supports 64-bit there either, so either there is an issue with 64-bit that we just haven't seen, or there is no need for 64-bit apps. Not one of our customers have asked about 64-bit, not one. And we have a very LARGE customer base....

Re: VI Client 2.5 only supports 32bit OS?

tWiZzLeR — Thu, 27 Dec 2007 21:18:03 GMT

mcadler wrote:
I got VI Client 2.5 running on Vista 64 bit today. It took some effort. The first steps are outlined above.

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.

Good luck. We shouldn't all have to do this. It would be trivial to make an installable version with these changes.

mcadler - This worked like a charm! Thanks for the detailed steps. Also, I thought that I should mention that I had to login as the local Administrator in order to get the VI CLient 2.5 to install and register correctly. Even though I had tried with another local account that had admin rights I could not get it installed correctly until I logged in as localhost\Administrator.

I hope this helps anyone who also ran into this issue.

Re: VI Client 2.5 only supports 32bit OS?

akemp — Fri, 21 Dec 2007 22:25:12 GMT

Schorschi,

Thanks for your comments. I guess short-sighted would be Vmotion, Storage Vmotion, 1st to offer vSMP, 1st to offer 64-bit guest support, 1st to offer shared memory model and many more. I've explained - in detail - the why, support is coming soon.

I don't agree at all with your MS comments as we support more MS operating guest's than anybody - including experimental support for Windows 2008.

Market forces and resources always have an impact on the development roadmap.

Regards,

Andre Kemp
Sr. Product Marketing Mgr. Apac
--
Pardon the brevity, sent from my handheld

Re: VI Client 2.5 only supports 32bit OS?

Crowey — Fri, 21 Dec 2007 00:38:05 GMT

Personally I think the big issue is that it only runs on Windows.

32/64 windows client support ... minor (though admittedly not trivial) issues in my book.

Re: VI Client 2.5 only supports 32bit OS?

clay_combs — Thu, 20 Dec 2007 20:49:00 GMT

I agree Vmware should fix this immediately. I was slammed with this today after my VC 2.5 upgrade. If the client worked on x64 in v2.0 they shouldn't have disabled it in v2.5.

Re: VI Client 2.5 only supports 32bit OS?

Randy_B — Tue, 18 Dec 2007 18:20:01 GMT

I agree that Vmware should make an immediate effort to build a patched version of the client that will run on a 64 bit Windows platform. If it can be done with a few hacks, a patched version, even unsupported, would not be a huge effort to make. While running another VM is a workaround, it also requires another Windows license, which is not trivial.

As far as polling the user community, I have been very involved with Vmware over the last 4 years and no one ever asked me what platforms our administrators are running.

Re: VI Client 2.5 only supports 32bit OS?

david.hittner — Tue, 18 Dec 2007 15:58:31 GMT

I also find the lack of 64-bit support rather short sighted. I suspect quite a few administrators run WinXP x64. WinXP x64 certainly makes testing VM configurations easier by running VMware Server and using the extra memory of your workstation (mine has 8GB). But regardless...

I find it a bit disconcerting that when given strong community feedback that "you've broken software with a mandatory upgrade" that the response was not "whoops, we'll put out a limited patch right away due to technical difficulties, and bring it up to full support in the next release", but rather has been "it shouldn't have worked in the first place, so you'll have to wait until we re-engineer it and release the new version in H2". We have to wait 6+ months for restored functionality??

Kudos for agreeing to fix the problem in the long term, but I really think we need a patch in the interim. Issuing a patch would also improve your credibility in the era of multiple Virtual software vendors. :-))

Re: VI Client 2.5 only supports 32bit OS?

mcwill — Tue, 18 Dec 2007 08:27:56 GMT

Perfect!

Step 4 was what I was missing before, but with your instructions I have now been able to run the VI client under Vista x64.

Thanks,
Iain

Re: VI Client 2.5 only supports 32bit OS?

mcadler — Tue, 18 Dec 2007 04:09:48 GMT

I got VI Client 2.5 running on Vista 64 bit today. It took some effort. The first steps are outlined above.

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.

Good luck. We shouldn't all have to do this. It would be trivial to make an installable version with these changes.

Re: VI Client 2.5 only supports 32bit OS?

Schorschi — Tue, 18 Dec 2007 02:48:28 GMT

The short-sighted development of VMware continues to amaze me. In this day of .NET based application development, you have to go way out of your way to not get 32bit and 64bit applications by default. This can mean only one thing, VMware has code that is so low level, that is designed so bad, they don't want to rewrite it? What other conclusion is there? They had to have a reason, and I am sure it was in some part based on VMware refusing to embrace Windows operating system in any serious way, they prove this day in and day out. I would be surprised if even 5% of VMware's entire development resources are Windows savvy. I believe this, given the absolutely horrible performance and scaling that VCB and VirtualCenter, which are effectively Windows based solutions.