lansti
Hot Shot
Hot Shot

UEM Log - multiple mapping of drives and printers

Hi, i have some issues with mapping printers, so i had to look into the UEM logs.

i can see that UEM map drives and printers several times during a logon...

UEM 9.2.0.701

Appvolume 2.12.1.103

Horizon View 4.5.0

Windows 10 LTSB - Linked Clone(Floating)

Printer:

2017-08-27 07:05:41.253 [ERROR] Error 1726 trying to map printer '\\printserver.domain.com\printer1' ('printer1.xml')

2017-08-27 07:05:41.253 [ERROR] Server unavailable for printer '\\printserver.domain.com\printer2' ('printer2.xml')

2017-08-27 07:05:41.253 [ERROR] Server unavailable for printer '\\printserver.domain.com\FollowMePrint' ('FollowMePrint.xml')

2017-08-27 07:05:41.268 [ERROR] Server unavailable for printer '\\printserver.domain.com\printer3' ('printer3.xml')

2017-08-27 07:05:41.268 [ERROR] Server unavailable for printer '\\printserver.domain.com\printer4' ('printer4.xml')

...

2017-08-27 07:05:54.081 [ERROR] Error 87 trying to map printer '\\printserver.domain.com\printer1' ('printer1.xml')

2017-08-27 07:05:57.268 [ERROR] Error 87 trying to map printer '\\printserver.domain.com\printer2' ('printer2.xml')

2017-08-27 07:05:59.784 [ERROR] Error 87 trying to map printer '\\printserver.domain.com\FollowMePrint' ('FollowMePrint.xml')

2017-08-27 07:06:02.292 [ERROR] Error 87 trying to map printer '\\printserver.domain.com\printer3' ('printer3.xml')

2017-08-27 07:06:05.104 [ERROR] Error 87 trying to map printer '\\printserver.domain.com\printer4' ('printer4.xml')

Drives:

2017-08-27 07:05:33.128 [DEBUG] Processing pending async UEM settings

2017-08-27 07:05:33.378 [DEBUG] Set friendly name for drive 'L:' to 'AgressoData' ('AgressoData.xml')

2017-08-27 07:05:33.378 [INFO ] Successfully mapped drive 'L:' to '\\server1\Agr_Data$' ('AgressoData.xml')

2017-08-27 07:05:33.440 [DEBUG] Set friendly name for drive 'O:' to '\\server2\hklist$' ('Compass.xml')

2017-08-27 07:05:33.440 [INFO ] Successfully mapped drive 'O:' to '\\server2.domain.com\hklist$' ('Compass.xml')

2017-08-27 07:05:41.268 [INFO ] Completed async UEM actions (8137 ms) [<<IFP#83fa3369-aff895]

...

2017-08-27 07:05:49.393 [INFO ] Performing async UEM actions [IFP#9cca6913-aff895>>]

2017-08-27 07:05:49.393 [DEBUG] Processing pending async UEM settings

2017-08-27 07:05:49.518 [DEBUG] Successfully unmapped drive 'L:' ('AgressoData.xml')

2017-08-27 07:05:49.534 [DEBUG] Set friendly name for drive 'L:' to 'AgressoData' ('AgressoData.xml')

2017-08-27 07:05:49.534 [INFO ] Successfully mapped drive 'L:' to '\\server1\Agr_Data$' ('AgressoData.xml')

2017-08-27 07:05:49.565 [DEBUG] Successfully unmapped drive 'O:' ('Compass.xml')

2017-08-27 07:05:49.597 [DEBUG] Set friendly name for drive 'O:' to '\\server2\hklist$' ('Compass.xml')

Why does it do the same operation several times? This will delay logintime with several seconds.

And i also as you can see with my printer, have issues with printer mappings, this user had to log off an on again, and then the printer was mapped correct.

Eventviewer do not tell me anything. Is this a common UEM issue?

Best regards
Lansti
Reply
0 Kudos
lansti
Hot Shot
Hot Shot

Regarding my printer issue, i tried to install all printers to the image and then remove the devices, and now it seems to work just fine since the drivers are located in the golden image and deployed to my clients.

But i still wounder why UEM is mapping my drives and printers twice during logon.

Best regards
Lansti
Reply
0 Kudos
Pim_van_de_Vis
VMware Employee
VMware Employee

Without the complete logfile I cannot see what triggers the second mapping of drives and printers. Could it be that a UEM refresh is performed? This can be triggered by AppVolumes.

Reply
0 Kudos
lansti
Hot Shot
Hot Shot

Hi, adding my logs here. Thanks for reply.

Best regards
Lansti
Reply
0 Kudos
Pim_van_de_Vis
VMware Employee
VMware Employee

These are just the Async logs, they don't show the complete picture. I also need the regular FlexEngine log.

I can see that Drives, Printers and shortcuts are re-created. This is probably a UEMRefresh command, triggered by AppVolumes.

Take a look at the following KB.

https://kb.vmware.com/kb/2146474
Reply
0 Kudos