We have a View 4.6 client/agent desktop that is crashing when printing using Internet Explorer to a local printer. Priinting with Firefox to any printer is fine, printing with any other application is fine, but printing in IE to the local printer causes the session to crash. I have the backend upgraded to View 5, but not these desktops (yet).
I assume you mean the session disconnects, but the Windows OS is still online?
What is the printer model?
Are you using Thinprint?
According to the helpdesk technician who is working on this, he said that in IE you try to print anything and the print dialog comes up. You tell it to print and the printer icon comes up in the tray. Then the screen goes black and eventually the session disconnects. It does appear that you can log back into the desktop right away.
This is a HP 2200 printer, connected locally. If he tries to print to any network printer it is fine. I installed the ThinPrint piece during the View Agent installation, but I am not "using" it in the sense that I have not set anything up specially to do anything with it. When he did a test page it showed some things that looked like ThinPrint drivers, such as "Printer created by TPAutoConnect" and "Printer model: TP Output Gateway".
Can you determine what the printer is named? if it's being redirected by thinprint it will have # and a number in the name. You could also try stopping the thinprint services on the desktop and see if the printer is still there.
If the printer is connected via USB you could try USB redirection to see if that corrects the issue.
The name of the printer is "HP LaerJet 2200 Series PCL 5#:1". It is being redirected by ThinPrint. So the question is why printing to a local printer would cause the session to disconnect, and only in IE.
Can you test disabling thinprint, adding the driver to the VDI machine, and letting the RDP printer redirection make the printer available inside the VDI machine. If we can narrow it down to only the thinprint mapped printer it would help. With that being said there isn't a lot of troubleshooting that goes into thinprint so a ticket with VMware may be necassary.
