- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mapping a printer with UEM only works when not capturing printer settings
We're struggling to get a consistent printing experience in our VDI environment. I was originally using a group policy preference to install and set our default printer, which works for our physical environment, but not consistently in our virtual environment for whatever reason. So I decided to let UEM handle it.
Horizon 6
AppVolumes 2.11
UEM 9.0 (also tested in 9.3)
Zero Client
When I first added the printer to be mapped and tested it, I found in my async log file:
2018-04-02 13:01:17.037 [ERROR] Error 3012 trying to map printer '\\printserver\printername' (tried 21 times; waited 21000 ms) ('Flex Print.xml')
I had heard that AppVolumes can interfere with printers so I tested an account with no appvolumes and got the same result. Then I decided to try deleting the Printers.zip file under my UEM profile, and then the mapping worked! I logged off, logged back on, and again a failure with the same error. Deleted Printers.zip and it works again. If I disable capturing the Windows common setting for printers, the mapping works every time. It also works if I uncheck "run asynchronously", but it adds 30+ seconds to log on time, which is not acceptable.
Any ideas why this might be? I'd like to capture printer settings and I'm not sure what I might be losing by disabling those settings.