We ran into this issue last year where some print jobs when printed would shift all characters one position forward like a Caesar Cipher. For instance A's would become B's, 1's would become 2's, G's would become H's etc. The fix for this was posted in KB2099984 where it instructed to set the HKLM\SOFTWARE\Wow6432Node\ThinPrint\TPView\EnableLegacyFonts DWORD to 1. We have had that in place for quite some time with no issues, however just recently it has started to happen again, even with the regkey still implemented on the host machine.

This appears to happen inside of IE when printing the PDF, and when opening directly with Reader/Acrobat. I opened the PDF in Chrome and it printed the characters properly. This also only appears to be certain PDF's, the one I am troubleshooting is a PDF form that is being exported out of a web application. The workaround I have right now is to print the PDF as an image since that bypasses any font dependencies or conversions or open the PDF in Chrome and print that way.

Horizon Client 4.7.0

AppVol 2.13.3.12

UEM 9.3.0.804

VMware Tools 10.1.10.6082533

Horizon Agent 7.3.2

Is anyone else seeing this issue show up again? I am not seeing anything in the thinprint.log indicating any issue as the print job is technically successful, just characters are skewed.

UPDATE:

Worked with support and they are aware of the issue and the Engineering team has assigned a Problem Report number to the issue and will be fixed in a later Client update which has no ETA as of yet. Another workaround was to downgrade to the 4.6.1 client.

Thank you for your response.

The issue was reported by only few users, so currently we don't have an KB article or public forum regarding this.

2059196 is the internal Problem Report number on which our Engineering team worked internally with the concerned team to get the issue resolved. We have also linked your Support Request # to the internal Problem Report number# 2059196.

Our Engineering team has acknowledged and taken ownership of the problem and have made that issue to be resolved in a future release/version of VMware Horizon Client. Currently there is no ETA as to the release date, or which product version the fix will be in. We'll keep you updated once the fix is available.