[HELP] My big problem with Horizon 7.4 - Printer Redirection

[LiaoYuRuei]

Hello, I have a big problem with Horizon 7.4 that I can't see the virtual printer in my virtual desktop.

My Horizon Components:

1.[Hypervisor] VMware vSphere ESXi 6.5

2.[VM] VMware vCSA 6.5

3.[VM on ESXi 6.5]  SRV1 (AD、DNS、DHCP) - Server 2008R2 Standard

4.[VM on ESXi 6.5] SRV2  (Connection Server) - Server 2008R2 Standard

5.[VM on ESXi 6.5] SRV3 (Composer、SQL) - Server 2008R2 Standard

6.[VM on ESXi 6.5] TPL (Horizon Agent for cloning) - Windows 7 Pro SP1

7.[Physical PC]  Horizon Client - Windows 7 Pro SP1

The step I deploy Horizon as follow:

1.Install the virtual machine environment, such as ESXi6.5, vCSA 6.5

2.Deploying VM OS and Install VMware Tools on SRV1, SRV2, SRV3, TPL...etc

3.Add AD、DNS、DHCP role on SRV1, and create the OU for Horizon

4.Join AD member (SRV2, SRV3, TP)

5.Install Connection Server on SRV2

6.Install SQL Server and Composer on SRV3

7.Install Horizon Agent on TPL and snapshot

8.Setting View Administrator (add trial license, add vCenter, add desktop pool ..etc)

After the Horizon environment setup, I used Horizon Client login into the virtual desktop,

I can't see the printer in my virtual desktop.

Some solution I have tried:

https://kb.vmware.com/s/article/1027293

https://kb.vmware.com/s/article/1013520

1.Check the services are running, and trying to restart these services,

• TP VC Gateway Service
• TP AutoConnect Service
• Print Spooler service.

2.Reinstall Horizon Agent on TPL.

3.Reinstall Horizon Client on physical PC.

4.Increase timeout value in registry

Change HKLM\Software\ThinPrint\TPAutoconnect\TimeOutClient from 600000 to 900000

Change HKLM\Software\ThinPrint\TPAutoconnect\TimeOutClientExecution from 600000 to 900000

It still doesn't work....

And some papers I saw that virtual print setting is on the Horizon client,

but I can't find it..

Does anyone have good solutions?

Or is any step I setup the Horizon environment wrong?

[ArnoM]

Do you have a Horizon View policy which disables printer redirection in place?

Do you use VMware UEM with smart policies, maybe printer redirection is disabled in there?

I've also seen before, if you open an application (for example notepad) and choose print, you do see the redirected printers in there.

[LiaoYuRuei]

Ok, I don‘t change any Horizon policy, but thanks for your reply, I think I should check my horizon policy.

And I do not install Horizon UEM, is the UEM necessary for print redirection?

[ArnoM]

No, UEM is not necessary.

You can check within the image (log on with an administrator) and run rsop.msc to look at the applied policies.

[LiaoYuRuei]

Ok, I’ll try some days later, thanks for your reply!

[LiaoYuRuei]

Hello, ArnoM​

​Appreciate for your help, I've tried a lot of ways, ex:

​- change vSphere hypervisor version (ESXi version)

​- change Windows server version 2008R2/2016

- ​does no install VMware Tools to assure the ThinPrint feature is installed by Horizon agent

​- download the GPO bundle from VMware and install it to change policy

​- and restart the TP service on the VDI, etc...

​, but I still couldn't find a way to solve it.

Only a way to see the redirected printer was using the RDP protocol (I can't see redirected printer by Blast Extreme or PCoIP.)

​Recently, I rebuilt the environment and tried the tpautoconnect command according to ​VMware Knowledge Base, the result as follow:

​Have you ever seen the message before?

And do you have experiences about nested ESXi? My Horizon 7 environment is run on a nested ESXi environment.

​(An ESXi 6.5 VM run on an ESXi 6.5 with physical Server, ​and Horizon 7 on the ESXi 6.5 VM. )

[bdeksnys]

Our enterprise is experiencing this issue as well.  I am surprised to not see more posts about it.  Does anyone have any insights into this?

For me, the best way to describe it is that users infrequently do not have their printers available inside of their VMware session.  Sometimes, restarting the print spooler in the VMware session corrects the issue.  When that does not work, restarting both VMware and their computer seems to be the only fix.  This is very frustrating to our users and I would like an explanation as to how to prevent it from occurring.

We are running View7, with Win7 guests, on Win7 clients, using Horizon 4.7.

[LarryBlanco2]

Just a shot in the dark.  Firewall?   Port blocked on the clients?    Maybe the AV has a firewall blocking?

LB

[cbaptiste]

This issue exists in 7.2.0 as well. I was told it would be resolved in 7.3.x and later. I guess not. Currently in production we are using the tpautoconnect /v through UEM as a reconnect trigger as work around. Could also be done as Windows unlock task. It only appears to now show at reconnect for us. Work fine at initial logins.

[afelix123]

Hi,

I saw Thinprint issues when using Win7 32bit as desktop VM OS. Do you have 32bit or 64bit Windows 7?