VMware Horizon Community
virtualdylan
Contributor
Contributor

PCoIP virtual printers?

Hi everyone, I'm having a problem with virtual printers not being created when I use PCoIP to connect to my Virtual Desktops. I'm using 4.0.1 so it's supposed to work. I found this: http://communities.vmware.com/click.jspa?searchID=8235807&objectType=2&objectID=1479938 but alas, rebooting the guest OS 5 times didn't fix the problem. The printers create fine if I connect with RDP. Does anyone have any suggestions?

Thanks

0 Kudos
7 Replies
Linjo
Leadership
Leadership

try this command: "tpautoconnect.exe -v" in the vDesktop.

Best regards,

Linjo

If you find this information useful, please award points for "correct" or "helpful".

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
0 Kudos
virtualdylan
Contributor
Contributor

Hi Linjo,

Thanks for responding. That command didn't work, it gave me some interesting output though. It looks like it's timing out waiting for my client to do something. Is there some setting on the client someplace that I'm missing?

C:\Program Files\VMware\VMware Tools>tpautoconnect.exe -v

15:03:56,664 INFO <2880> Program 'TPAutoConnect - TPAutoConnect

User Agent' started, version=7,17,512,1, pid=2844, buildtype=release

15:03:56,664 DEBUG <2880> MessageFrameWork Worker Added, Name=Sy

stem, Description=The Builtin MessageFrameWork Administration Queue, Channel=000

00000

15:03:56,696 DEBUG Outgoing SharedMemory ch

annel to machine FullViewTest1.mydomain.local connected as : mydomain\user1, Authentic

ated through SSPI, package = NTLM, encrypting = true

15:03:56,696 DEBUG Connection to Node Manag

er established.

15:03:56,696 DEBUG ChannelCallbackEx: remot

eName:"guest-nm" incoming:false opened:true

15:03:56,774 DEBUG <2880> MessageFrameWork Worker Added, Name=PC

oIPVChan-CLIENT(2844), Description=PCoIPVChan, Channel=00000000

***********> VCServerAPI::Init(): Protocol = PCOIP

***********> VCTransport::ProcessLocalMessage(): server local connect message fr

om ''

15:03:58,946 DEBUG <2880> pcoip_vchan_open(): failed to open cha

nnel "RDP__CARANOC" (err=INVALID_STATE)

***********> VCPCoIPTransport::OpenStream(): pcoip_vchan_open() failed (err=INVA

LID_STATE)

TPAutoConnect User Agent, Copyright (c) 1999-2009 ThinPrint AG, 7.17.512.1

Can't connect to virtual channel (5).

Try .print Client on MyWorkstation:4000.

Try .print Client on 10.0.0.79:4000.

Timed out while waiting for client response...

Close all open message boxes.

No suitable client protocol found.

Exiting with code.......(219)

***********> VCServerAPI::Exit(): Protocol = UNKNOWN

0 Kudos
virtualdylan
Contributor
Contributor

So does that log file say anything obvious to anyone? I checked firewall settings on the VM and the client, but they were disabled.

0 Kudos
andreleibovici
Enthusiast
Enthusiast

I have seen this issue before.

The procedure below will help you to fix most VMware View agent related issue.

  • First, make sure the printer drivers is installed and the printer
    configured at the local workstation.

  • Make sure Windows Firewall is disabled.

  • Connect to VM or Template from vCenter Console

  • Uninstall VMware View Agent

  • Uninstall VMware Tools

  • Reboot

  • Delete HKEY_LOCAL_MACHINE\SOFTWARE\VMware,
    Inc.\VMware Tools

  • Delete HKEY_LOCAL_MACHINE\SOFTWARE\VMware,
    Inc.\VMware VDM

  • Delete C:\Program Files\VMware\VMware View\*.*

  • Delete C:\Program Files\VMware\VMware Tools\*.*

  • Delete C:\Documents an Settings\All
    Users\Application Data\VMware\VDM\*.*

  • Reboot VM

  • Install VMware Tools (Complete)

  • Reboot

  • Install VMware View Agent (Latest release)

  • Reboot

0 Kudos
tdubb123
Expert
Expert

I am having same issues with virtual printers not showing up on horizon view 6 desktop.

The endpoint(host ) have network printers instlled using universal hp drivers.

I did tpautoconnect -d

and then tpautoconnect -v

but keep getting no suitable client protocol found

0 Kudos
tdubb123
Expert
Expert

was able to get printer redirection to work after downgrading the client to 3.0 from 3.3

tried 3.1 and 3.2 and didnt work either so something after 3.0 broke printer redirection

agent was still at latest 6.1

0 Kudos
admin
Immortal
Immortal

Hi tdubb,

Could you provide the outputs after you run "tpautoconnect -d" and "tpautoconnect -v"?

Which kind of View Client are you using?

I'm using View Mac Client 3.2 connecting to View Agent 6.1.1, thinprint works.

-Victoria

0 Kudos