We have about 100 printers spread across 14 branch offices. I created printer mappings for each printer at each branch per a condition of View Client Machine Name, then let the user set their default:
However the printer does not map at login. When I log in as a UEM user with logs set to debug, I get:
2018-12-06 16:38:48.698 [INFO ] Skipping printer mapping due to conditions ('VTPR5222.xml')
2018-12-06 16:38:48.698 [DEBUG] Conditions: Check for Horizon client property 'MACHINE_NAME' = false (property not available)
If I do a flexengine.exe -uemrefresh, the printers map:
async log
2018-12-06 16:57:00.532 [INFO ] Successfully mapped printer '\\oncu-print\VTPR5225' ('VTPR5225.xml')
2018-12-06 16:57:03.406 [INFO ] Successfully mapped printer '\\oncu-print\VTPR5226' ('VTPR5226.xml')
2018-12-06 16:57:06.202 [INFO ] Successfully mapped printer '\\oncu-print\VTPR5227' ('VTPR5227.xml')
2018-12-06 16:57:08.686 [INFO ] Successfully mapped printer '\\oncu-print\VTPR5230' ('VTPR5230.xml')
2018-12-06 16:57:11.794 [INFO ] Successfully mapped printer '\\oncu-print\VTPR5232' ('VTPR5232.xml')
regular log:
2018-12-06 16:56:53.283 [DEBUG] Conditions: Check for Horizon client property 'MACHINE_NAME' = true ('WT052-13' starts with 'WT052')
2018-12-06 16:56:56.642 [INFO ] Successfully mapped printer '\\oncu-print\VTPR5222' ('VTPR5222.xml')
2018-12-06 16:56:56.657 [DEBUG] Conditions: Check for Horizon client property 'MACHINE_NAME' = true ('WT052-13' starts with 'WT052')
2018-12-06 16:56:56.657 [INFO ] Scheduled printer mapping for async processing ('VTPR5225.xml')
2018-12-06 16:56:56.704 [DEBUG] Conditions: Check for Horizon client property 'MACHINE_NAME' = true ('WT052-13' starts with 'WT052')
2018-12-06 16:56:56.704 [INFO ] Scheduled printer mapping for async processing ('VTPR5226.xml')
2018-12-06 16:56:56.720 [DEBUG] Conditions: Check for Horizon client property 'MACHINE_NAME' = true ('WT052-13' starts with 'WT052')
2018-12-06 16:56:56.720 [INFO ] Scheduled printer mapping for async processing ('VTPR5227.xml')
2018-12-06 16:56:56.720 [DEBUG] Conditions: Check for Horizon client property 'MACHINE_NAME' = true ('WT052-13' starts with 'WT052')
2018-12-06 16:56:56.720 [INFO ] Scheduled printer mapping for async processing ('VTPR5230.xml')
2018-12-06 16:56:56.736 [DEBUG] Conditions: Check for Horizon client property 'MACHINE_NAME' = true ('WT052-13' starts with 'WT052')
2018-12-06 16:56:56.736 [INFO ] Scheduled printer mapping for async processing ('VTPR5232.xml')
Since the View client info is Volatile, can you not use it at log in? Or can you delay the printer mapping up the the viewclient info has been registered?
We are running Horizon 6.0.1
Ah, that explains it. In that version, the ViewClient properties are not available yet when UEM runs during logon; a change was made in Horizon 6.2 to provide them earlier.
You can configure UEM to skip processing printer mappings at logon, and perform a -UEMRefreshPrinters through the startup folder. The printers will appear slightly later, but that's the best we can do on 6.0.1 🙂
Install the VMware UEM FlexEngine Advanced Settings ADMX template, and add the Disable UEM action types policy setting to your UEM GPO, configured as follows:
In addition, configure a shortcut through UEM, and specify the startup folder as its destination. Do not check the Run asynchronously check box in that shortcut, as that might result in it being created after Explorer has already started (which means that it would not get to run.)
As a test you can of course just start with that shortcut. The only reason to skip processing printers at logon is to save a bit of time and not pollute the log file.
Hi matthewgONCU,
Can you try using the Endpoint Name condition instead of Horizon Client Property?
Which version of Horizon are you using, and which version of UEM? How are you running UEM at logon?
Same issue.
We are running Horizon 6.0.1 but are planning a complete refresh to Horizon 7.6 (new install), but would like to get all our users moved over to UEM before the refresh. Everything else seems to be working except this printer issue with our test users.
We are running Horizon 6.0.1
Ah, that explains it. In that version, the ViewClient properties are not available yet when UEM runs during logon; a change was made in Horizon 6.2 to provide them earlier.
You can configure UEM to skip processing printer mappings at logon, and perform a -UEMRefreshPrinters through the startup folder. The printers will appear slightly later, but that's the best we can do on 6.0.1 🙂
Install the VMware UEM FlexEngine Advanced Settings ADMX template, and add the Disable UEM action types policy setting to your UEM GPO, configured as follows:
In addition, configure a shortcut through UEM, and specify the startup folder as its destination. Do not check the Run asynchronously check box in that shortcut, as that might result in it being created after Explorer has already started (which means that it would not get to run.)
As a test you can of course just start with that shortcut. The only reason to skip processing printers at logon is to save a bit of time and not pollute the log file.
I tried to use this GPO and created a shortcut that runs in the startupfolder, butt still my default printer is the "microsoft print to PDF".
in UEM i have this setting for mapping our default printer:
Hi lansti,
Anything in the log files?
Log file tells me that that the Printer was mapped during UEM Refresh as expected:
2018-12-10 11:41:43.084 [INFO ] Performing UEM refresh [IFP#02bf8939-1b26ae>>]
2018-12-10 11:41:43.104 [DEBUG] Refreshing UEM printer mappings
2018-12-10 11:41:43.279 [DEBUG] Conditions: Check for OS 6.1W = true
2018-12-10 11:41:47.016 [INFO ] Successfully mapped printer '\\server\FMPPC' ('FollowMe Uniflow.xml')
2018-12-10 11:41:47.016 [INFO ] Set printer as default
But it is not set as default printer...
Are you by any chance using ThinPrint or a third-party printing solution that might be "hijacking" the default printer?
Nope, and its strange that print to PDF should be set as default printer
Its seems that something is written to registry, even if i use GPO to force a default printer, "Print to PDF" is default.
Hi lansti,
Not sure what might be causing this. I just came across the following, though, in the Printers & scanners control panel on Windows 10:
But why on earth would you disable that setting.. You do know that Microsoft always knows best, like with your FTA and new version of Windows 10 and stuff /sarcasm
Yes, do turn it off.. It is a registry key or policy that you can set.. User Settings --> Administrative Templates --> Control Panel --> Printers --> Turn off Windows default printer management.
Thanks for the info. We are building out a new environment so once that's done, I'll continue to test. Thanks again.
Sounds good, matthewgONCU. Good luck with the new environment, and keep us posted!
Hi UEMdev, i should told you that this is regarind windows 7 :smileyplain: Sorry.
On my windows 10 environment it seems to work just fine.
Hi lansti,
If you perform a UEM printer refresh, is the correct printer marked as the default? Or if you change it manually, does it "stick"?
Thanks for your time UEMdev, correct, even after a manually printerfresh from the startup folder it get sticked at:
UemRefreshprint:
Hi lansti,
Can you create a new post for this, as it is unrelated to the Horizon Client Property from this topic?