Cannot connect to printer via UPS 7.15/server2016

[Tim Muermans1709158595]

Installed XA7.15 on server2016

Installed Server2016 Print server role + UPSserver_xa64.msi (7.15)

Set computer policy on VDA: "Universal Print Server Enable: enabled with no feallback to windows"

 

Set user policy on user:
Universal Print driver usage: "Use universal printing only"
Universal driver preference: "emf, xps, pcl5c, pcl4, ps"automatic installation of in-box printer drivers: disabled
auto-create generic universal printer: enabled
auto-create client printers: do not create client printers

When connecting to our new printserver \\printserver\printer we get:
"windows couldn't connect to the printer. check the printer name and try again. if this is a network printer, make sure that the printer is turned on, and that the printer address is correct."
(When we disable universal print driver usage in the policy, we can map the printer via the same way but it gets off course installed with native drivers)

when we go to \\printserver\ and right-mouse button click on the shared printer -> open we get:
"Operation could not be completed (Error 0x00000709). Double check the printer name and make sure that the printer is connected to the network".

Summary: When the universal print driver is enabled via Citrix policies we get the 2 errors above. When we disable the universal print driver policy we can add the printer but with it's native drivers.
The user/computer policy have both highest priority

 

Any idea someone ?

[Michael Koch]

We have the same problem with windows server 2008 R2 (printserver and XenApp 7.15 server).

 

Any solution?

[Tommy De Coninck]

On ‎21‎/‎03‎/‎2018 at 3:30 PM, Michael Koch said:

We have the same problem with windows server 2008 R2 (printserver and XenApp 7.15 server).

 

Any solution?

 

Dito. Any solution you could share?

[Marlon Bastidas]

we have the same error when we log with roaming profile but local works fine

[Tommy De Coninck]

XenApp 7.15 CU1 UPS on Windows 2008 R2:

 

when mapping a printer by logonscript va \\printserver\printername we have following errors:

Return code -2147023095

 

I believe this error code means "Invalid Printername" or "Printer not found".

 

We only have the issue in ICA sessions, not when logging on with RDP.

 

Update:

 

mapping on ipaddress works fine

mapping on hostname or fqdn does not work (not by logonscript, not by preferences)

ping resolves fine

current workaround: local hosts-file (with ip's of required printservers) on all session hosts (we use MCS)

Edited October 1, 2018 by Tommy De Coninck
update

[Barbara CERRETTI]

Hi Guys, same here. Any news?

[EDV IT1709156476]

Same Problem here