Thank you VMWare.

This time I will be quick. Over the weekend I upgraded my VMWare ESXi environment at home and from that end, everything worked smoothly (yes I know most of the time upgrading VMWare stuff is not really that easy). But as with anything that usually comes out from 3401 Hillview Ave, Palo Alto, CA, something wrong had to happen.

VMWare had MONTHS to fix the freaking issue with their VSphere Infrastructure Client or whatever that is called now (as they now copy everything Citrix does, they started changing names – word on the street is VMWare ESXi will be renamed VMWare SEXi and VSphere will become VOval) when on Windows 7.

Of course I am running Windows 7. Windows XP, according to my daughter, is “so last year” so I moved everything I have to Windows 7. Once you are in Windows 7 land the VIC (Virtual Infrastructure Client Crap) does not work anymore and when you try to logon it throws one of these really useful, easy to understand error messages. Why not show a simple window that says “You are screwed. Thanks for using VMWare.”?  

Thank Lord there is a fix for what lazy VMWare screwed up. You need to grab a DLL from somewhere and change a config file to get that crap working again. All explained here.

Once I did that, everything is now up and running again. And on Windows 7.

Please do not tell me you need Windows XP Mode on Windows 7 to fix this crap VMWare.

Virtualization is cool and great. But using it to fix shit you created in the first place, is not cool.



3,983 total views, 2 views today

9 Replies to “Thank you VMWare.”

  1. Have you every tried laying the blame with Micro$oft for building an OS that doesn’t support already written applications? As far as I recall, the vSphere Client was release BEFORE WINDOWS 7.

    1. Hi Rynardt! Here I do not think it is really the case. This is a common practice in the industry. Let’s take a look. Several applications now do not work on OS X 10.6 Snow Leopard but they did work on 10.5 Leopard. Several applications that worked under Ubuntu 8.x now do not work on Ubuntu 9.x. Several applications that worked under Windows XP now do not work on Windows Vista or Windows 7. Even things that worked on VMWare ESX 2.5 did not work properly on ESX 3.5. Why is Microsoft any different here? No differences at all.
      OSs evolve, the same way applications do. When a major vendor is coming out with a major release for something, it is expected the other players on this Ecosystem will start working on the new OS, when still in Beta, to make their products work.
      Do you think all the companies like Veeam, Vizioncore and so on wait for VMWare to RTM the next version of ESX to then start checking if their products work with it? I do NOT think that is the case. As soon as VMWare releases Beta code to developers these companies are all over, to make sure their products work with the next release. Definitely not the case here. VMWare had MONTHS (at least six as already mentioned) to fix a very simple thing. Why VMWare is different then everyone else I have no clue. 🙂

  2. So.. you expect VMWare to support a Microsoft operating system that’s not actually had it’s official release yet? Patience is a virtue.

    1. Hey V.M.Ware! Well I expect at least VMWare to start thinking about supporting a major OS being released by a major company that for several reasons owns 90% of the desktop market, especially when all that takes, at least as a workaround, is copying a DLL and changing a text file. Plus we are not talking about an OS that has just been released to Beta. Nope. It is already in RTM and this issue has been around for at least 6 months. If it took me 2 minutes to fix it, why would be a big deal for VMWare to get it fixed? That is my point.

  3. “Several applications that worked under Windows XP now do not work on Windows Vista or Windows 7” — So in other words what you are saying is that all application vendors who’s applications don’t yet run on Windows 7 are lazy then? Why single out VMware? You then go on to say that VMware is different than everyone else, but in the same reply you say several applications now do not work under VISTA and Windows 7? So matey, tell us which one of the two points you made in your reply do you stand by?

    VMware (and any other vendor for that matter) develop their applications, and they get to call if and when they will support an operating system for their application. It’s as simple as that. They don’t owe you anything. If you really hate VMware this much, I recommend you uninstall their products straight away and go somewhere else. They are not forcing you to use their products, and I’m sure they won’t miss you when you’re gone.

    As for Victor’s point (who’s name isn’t really Victor, if you look carefully), if an OS is not yet released to the general public and certainly not yet not in VMware’s list of supported operating systems, then VMware has no obligation to support their applications on such operating systems. I completely agree with “Victor”.

    P.S It’s not called the vSphere Infrastructure Client, it’s just the vSphere Client.

    1. No that is not what I am saying. 🙂 What I am saying is all major ISVs do take new major OS releases seriously. I do not expect a small software company to have their products certified for Windows X, whatever X is, before its release date. That is not the case.
      But I do expect major software companies to start making their products compatible with major OS releases from other major companies, especially when that company owns 90%+ of the desktop market.
      Did I mention I hate VMWare anywhere on my post? No as far as I know. I just do NOT like certain things they do every once in a while.
      The same way I do NOT like things that Microsoft did (very similar to this if you remember when Windows Server 2008 came out and Windows XP Pro clients did NOT have an updated RDP client available).
      I am not here to pick on any vendor per se. If you ever watched any of my presentations at BriForum you would understand that I am very honest about ALL vendors, on what I like and what I dislike. And more than that I am aware there is no perfect software vendor. Microsoft or VMWare. 🙂

  4. I have to agree with he author, it is absurd. VMware released the broken client after Win 7 was already at RC stage. It seems like a relatively simple fix, and they haven’t bothered to spend any time on it. That is not very forward thinking at all. The funny thing is that out of all the applications I use, Vsphere Client is absolutely the only one that won’t run on Windows 7.

    This leads to two points

    1- It is almost certain it is VMware’s faulty code that broke, If MS had changed .net outside the spec, it would have broken far more apps than Vsphere Client.

    2- With Windows 7 being by all accounts the most backward compatible OS Microsoft has ever released, adoption will be quick. Every tech I interact with is using it as their primary system by now. We actually have to hunt for a Vista or XP machine. VMware should wake up and realize the customers for the vsphere client are techs, techs that will be running newer OSes.

    Having it broken for a few weeks was understandable, several months is absurd and seriously makes me question VMware’s ability to stay ahead of the curve in technology. If they are not nimble enough to have a patch available by now, well that doesn’t look good at all.

  5. Of course if VMWare would just release a vSphere client for OS X, then all this Windows vista,xp,7 stuff wouldn’t be an issue 😉

    But seriously, why does VMWare not support a native OS X client so you can sit on your cushy chair surfing the interwebs and still be in command of all your VMs with painless ease.

    Bring on a native OS X client for ESX/ESXi/Virtual Center!

Leave a Reply

Your email address will not be published. Required fields are marked *