Security Patch Breaks VMware Users' Windows Desktops

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."

Comments

VMWare is not VMware view

[Anonymous Coward]

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:VMWare is not VMware view

[Khue]

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. Second movers are sometimes the winners.

Broke a few things so far

[digitalhermit]

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:Broke a few things so far

[phoebus1553]

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:Broke a few things so far

[syousef]

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.

Re:BYOD!?

[Penguinisto]

One would think that Microsoft would beta-release their patches to the really big software partners, so that at least some sort of testing could happen.

Then again, the conspiracy theorist side of me keeps saying that maybe Microsoft doesn't mind if the biggest competitor to Hyper-V suffers a few PR flubs once in awhile...

Re:That Microsoft Icon

[lordshipmayhem]

Why wasn't Slashdot's Microsoft icon completely scrapped with the re-design?

That thing looks so incredibly dated and anachronistic...(snip)

Sort of like Microsoft...

Not the whole story..

[Anonymous Coward]

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?

[TrancePhreak]

They already fixed it according to the summary, so where's the story? Operating system updated, breaks software. Software gets updated.

Re:Old wine in new bottle?

[kikito]

"At that point all the legacy unportable corporate applications that need IE6 will run in some kind of frozen in time universe"

That point is here already. There are companies effectively frozen in time, from the IT point of view.

Re:That Microsoft Icon

[Larryish]

The current Microsoft icon needs to be replaced by an animated GIF of Steve Ballmer doing the monkey dance.

Re:That Microsoft Icon

[MobileTatsu-NJG]

This "my software is better than yours" sentiment with people arguing how evil Apple and MS are is annoying enough, does slashdot really have to propagate this with that icon?

Yes. Slashdot serves ads while we fanboy-fight.

Re:BYOD!?

[cusco]

They do, most of the patches are in the hands of their larger partners for a month before release. Not sure if VMWare is not considered a partner, or if they just didn't do extensive enough testing. That they already have a fix for View suggests that they knew there was going to be a problem but didn't want to push it out into the real world until they had confirmed that it was an issue outside the lab.