VMware Horizon Community
ARuvVD11
Enthusiast
Enthusiast

Can't get UEM to map default printer.

Trying to get uem to install and set a network printer as default for a specific user group, but it keeps failing with nothing more in the logs than "[ERROR] Error 1726 trying to map printer"

Anyone have any insights, or perhaps more detailed info then what's in the admin guide?

Reply
0 Kudos
18 Replies
Raymond_W
VMware Employee
VMware Employee

Hi,

Can you check if Windows is able to download and/or install the correct printer driver for this printer. Or is the printer driver installed in the Windows image ?

Raymond

Kind regards, Raymond Twitter: @raymond_himself
Reply
0 Kudos
ARuvVD11
Enthusiast
Enthusiast

Sorry, I failed to mention that doing a manual printer refresh from the UEM shortcut WILL map the printer after log on.

Reply
0 Kudos
Raymond_W
VMware Employee
VMware Employee

Can you please post a UEM logfile in debug mode with at least one import and export moment.(done though the UEM policy or by placing a flexdebug.txt in the same location as the existing logfile)

Raymond

Kind regards, Raymond Twitter: @raymond_himself
Reply
0 Kudos
ARuvVD11
Enthusiast
Enthusiast

end of log has a clean bootup that failed to set the printer, and a UEM user environment refresh that worked.

Reply
0 Kudos
Raymond_W
VMware Employee
VMware Employee

You are so right, I apologise... my log file viewer did not refresh :smileysilly:

Can you please post the async logfile ? This logfile can be found in the same place as the normal logfile.

Thanks !

Kind regards, Raymond Twitter: @raymond_himself
Reply
0 Kudos
ARuvVD11
Enthusiast
Enthusiast

Since it's so short...

