To all,
I have an Horizon 6.2 deployment on one of our environments, and lately have seen issues due to change in ThinPrint redirection behavior. Prior to 6.2, printers that were redirected from the local client via ThinPrint were appended with :1, :2, and so forth to prevent conflicts with the printers that are installed on the virtual desktop. However, starting from version 6.2, ThinPrint will redirect the local client's printers to the virtual desktop with the exact name specified in the printer object. This has caused numerous issues on our end, mainly related to PDF printer driver (Bullzip PDF, ABS PDF printer from QuickBooks, XPS Document Writer):
1. For QuickBooks print to pdf function to work, both ABS PDF printer object and XPS Document Writer object must be installed for it to work. However, when a user connects to the virtual desktop with a client that has QuickBooks installed locally on their client desktop, ThinPrint will overwrite those printer objects with the redirected one, which will cause those printers to cease to function correctly since ThinPrint redirection does not support file-based printers. When user logs off, ThinPrint will delete those printer objects permanently, which will require a reinstall of those printer objects on the virtual desktop, even for non-persistent desktops if user data is persisted (e.g. Writable Volumes UIA+Profile from App Volumes).
2. Similarly, if the user has PDF printer (e.g. Bullzip) installed, or XPS Document Writer installed (which is installed by default on every Windows 7/8/8.1/10 desktop), on their client machine, and attempts to connect to the virtual desktop that has the same Bullzip/XPS Document Writer installed, ThinPrint redirection component will delete the Bullzip/XPS object, requiring a re-install of those printer objects. Since QuickBooks PDF printer requires XPS Document Writer to function, this also breaks the QuickBooks PDF printing functionality.
This has caused a fair amount of headache from us, and I would like to know if we can revert the ThinPrint redirection behavior back to the prior release. I really don't want to disable ThinPrint altogether as certain users want the ability to print from their home printer. Plus, the KB article on disabling ThinPrint (https://kb.vmware.com/kb/1031688, https://kb.vmware.com/kb/2012770, https://kb.vmware.com/kb/2003626) from the client side does not work at all.