Printer Redirection Not Working On Reconnect

[jmatz135]

We are running Horizon View 7.2 and UEM 9.2.  When a user logs into a VDI desktop they get all of their printers that are connected to their local desktop mapped to the VDI desktop and everything works properly.  The problem is that when they disconnect and then come back later and reconnect to that same desktop the printers do not get mapped to the VDI desktop every time.  I'm not even sure where to look for a solution to this.  Anyone have any ideas?

Edit:  After further analysis this seems to only happen when using the PCOIP protocol to connect to the desktop.  If I switch to the Blast protocol it seems to map the printers properly every time.

[AishR]

Please refer KB Printers are not mapping to VMware View Client desktop virtual machines (1013520) | VMware KB  for the solution

[jmatz135]

Yeah, I've seen that.  Steps 1 and 2 are out.  Step 3 works, but I can't really have users doing that all of the time.  I'm going to try Step 4 but I have to place that in the master image so I haven't gotten to it yet.

[jmatz135]

Step 4 doesn't help the issue.

[techguy129 · Accepted solution]

We had the same issue. We rolled our agent back to 7.1 Vmware support said there is an issue with thinprint in 7.2.

Also, we had other USB issues related to UEM 9.2 that were fixed with using this workaround

Re: Appstack and Horizon USB issues when UEM in installed but not configured

[jmatz135]

That would make sense.  Haven't really seen it until now, but we rolled out the 7.2 agent pretty recently and it seems to correlate to the time frame.  I'll have to check if a pool with the 7.1 agent has the same issue.

[jmatz135]

Also, they released UEM 9.2.1 recently that has some fixes to USB in the release notes.

VMware User Environment Manager Release Notes 9.2.1

[jmatz135]

Yep, so it is the View Agent 7.2 that breaks it.  Deployed a pool with Agent 7.1 and it works every time.  At least I know the issue now, too bad it will be months until a fix is in place.

[thebenjohnson]

I just provided feedback to VMWare article Printers are not mapping to VMware View Client desktop virtual machines (1013520) | VMware KB
Yes, the article is only for view versions up to 5.x but it's the best KB that deals with this issue in my opinion.

We arrived at a place that allows thin print to work consistently for our environment, here's the short of it:

5 pools

350+ Desktops

View Agent 7.2

Printer will *sometimes* map over but guaranteed to drop off and be nearly impossible to get back (only to have it drop again, and that's if you're lucky).

Found on isolated cases, connecting using the VMWare Blast protocol allowed the local printer to map to the Virtual and stay on the virtual.

Tested more machines, more successful.

Changed the default connection protocol for the pool to VMWare Blast protocol and no additional issues reported.

Still observing any potential impact to performance but so far it's been smooth.

RDP seems to redirect as well without dropping the printer.

Anyone else have success trying this?

[jmatz135]

This is an agent 7.2 issue.  If you upgrade to the agent 7.3.1 the issue is fixed.