VMware Horizon Community
Cronistar
Contributor
Contributor

View 4.5 + Latest Windows Updates != :)

Anyone having pains after the latest set of Windows Updates for Windows 7? I'm seeing a spattering of clients having issues with the View 4.5 client freezing up.  I noticed there was an IE update, looks like to version 8.0.7600.16385.

Also, we're seeing event log errors that are consistent with haivng IE 9 beta installed, such as:

backtrace[07] frame 0x04f5f91c IP 0x02df9be2 params 0x4f5f954 0 0x1 0x18cb1d8 ??? [C:\Program Files\VMware\VMware View\Client\bin\wswc_http.dll base 0x02df0000 0x0001:0x00008be2]

Anyone else seeing this?

Reply
0 Kudos
30 Replies
grossag
VMware Employee
VMware Employee

Yeah this issue is similar in cause to VMware KB 1028650.  Microsoft KB http://support.microsoft.com/kb/2482017 breaks the Windows View Client.  Unfortunately running in compatibility mode isn't a workaround for this new issue.

Reply
0 Kudos
Cronistar
Contributor
Contributor

Any ideas of a potential workaround for the time being, aside from a ThinkApp package? Is there a timeframe on an updated client?

Reply
0 Kudos
grossag
VMware Employee
VMware Employee

Nothing yet, but we are taking this very seriously.

Reply
0 Kudos
thorwitt
Contributor
Contributor

Same problem here, getting a lot of calls from our Win7 remote users.

Login to view security server hangs no response from the view client.

Event log shows this:

backtrace[01] frame 0x02c1f694 IP 0x76404e05 params 0x7640ac78 0x764bb194 0x1f1940 0 GetUrlCacheHeaderData + 0x08d0 [C:\windows\system32\wininet.dll base 0x76400000 0x0001:0x00003e05]

Hope we can get a fast solution for this. A lot of from our road warriors can't work!

Reply
0 Kudos
mittim12
Immortal
Immortal

Hey Guys,   I just wanted to drop a quick thanks for putting this out there.  I had one instance this morning and I remembered reading over this thread last night.  

Reply
0 Kudos
grossag
VMware Employee
VMware Employee

VMware KB article 1034262 is up with information about this issue.  The workaround it currently has is to uninstall the Microsoft patch 2482017.  I will let you know when we update it with a better workaround.

Reply
0 Kudos
towlesd
Contributor
Contributor

I already worked out this issue this morning.

http://www.christowles.com/2011/02/vmware-view-windows-7-client-cant.html

You actually need to uninstall 2 KBs


KB 2482017
KB 2467023

Copied from my later post:

I noticed a few people asking how to host the new Vmware Client build so that their users could download it. I updated my Vmware View server's Web Site to correctly give the new Client build and wrote up a how to here. Its a really simple process and doesn't take but 2 minutes to complete.

http://www.christowles.com/2011/02/vmware-view-45-client-353760.html

Message was edited by: towlesd

Reply
0 Kudos
DanoYWG
Contributor
Contributor

I was able to get it to work by running in Vista SP2 compatibility mode and checking the Run as Administrator checkbox, but I'll try removing those two updates and see if it will work normally.

Thanks!

Reply
0 Kudos
grossag
VMware Employee
VMware Employee

VMware KB article 1034262 has been updated with a link to a build containing the fix.  Keep in mind that the version of the build with the fix is still 4.5.0 so you will not be able to upgrade from View 4.5.0 GA build to this build.  Instead you will have to uninstall the View 4.5.0 build and then install this new build.  We understand this is a pain for users so we are looking into more routes.  But this build with the fix is your best bet now.

Reply
0 Kudos
grossag
VMware Employee
VMware Employee

Thanks for letting us know.  We have updated the KB to call out both of those Microsoft KB's as causing problems as well as providing a build with a fix.

Reply
0 Kudos
foodandbikes
Enthusiast
Enthusiast

Is there a way to script a removal of the current View client?

The install options allow for silent install and other items, but I haven't seen a switch for "remove previous version" or similar.

It's gonna be a huge PITA to have to manually remove the client from PCs.

Reply
0 Kudos
libbycm
Contributor
Contributor

Glad to see a patched client is out.. it works fine.

However, this is only the basic client.  Will an updated build of the Local Mode client follow soon?  Is there an ETA?

Reply
0 Kudos
grossag
VMware Employee
VMware Employee

Do you have users who need a patched build of the Local Mode client?

Reply
0 Kudos
grossag
VMware Employee
VMware Employee

Yes I believe this is possible.  This is what someone on our installer team told me:

--------------------

The silent uninstall is common with any other MSI packaged product. 'Msiexec /?' tells them how. They will need the installer MSI file or product code for the product version they want to remove. Getting the MSI involves performing an administrative installation using:
   VMware-viewclient-4.5.0-nnnn.exe /a
The UI will prompt for a extract location and expand the content there. Now they can pass the MSI file location as an argument to msiexec which in turn will read it from there.
   msiexec /x <path_to_product_msi_file>
This involves making the MSI file available to the guest which is not that convenient for an admin. The alternative is to peek at the extracted MSI file with an MSI viewer like Orca and read the ProductCode property value from the Property table. The resulting uninstall command can be easily pushed to any remote machine/VM. For the 4.5.0 client this would be:
   msiexec /x {62BC4171-CE82-4D7E-BA13-09E39234DF7C}
A third approach would involve locating the uninstall command in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall key. Searching for the Product name will reveal a key there with a UninstallString value that contains a ready to run uninstall command. This is what the command being issued when removing a program using the Add/Remove Programs Control Panel applet.
Once they have the uninstall command they can use the MSI online reference (http://msdn.microsoft.com/en-us/library/aa372024.aspx) to see what other command line options might be of interest for them.
Reply
0 Kudos
foodandbikes
Enthusiast
Enthusiast

Thanks grossag.

I've been digging around and found another way to do it with VBscript.

Here's the code. Note, due to word wrap, the below code may need to be altered.

strComputer = "."
Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")

Set colFeatures = objWMIService.ExecQuery("Select * from Win32_Product Where Name = 'VMware View Client'")

For Each objFeature in colfeatures
     objFeature.Uninstall()
Next

Reply
0 Kudos
libbycm
Contributor
Contributor

Yes, we have several users (myself included) using the Local Mode client as part of some internal VDI proof of concept testing we started a few weeks back, so the windows patches sort of killed us..

Reply
0 Kudos
mittim12
Immortal
Immortal

It would be nice if a login wasn't required to download the updated client.  This way I could just point my remote users to the link instead of having to download it and determine a method of getting it to them. 

Reply
0 Kudos
libbycm
Contributor
Contributor

How about downloading it, putting it up on an internal IIS/apache server, then sending the link out? Smiley Happy

Reply
0 Kudos
grossag
VMware Employee
VMware Employee

The View Connection Server already serves up the binary when users enter the address in a web browser.  You can just replace the existing 4.5.0 client binaries on the server with the updated binaries (although you may have to rename them to be the same name as the previous binaries) and I believe it will work correctly.  If you want more directions, let me know.

Reply
0 Kudos