Security Patch Breaks VMware Users' Windows Desktops 80
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."
VMWare is not VMware view (Score:5, Informative)
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:Broke a few things so far (Score:5, Informative)
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.
Not the whole story.. (Score:3, Informative)
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. /FA option to try and force a reinstall of the same versions, that is next on my list.)
(No I have not tried MSIEXEC
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