For as far as I know you can't add a driver for a printer in an appstack (not 100% sure though because the spooler is being restarted after appstacks are attached) if you attach the device locally and you would need to passthough the device on your ThinClient even if it would be possible. Also, your TC would need to support this.
What we did is we connected the Dymo printers to a Dymo printserver using this thing (yes, I'm Dutch DYMO LabelWriter Print Server - Printershop.nl ) , created a print queue for it on the print server and installed it into the VDI using a script to install the printer. Manually installing works as well. The thing is that you don't need to worry to much about drivers because it is network connected. And now you are able to share it with multiple users.
We then created an Appstack that ONLY holds the application for the Dymo Labelwriter (not the driver, please do not select it during install) and gave permissions to people that have permissions to a Dymo Labelprinter.
The thing is that the Dymo software actually looks for a Dymo Labelwriter with it's corresponding driver when starting up. If it can't find a Dymo printer it simply wont work.
yes, this works, you can add software and drivers, the only issue we have at times, is that certain stacks can mess up with the printers so in some cases I need to run a batch file to install the drivers (more like rescan, along with gpo to let non admin users perform task.
Yes, appstacks will include printer drivers as well. Quickbooks, for instance, installs its own PDF printer driver for Save to PDF functionality. We use Quickbooks appstack for a while without much issues.
We also are going to the route of the Dymo Print Server to cut down on so many of them to support. USB pass through with the AppStack works fine with a Thin Client. Not so much with the Horizon Client on a Windows machine. We gave up on those.
What does everyone have for UEM settings for Dymo? We are having issues getting settings like the Register prompt to stop prompting upon launch or Address Books to show as default upon launch in our non-persistent environment. Windows 10 1607, UEM 9.2, AppVolumes 2.11, Horizon View 7.0.2. Non-persistent.
Here are our settings in UEM for Dymo:
Predefined Settings for Dymo:
Thank you, all, for your responses. The end of the matter is complicated, but basically, we installed the drivers but uninstalled the software onto our gold-template. Then we made sure the thin client was configured to allow printer redirection. So we are using DYMO as an app stack, even though the drivers are preinstalled on the template.