Details

This article helps with basic debugging steps and steps to collect required logs after exhausting the checklist when you see issues related to VMware Integrated PrintingChecklist before reporting issue: 1. Verify your expected Display protocol is correct: Please ensure Blast or PCoIP is the selected Protocol. Additionally, ensure the protocol configured in your environment is selected. Note: RDP is not a supported display protocol for VMware Integrated Printing. 2. Verify that the necessary processes are running: ComponentServices/ ProcessWindows Agent spoolsv.exe , vmware-print-redir-service.exe,vmware-print-redir-server.exeWindows Clientvmware-remotemks.exe , vmware-print-redir-client.exeLinux Client vmware-remotemks, vmware-print-redir-client For a breakdown of the specifics of the Linux OS, please see VMware Integrated Printing - Debugging Linux Services (90133) 3. Verify that your configurations are correct:Dynamic Environment Manager Group Policy Settings: ConfigurationImpact DEM Printing Smart Policy is disabled. Documentation: Configure Horizon Smart Policies for User Environment SettingsVMware Integrated Printing (VIP) will not work. VMware Integrated Printing Policy Group Policy Settings:Each of these options will be in the imported VMware Integrated Printing ADMX template, detailed in full within Product Documentation: VMware Integrated Printing Policy Settings ConfigurationImpact“Do not redirect client printer(s)” GPO is enabled.Client printers will not be redirected. “Disable LBP” GPO is enabled. Location Based Printing (LBP) printers will not be added.“Printer Driver Selection” GPO is set to "Always Use NPD".Client printers will not be redirected if no native print driver is installed on Agent. A valid filter is defined in the “Specify a filter in redirecting client printers” GPO. The printers that meet the conditions will not be redirected. Note: The Group Policies above support both computer configuration and user configuration. User configuration has a higher priority than computer configuration. 4. Known Issues with VMware Integrated Printing Please also review Known Issues with VMware Integrated Printing (89694) Beyond the above checklist, it is likely that logs will require review along a precise timeline of the issue with as much contextual and troubleshooting data as possible. Gathering the Right Data For Review: 1. Enabling Logs at the Right Level for debugging.2. Reproduction/Simulation of the Issue.3.Log Collection and Support Ticket Submission 1)Enabling Logs at the Right Level for debugging: Enable logging: Logging is enabled on Windows/Mac/Linux platforms by default. The default log level is Info. Logging is not enabled on both mobile platforms by default. Launch Horizon iOS client App, go to “Settings” -> “Log collection”, then turn “Logging” on.Launch the Horizon Android client App, go to “Settings” -> “Log collection”, then turn “Enable log” on Changing log levels: Windows Agent and Windows Client Add or edit the value in the registry. HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VDM\PrintRedir\LogLevel, REG_SZ, "verbose" Linux Client Add the following lines in the “$HOME/.vmware/config” file. printRedirection.logLevel= "verbose" print-client.logLevel= "verbose" print-vdp.logLevel= "verbose" Mac Client Add the following lines in the “$HOME/Library/Preferences/VMware Horizon View/config” file. printRedirection.logLevel= "verbose" print-client.logLevel= "verbose" print-vdp.logLevel= "verbose" iOS and Android Client: Enhanced log levels are not available for mobile platforms at the moment. Notes: The new client log level will take effect after reconnecting the session.The New Windows Agent log level will take effect after rebooting the agent machine.Ideally, it is best to set the log levels higher and then reboot the agent before you simulate any issue. If the agent machine cannot be rebooted for some reason, the new Windows agent log level will take effect after restarting the "Print Spooler" service and restarting the "VMware Printer Redirection Service" service, and then reconnecting into the session. 3. Reproduce / Simulate the issue:Context is critical here: A video recording of the issue is always helpful with a clear timestamp.Alternatively, utilize a tool such as Steps Recorder to build a clear picture.Imagine you are bringing a colleague up to speed who cannot be physically present on site 4. Log Collection and Support Ticket Submission: Use the support.bat on each component to collect. Complete details are contained in this article: Collecting VMware Horizon View (vdm) log bundles (1017939)You can raise a Technical Support Request and we will review the logs with the context provided: How to file a Support Request in Customer Connect and via Cloud Services Portal (2006985) Additional Data For Issues with Printed Documents:If the issue is related to printed documents, for example. some characters are missing /garbled /mojibake:We recommend supplying the following additional data points. Print Data files from the agent machine.Scanned copy of the physical output.A copy of the document file printed or the unexpected behaviour is clearly explained and highlighted on the physical output. Instructions to gather Print Data Files: Open “Devices and Printers”, under “Hardware and Sound” in “Control Panel”.Open the “Printer properties” of the target printer.Click the “Advanced” tab, select the “Keep Printed Documents” checkbox, then click “OK”.After printing the document from the agent, open the “C:\Windows\System32\spool\PRINTERS” folder & copy the *.spl file.