VMware Horizon Community
mwandell
Enthusiast
Enthusiast

VMWare Integrated Printing not working - Horizon 7.12

I upgraded my Horizon Environment to 7.12 and updated my image with Agent 7.12.  I switched from Virtual Printing to Integrated Printing to get the updated features. When I connect, I do not get any printers redirecting and cannot figure out why.  I cannot find any logs or errors that may be causing this.  Thanks in Advance for any assistance with this. 

Reply
0 Kudos
7 Replies
Shreyskar
VMware Employee
VMware Employee

Which protocol are you connecting with?

Reply
0 Kudos
mwandell
Enthusiast
Enthusiast

I have tried connecting with all of the Protocols.  RDP does give me redirected printers, but it appears that they are RDP printers and not the integrated printers.

Reply
0 Kudos
zhanghui1
VMware Employee
VMware Employee

Please post the latest log file print-server*.log under C:\ProgramData\VMware\VDM\logs

It's better to change log-level to "verbose" firstly and then reconnect to generate a new log file.

Please set on agent side as below:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VDM\PrintRedir

LogLevel       REG_SZ                       verbose

Reply
0 Kudos
mwandell
Enthusiast
Enthusiast

@zhanghui1 Attached are the requested logs

Reply
0 Kudos
zhanghui1
VMware Employee
VMware Employee

Seems the print spooler service is not running on the agent side.

Please double check it. If this is true, you can:

1. Reboot agent or

2. Start the service manually.

Reply
0 Kudos
mwandell
Enthusiast
Enthusiast

I manually restarted the Agent, Print Redirection Service, and Print Spooler and then logged in. This did not work unfortunately. Nothing new in the logs either

Reply
0 Kudos
zhanghui1
VMware Employee
VMware Employee

Before you manually restart the service, it's stopped or started? From the log, it showed the RPC 1722 which means the print spool service is not running.

Another finding is after the session connected, it immediately disconnected, I don't know what caused disconnect happening yet.

Now please set the log level on both client and agent sides. (same setting in the registry) and collect the logs for both client and agent.

Please clear all the log on the client sides firstly and then retry to collect all the files under C:\ProgramData\VMware\VDM\logs.

At least you need to collect 1 print-client*.log file and 2 print-vdp*.log files there.

Thanks

Update:

The disconnect is caused by the client.  On the client-side some error happens, so the client tells the agent to stop, that's why the connection is closed.

What's the client's version?  I can know it once I get the client logs.

Reply
0 Kudos