[Solved]Network Printer mapping not mapped, Flexengine-Async.log in use

[Moshikot3]

Hello,

I've created a list of printers that need to be installed on system Startup.

It looks like this:

For some reason (I don`t really know why so that is why I'm asking here)

for some users those printers are not getting mapped - log file says Scheduled printer mapping for async processing *PrinterName*.xml

and nothing really happens.

In task manager Flexengine.exe is still running even after 30 min.

Killing Flexengine.exe and Running Flexengine.exe -UemRefreshPrinters seems to work.

I also noticed that Flexengine-async.log is keep being in use even after the Workstation is up, I think it is related somehow to the printers mapping but I don't really know where is the issue (What printer can cause that? if it is printer issue)

After killing Flexengine.exe and "Freeing" Flexengine-async.log, Log file can be opened and the last row I can see is:

[DEBUG] Broadasting DEM shortcut changes.

Does anyone have an idea what can cause it? or how can I focus on the setting that can cause this issue.

[Schmad7]

I'm basically seeing the same thing in our environment as well. We're seeing the issue with Canon C325 printers. Is there any correlation there to your environment? The only other setting that we have which is different is 'undo and logoff and logon'. Are you on 2111 as well? 

Really looking for a solution here because the only thing we can really do for users is to unmap and remap the printer manually for them or run that command you mentioned.

[kvmw2130]

Hello,

FlexEngineAsync process is busy retrying some failed drive map or printer map. To know about the exact cause of the FlexEnginee Async process hung, please log off session and open the FlexEngine-async.log. It will show us the error code related to printer mapping or drive mapping during the async processing

[Schmad7]

The user has done this for a few days so there are some async logs, but nothing that shows an error code. You'll notice at the bottom of the log is where I ran "FlexEngine.exe" -UemRefreshPrinters after killing flexengine.exe manually. When looking at flexengine log I noticed the Async process was worded different than others. When it comes to this printer it states in the logs: ' [DEBUG] 'Asynchronously mapping user's preferred default printer '\\print-01\Purchasing-C3525'.' It is not scheduling it to be mapped as other async tasks are doing, such as: 'Scheduled printer mapping for async processing ('ITS-743C.xml')'

I'm not sure if that wording helps you in troubleshooting, but from my point of view from the DEM Management console, this printer has identical settings to other printers. 

2022-03-04 08:27:11.552 [INFO ] Performing async DEM actions [IFP#649445c3-1b6ff0>>]
2022-03-04 08:27:11.565 [DEBUG] User: Domain\user, Computer: DESKTOP-059, OS: x64-win10 (Version 2009, BuildNumber 19042.1526, SuiteMask 100, ProductType 1/4, Lang 0409, VMware VDM 8.4.0, App Volumes 4.5.0.77, DEM 10.4.0.1013 (2111E), ProcInfo 1/1/6/6, UTC-06:00S), PTS: 6664/4584/1C
2022-03-04 08:27:11.584 [DEBUG] Processing pending async DEM settings
2022-03-04 08:27:11.888 [INFO ] Successfully created shortcut in programs menu ('Default Printer Import.xml')
2022-03-04 08:27:11.888 [DEBUG] Processed 1 DEM shortcut (1 successful)
2022-03-04 08:27:11.889 [INFO ] Done (336 ms) [<<IFP#649445c3-1b6ff0]
2022-03-04 08:35:11.592 [INFO ] Performing async DEM actions [IFP#adb2af6a-1b0204>>]
2022-03-04 08:35:11.601 [DEBUG] User: Domain\user, Computer: DESKTOP-062, OS: x64-win10 (Version 2009, BuildNumber 19042.1526, SuiteMask 100, ProductType 1/4, Lang 0409, VMware VDM 8.4.0, App Volumes 4.5.0.77, DEM 10.4.0.1013 (2111E), ProcInfo 1/1/6/6, UTC-06:00S), PTS: 6844/7060/1C
2022-03-04 08:35:11.619 [DEBUG] Processing pending async DEM settings
2022-03-04 08:35:11.924 [INFO ] Successfully created shortcut in programs menu ('Default Printer Import.xml')
2022-03-04 08:35:11.925 [DEBUG] Processed 1 DEM shortcut (1 successful)
2022-03-04 08:35:11.925 [INFO ] Done (333 ms) [<<IFP#adb2af6a-1b0204]
2022-03-07 07:07:16.654 [INFO ] Performing async DEM actions [IFP#2df3ff23-2dd2c6e>>]
2022-03-07 07:07:16.665 [DEBUG] User: Domain\user, Computer: DESKTOP-024, OS: x64-win10 (Version 2009, BuildNumber 19042.1526, SuiteMask 100, ProductType 1/4, Lang 0409, VMware VDM 8.4.0, App Volumes 4.5.0.77, DEM 10.4.0.1013 (2111E), ProcInfo 1/1/6/6, UTC-06:00S), PTS: 7688/7336/1C
2022-03-07 07:07:16.687 [DEBUG] Processing pending async DEM settings
2022-03-07 07:07:16.961 [INFO ] Successfully created shortcut in programs menu ('Default Printer Import.xml')
2022-03-07 07:07:16.961 [DEBUG] Processed 1 DEM shortcut (1 successful)
2022-03-07 07:07:16.962 [INFO ] Done (308 ms) [<<IFP#2df3ff23-2dd2c6e]
2022-03-07 09:13:22.335 [INFO ] Performing async DEM actions [IFP#9e285cdc-25cf3f>>]
2022-03-07 09:13:22.346 [DEBUG] User: Domain\user, Computer: DESKTOP-062, OS: x64-win10 (Version 2009, BuildNumber 19042.1526, SuiteMask 100, ProductType 1/4, Lang 0409, VMware VDM 8.4.0, App Volumes 4.5.0.77, DEM 10.4.0.1013 (2111E), ProcInfo 1/1/6/6, UTC-06:00S), PTS: 3172/6948/1C
2022-03-07 09:13:22.366 [DEBUG] Processing pending async DEM settings
2022-03-07 09:13:22.700 [INFO ] Successfully created shortcut in programs menu ('Default Printer Import.xml')
2022-03-07 09:13:22.700 [DEBUG] Processed 1 DEM shortcut (1 successful)
2022-03-07 09:13:22.701 [INFO ] Done (366 ms) [<<IFP#9e285cdc-25cf3f]
2022-03-07 13:29:07.936 [INFO ] Performing async DEM actions [IFP#1cae93de-549939>>]
2022-03-07 13:29:07.939 [DEBUG] User: Domain\user, Computer: DESKTOP-057, OS: x64-win10 (Version 2009, BuildNumber 19042.1526, SuiteMask 100, ProductType 1/4, Lang 0409, VMware VDM 8.4.0, App Volumes 4.5.0.77, DEM 10.4.0.1013 (2111E), ProcInfo 1/1/6/6, UTC-06:00S), PTS: 12960/8864/1C
2022-03-07 13:29:07.982 [DEBUG] Processing pending async DEM settings
2022-03-07 13:30:04.418 [INFO ] Printer mapping logs for 'Purchasing-C3525.xml':
2022-03-07 13:30:04.418 [INFO ] At 13:30:04.361, Successfully mapped printer '\\print-01\Purchasing-C3525' (took 2 tries; waited 100 ms) ('Purchasing-C3525.xml')
2022-03-07 13:30:04.420 [DEBUG] Processed 1 DEM printer mapping (1 successful)
2022-03-07 13:30:04.422 [INFO ] Done (56496 ms) [<<IFP#1cae93de-549939]

[Moshikot3 · Accepted solution]

We managed to resolve this issue by disabling Printer Mapping at logon via group Policy

and creating a triggered task that refreshes the UEM Printer after All Appstack attached on DEM Management console.

(https://communities.vmware.com/t5/Dynamic-Environment-Manager/Appvolumes-causes-problems-with-UEM/td...)

[aslafborker]

Hi Moshikot3,

Could you please share some more details about the GPO for "disabling Printer Mapping at logon". We have one of the user for now facing the same issue.