2015-09-29 11:54:59.658 [INFO ] Performing async UEM actions [IFP#18eea98c-14683b>>]

2015-09-29 11:54:59.658 [DEBUG] Processing pending async UEM settings

2015-09-29 11:55:00.033 [INFO ] Skipping creating UEM shortcut on desktop as shortcut already exists ('UEM Self-Support.xml')

2015-09-29 11:55:00.033 [INFO ] Successfully created UEM shortcut in programs menu ('UEM Self-Support.xml')

2015-09-29 11:55:00.049 [INFO ] Skipping creating UEM shortcut on desktop as shortcut already exists ('UEM User Environment Refresh.xml')

2015-09-29 11:55:00.049 [INFO ] Successfully created UEM shortcut in programs menu ('UEM User Environment Refresh.xml')

2015-09-29 11:55:00.049 [DEBUG] Broadcasting UEM shortcut changes

2015-09-29 11:55:13.096 [ERROR] Error 1726 trying to map printer '\\ietprint1\itx-pear' ('ITX Printer.xml')

2015-09-29 11:55:13.096 [DEBUG] Processed 1 UEM printer mapping (1 error)

2015-09-29 11:55:13.096 [DEBUG] Processed 2 UEM shortcuts (2 skipped)

2015-09-29 11:55:13.096 [INFO ] Completed async UEM actions (13436 ms) [<<IFP#18eea98c-14683b]

Reply
0 Kudos
Raymond_W
VMware Employee
VMware Employee

Hi,

My guess is, that this is printer driver related.

Can you please give me some more info about your environment ?

  • Are you using VDI ? If yes, Persistent or Non-persistent
  • Is the printer driver pre-installed on the machine or is it downloaded from the printserver ?
  • Are you using App Volumes ?

Thanks in advance !

Raymond

Kind regards, Raymond Twitter: @raymond_himself
Reply
0 Kudos
ARuvVD11
Enthusiast
Enthusiast

Yes, non-persistent VDI, windows 7. hp printer, with universal drivers installed (but that doesn't seem to matter.)

Printer driver is installing when mapped. Maps correctly when asynchronous settings is NOT applied, but dramatically increases boot time.

I am using app-volumes.

Reply
0 Kudos
Raymond_W
VMware Employee
VMware Employee

Thanks !

Did you already tried to detach all app stacks and map the printer asynchronously ?

If no, can you please try this ?

Kind regards, Raymond Twitter: @raymond_himself
Reply
0 Kudos
ARuvVD11
Enthusiast
Enthusiast

I signed in with a test account that had no appvols assigned to it, the printer loaded correctly asynchronously

2015-09-29 14:24:26.787 [INFO ] Performing async UEM actions [IFP#18b7585f-6606e>>]

2015-09-29 14:24:26.787 [DEBUG] Processing pending async UEM settings

2015-09-29 14:24:26.897 [INFO ] Successfully created UEM shortcut on desktop ('UEM Self-Support.xml')

2015-09-29 14:24:26.897 [INFO ] Successfully created UEM shortcut in programs menu ('UEM Self-Support.xml')

2015-09-29 14:24:26.912 [INFO ] Successfully created UEM shortcut on desktop ('UEM User Environment Refresh.xml')

2015-09-29 14:24:26.912 [INFO ] Successfully created UEM shortcut in programs menu ('UEM User Environment Refresh.xml')

2015-09-29 14:24:26.912 [DEBUG] Broadcasting UEM shortcut changes

2015-09-29 14:25:12.922 [INFO ] Successfully mapped printer '\\ietprint1\itx-pear' ('ITX Printer.xml')

2015-09-29 14:25:12.922 [INFO ] Set printer as default

2015-09-29 14:25:12.922 [DEBUG] Processed 1 UEM printer mapping (1 successful)

2015-09-29 14:25:12.922 [DEBUG] Processed 2 UEM shortcuts (2 successful)

2015-09-29 14:25:12.923 [INFO ] Completed async UEM actions (46145 ms) [<<IFP#18b7585f-6606e]

Reply
0 Kudos
NiklasAndersson
Enthusiast
Enthusiast

Did you ever get it working with the Writable/AppVols attached? I have the exact same problem and get "Error 6 trying to map printer" until I disable the writable volume for the user.

Reply
0 Kudos
ijdemes
Expert
Expert

Have you tried this? --> https://kb.vmware.com/s/article/2137401


\\ Ivan
---
Twitter: @ivandemes
Blog: https://www.ivandemes.com
Reply
0 Kudos
DEMdev
VMware Employee
VMware Employee

Hi NiklasAndersson01,

As this is a rather old thread (as is that KB article Ivan pointed you at Smiley Wink), let's start with some basic info:

  • What versions of DEM/UEM and App Volumes are you using?
  • Do printers map correctly if you perform a FlexEngine.exe -UEMRefreshPrinters within the session?
Reply
0 Kudos
NiklasAndersson
Enthusiast
Enthusiast

Environment is Horizon 7.10 with AppVolumes 4.01, using writable volumes only for OneDrive and Git repos.

  • Running DEM 9.9 (about to go to 9.11).
  • Runninng FlexEngine.exe -UEMRefreshPrinters does not map the new printer.

Only way to get the printer to map right now is by disabling the users Writable Volume. Drivers are installed in image, but I've also tried other drivers not in the image and then the driver is downloaded and installed but the printer is not mapped.

Reply
0 Kudos
DEMdev
VMware Employee
VMware Employee

Hi NiklasAndersson01,

Thank you for the additional information. I assume that "manually" mapping the printer in the session (i.e. without DEM) does not work either?

Reply
0 Kudos
NiklasAndersson
Enthusiast
Enthusiast

You are right, manually trying to map the printer gives the same error when having a Writable Volume attached.

Reply
0 Kudos
DEMdev
VMware Employee
VMware Employee

Hi NiklasAndersson01,

You are right, manually trying to map the printer gives the same error when having a Writable Volume attached.

Thank you for confirming that.

I don't know much about App Volumes (as my user name indicates Smiley Happy), so I'd suggest to pick this up in the App Volumes forum instead.

Reply
0 Kudos