VMware Horizon Community
DPhil23
Contributor
Contributor

UEM Printer Mappings Failing With AppVolumes

Hi,

I've run into the issue where Appvolume packages that include a printer conflicts with UEM printer mappings due to Appvolumes restarting the print spooler. Previous threads indicated the solution was to disable UEM printer mappings on logon and create a triggered task to refresh printers mappings upon all appstacks being attached. The issue I'm encountering is the UEM printer mappings are being processed prior to the ADMX setting to disable printer mappings on logon, relevant logs + screenshots below:

2023-06-02 12:46:03.548 [INFO ] Scheduled printer mapping for async processing ('Secure Letterhead Printer.xml')
2023-06-02 12:46:03.555 [INFO ] Scheduled printer mapping for async processing ('Secure Printer.xml')
2023-06-02 12:46:06.073 [INFO ] Collected ADMX-based settings to apply ('Printer Mappings.xml')
2023-06-02 12:47:07.845 [DEBUG] Processed 8 DEM printer mappings (2 scheduled, 4 skipped, 2 disabled)
2023-06-02 13:09:42.843 [DEBUG] Tasks run for trigger 'All AppStacks attached':
2023-06-02 13:09:42.843 [DEBUG] At 12:48:08.111, refreshed environment settings ('"C:\Program Files\Immidio\Flex Profiles\FlexEngine.exe" -UemRefreshPrinter')

DPhil23_0-1685675886283.png

DPhil23_1-1685675970047.png

Any thoughts or assistance is greatly appreciated.

Reply
0 Kudos
1 Reply
DEMdev
VMware Employee
VMware Employee

Hi @DPhil23,

Policy settings for the DEM agent itself should be configured in Active Directory Group Policy. Doing that using DEM's ADMX-based settings will make them available too late to be picked up, as you have found.

Reply
0 Kudos