Loading...
Loading...
Thinprint Printers are not mapping to VMware View Client desktop virtual machines. Thinprint Printers are not redirected to VMware View Client desktop virtual machines.
Printer redirection issues can be caused by various factors including but not limited to network on the client or agent side, and firmware/hardware on the printer. Horizon Client 2006 and upwards do not have the feature - Thinprint has been deprecated Reference: Release Notes Horizon 8 (2006) removes support for some legacy components. If you are currently using any of these technologies, you can migrate them before proceeding with your Horizon 8 (2006) upgrade.Please see Ensuring a successful migration from Horizon 7 to Horizon 8 (89840) for additional advice. ThinPrint – If you are using ThinPrint, see Configuring VMware Integrated Printing.Feature comparison https://kb.vmware.com/s/article/79067On an agent machine, you'll be able to verify which component is in use by checking the following registry entry: [HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\Installer\Features_HorizonAgent] "PrintRedir"="Local" for VMware printing "Thinprint" for thinprint Note, Thinprint is still a feature in Horizon 7.13: VMware Horizon 7 version 7.13 Support Plan (81189)Note: There is a client component to Thinprint and if you update to a version above its deprecation - thinprint will not function.
To resolve this issue, perform these steps in order. If step 1 does not resolve the issue, proceed to step 2 and so on. Do not skip a step. Reinstall the VMware View agent. If this step does not solve your issue, proceed to step 2.Reinstall the VMware View Client on the client PC. If this step does not solve your issue, proceed to step 3.Stop and start the TP service located in::\Program Files\Common Files\ThinPrint\ with these commands: tpautoconnect -d (Stop) tpautoconnect -v (Start) These commands cause the redirection of the printers. If this step does not solve your issue, proceed to step 4. Note: The following steps modify the Windows registry. Before making any registry modifications, ensure that you have a current and valid backup of the registry and the virtual machine. For more information on backing up and restoring the registry, see the Microsoft Knowledge Base article 136393. The preceding link was correct as of April 4, 2020. If you find the link is broken, provide feedback and a VMware employee will update the link.Increase timeout values in the registry, then reboot the virtual machine. For example: Change HKLM\Software\ThinPrint\TPAutoconnect\TimeOutClient from 600000 to 900000 Change HKLM\Software\ThinPrint\TPAutoconnect\TimeOutClientExecution from 600000 to 900000 If this step does not solve your issue, proceed to step 5. Check the registry for names such as "PName_<number>"="<printername>,<value>" from [HKEY_CURRENT_USER\Software\AppDataLow\Software\ThinPrint\Client]. If <value> is set to 0, the printer is not selected to be mapped and you must manually change <value> to 1. For example, change "PName_4"="IBM Proprinter,0" to "PName_4"="IBM Proprinter,1". Please also be aware of the following diagnostic tool from thinprint https://help.thinprint.com/doc/diagnostic-utility-quickstart/
プリンタが View Client デスクトップ仮想マシンにマッピングされない打印机未映射到 View Client 桌面虚拟机
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.