Univention Bugzilla – Bug 44171
Manual installation of server side (point'n'print) printer drivers fails
Last modified: 2020-07-03 20:54:57 CEST
Created attachment 8714 [details] printer_driver_assignment_fails.png The installation of server side (point'n'print) printer drivers as Domain Administrator fails on Windows clients (Windows 7, Windows 10) I've used printmanagement.msc to assign the printer drivers. I've tried it both ways: * against the "short" server names (not fqdn, no GPOs for Point-and-Print configured) * against the server FQDNs, with GPOs for Point-and-Print configured (see Bug 43252 Comment 5) The client presents a popup saying something like "do you trust this printer", I click on "Install driver", the driver download starts, and the the same "do you trust this printer" popup is shown again. I agree a second time, the download starts again and finally a different popup is shown, saying that the driver (with correct driver name) is not installed, asking if I want to install it now.
And now the bizarre world of Windows Point'n'Print: It works when you configure a group policy to automatically deploy printer connections to the client machine.
It works only for the Windows 7 client, which had the latest Monthly Rollup March 2017 installed. The installation via the printer connections GPO didn't work for the Windows 10 Client, which has the latest Build14393.969. *But* the unprivileged user could connect to the printer, was asked if the driver should be downloaded, then a UAC popup was presented asking for Domain Administrator credentials and after that the printer worked like charm.
This issue has been filed against UCS 4.2. UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.