Follow Slashdot blog updates by subscribing to our blog RSS feed

 


Forgot your password?
Close
typodupeerror
×
Microsoft Virtualization Windows Bug IT

Security Patch Breaks VMware Users' Windows Desktops 80

Posted by timothy from the outside-design-specs dept.
jbrodkin writes "VMware is telling customers that two Windows 7 security patches have left VMware View users incapable of accessing their Windows desktops. Security updates issued on Patch Tuesday fixed Windows but broke the VMware View connection between users' PCs and remotely hosted Windows 7 desktops. Users will have to upgrade VMware View or uninstall the Microsoft patches in order to regain access to their desktops."
This discussion has been archived. No new comments can be posted.

Security Patch Breaks VMware Users' Windows Desktops More

Security Patch Breaks VMware Users' Windows Desktops

Comments Filter:

  • VMWare is not VMware view (Score:5, Informative)

    by Anonymous Coward on Thursday February 10, 2011 @05:12PM (#35167634)

    VMware view is way to access remotely hosted virtual machines.

    VMWare workstation and server are not affected.

    VMWare view clients just need to be updated.

    • Re: (Score:2)

      by Khue ( 625846 )
      I was actually going to mention this. VMware actually typically assumes you are on the latest version of their software products anyway. After reading the article I didn't think that this was as big of a catastrophe as some of you have made it out to be. Upgrading the VMware View client on the virtualized device doesn't really sound all that difficult and I highly doubt that this is bringing anyone who matter's production system to it's knees. Also, stop upgrading everything on the day patches are released.

      • Re: (Score:2)

        by mwvdlee ( 775178 )

        VMware actually typically assumes you are on the latest version of their software products anyway. [...] Also, stop upgrading everything on the day patches are released.

        Can you see the irony?

  • Broke a few things so far (Score:5, Insightful)

    by digitalhermit ( 113459 ) on Thursday February 10, 2011 @05:12PM (#35167638) Homepage

    At some point the responsibility shifts from Microsoft to VMWare. Where the responsibility for alerting customers lies is maybe not clear yet.

    The update has broken a few things for me. Half my desktop gadgets are not functioning properly. There are some other glitches that I noticed with my AV software, though I'm still confirming on other PCs.

    • Re: (Score:1, Insightful)

      by nemesisrocks ( 1464705 )

      The responsibility absolutely is VMWare's. Large software companies generally have access to early releases of the Microsoft patches, specifically so they can perform whatever testing they need.

      Sounds like in this case, VMWare didn't bother doing their testing (or that testing was too costly), and is now trying to blame Microsoft for their fuckup.

      • Re:Broke a few things so far (Score:5, Informative)

        by phoebus1553 ( 522577 ) on Thursday February 10, 2011 @05:35PM (#35167924) Homepage

        The responsibility absolutely is VMWare's. Large software companies generally have access to early releases of the Microsoft patches, specifically so they can perform whatever testing they need.

        Sounds like in this case, VMWare didn't bother doing their testing (or that testing was too costly), and is now trying to blame Microsoft for their fuckup.

        Lets try to RTFA before assuming...

        However, Lee said the Patch Tuesday security updates included the "early release of updates anticipated in" the Service Pack, which is due out Feb. 22. Lee said VMware provided its own VMware View update to customers "within 24 hours of the Microsoft security patch, in an effort to minimize customer impact."

        Sounds like MS did an early release of things VMWare knew was coming, but not expected until later. You're right that they were testing, hence the speedy update. Sounds like MS just released early and didn't communicate the release, so shift that blame back to MS.

        • Re: (Score:2)

          by jovius ( 974690 )

          Sounds like MS just released early and didn't communicate the release, so shift that blame back to MS.

          Lack of communication. And now she want's to talk about issues. I decided to rather have her neatly framed on my desktop than in control.

        • Re: (Score:1)

          by wharlie ( 972709 )

          There is shared responsiblity.
          Some responsibility also lies with the users.
          VMware View is an enterprise product, not used by home users.
          All enterprises should thoroughly test any patches they deploy, this would be picked up instantly.
          More of an annoyance than an issue really.

    • Re: (Score:3)

      by syousef ( 465911 )

      At some point the responsibility shifts from Microsoft to VMWare. Where the responsibility for alerting customers lies is maybe not clear yet.

      The update has broken a few things for me. Half my desktop gadgets are not functioning properly. There are some other glitches that I noticed with my AV software, though I'm still confirming on other PCs.

      You know what. I'm tired of running an experimental desktop. I have had enough things break that I view the patches as a greater security risk than the flaws they're meant to fix. I'm sick of it.

    • "At some point the responsibility shifts from Microsoft to VMWare. Where the responsibility for alerting customers lies is maybe not clear yet"

      At what point did VMware, invent a time machine, go back in time, inflitrate Microsoft and hack out a Windows 7 security patch that broke VMware.

      "VMware is telling customers that two Windows 7 security patches have left VMware View users incapable of accessing their Windows desktops"

      • Re: (Score:2)

        by Nevo ( 690791 )
        Maybe VMWare was doing something that the documentation says you shouldn't do, and the security patch came along and actually started enforcing what the documentation said. Don't be so quick to judge MSFT. Without further details it's not possible to know whose fault this is (as if assigning blame is productive).

    • At some point the responsibility shifts from Microsoft to VMWare. Where the responsibility for alerting customers lies is maybe not clear yet.

      The update has broken a few things for me. Half my desktop gadgets are not functioning properly. There are some other glitches that I noticed with my AV software, though I'm still confirming on other PCs.

      And those gadgets that broke. Are they MS gadgets, or third-party? If MS, then I think it's safe to say that MS screwed up somewhere...

    • At some point the responsibility shifts from Microsoft to VMWare. Where the responsibility for alerting customers' lies is maybe not clear yet.

      (Was I the only one who read the bold section as such?)

      I'll take full responsibility for notifying you of which customers are lying. IMHO, this should have been the burden of the headline author: "Patch breaks VMware" is misleading -- The headline should read: "VMware Viewer Client Broken by Windows Desktop Security Patch" or simply "Windows update breaks desktop users' software, once again". Patch the client (viewer), or remove the client machine's security patch (not the remote server) in order to regain

  • Its a good thing we are so slow at integrating new software. We only have 3 Windows 7 machines in VMWare the rest are all Windows XP!

  • Not the whole story.. (Score:3, Informative)

    by Anonymous Coward on Thursday February 10, 2011 @05:43PM (#35168024)

    They have an updated build of the View Client available for download that fixes the problem.

    Good yes?

    Not really. The updated client has a new build number but the SAME version number in the MSI! Why does this matter? It matters because the MSI will not UPDATE an existing install. It looks like the same version so you have to uninstall and then reinstall.
    (No I have not tried MSIEXEC /FA option to try and force a reinstall of the same versions, that is next on my list.)

    They had the fixed build quick enough that I am guessing that this issue was known prior to today. It is just crazy that they did not change the version number so that the tools for managing applications (SCCM et al) can detect that a new version is available and install it.

    Even their own View Connection Servers which check the version of your View Client when you talk to them will not detect that a new version is available.

    Crazy!

    Jorgie

  • Where's the story? (Score:3)

    by TrancePhreak ( 576593 ) on Thursday February 10, 2011 @05:52PM (#35168122)
    They already fixed it according to the summary, so where's the story? Operating system updated, breaks software. Software gets updated.

    • Re: (Score:1)

      by Anonymous Coward

      The news is that they released a new BUILD of the client, not a new version.

      As I said in my note above, since it is a new build not a new version, you cannot just install it, you have to uninstall first AND VMware's own tools for checking the version of the View Client tell you that you are up to date even if the Connection Sever has the new build and your workstation has the old one.

      Jorgie

  • They're a lot more secure that way!

  • New Borg Icon Sucks (Score:1)

    by Anonymous Coward

    WTF? The old Borg icon is much better. Did the creator of this new one not even watch Star Trek and realize borg skin is pale white/blue?

    jeez

  • Recent patches seemed to have buggered a Win7 VM I had running in VirtualBox. It wasn't a total buggering but the old configuration of the VM was fine (well, fine enough) until recent patches made it unusable. It bogged down and ground to a halt until I went into safe mode and disabled just about everything that was running.

    Sound like it's not just a vmware problem. Wonder if bare metal users were impacted too.

Slashdot Top Deals

Never test for an error condition you don't know how to handle. -- Steinbach

Close