Seagull Zebra Drivers - Packaged? Folgen

0
Avatar
Chris Ottenot

We have had problems with various vendor's drivers since Microsoft's July 2016 patch that requires, prefers may be a better term, packaged drivers.  Even the latest 7.4.3 driver shows up as packaged = false when installed.  Are they any plans to change the drivers to packaged?  Thank you.

6 Kommentare

0
Avatar
Chris Ottenot
Aktionen für Kommentare Permalink

After additional testing, here is what I found.  The drivers show true when they installed locally on our W2012 R2 print server.  They also show true if they are installed locally on W7 workstations.  They show false if a queue on the W2012 R2 print server is mapped on a W7 workstations.  Normally, a packaged driver that shows true on the print server will show true on a W7 workstation when the queue is mapped.  Something is fishy.

0
Avatar
Raul Soto
Aktionen für Kommentare Permalink

Chris,

Version 7.4.3 of Seagull drivers are package aware. However, our drivers are digitally signed only by Seagull Scientific. Because of this, the standard user will still see the elevation prompt when trying to do point-and-print driver installation on the client machine.

To avoid this and have windows recognize the driver is package aware, you will have to install the certificate on the clients. We have an article on how to do this here: https://support.seagullscientific.com/hc/en-us/articles/217079018-Installing-Authenticode-signature-prior-to-Seagull-Driver-installation

Give this a try and let us know if there are problems.

0
Avatar
Chris Ottenot
Aktionen für Kommentare Permalink

It took awhile to get the cert added as they had to push it as part of a policy.  Two W7 workstations were rebooted, the Zebra queue deleted, and the driver/driver package removed.  When the printer was remapped, the "Do you trust this printer?" dialog box still appeared and the driver shows packaged false.  The W10 workstations map with no dialog box and the driver shows packaged true under both normal and admin accounts.  Please let me know if there is something else we can try to resolve the problem with the W7 workstations.

0
Avatar
Marc-Andre Galipeau
Aktionen für Kommentare Permalink

I have the same issue Chris Ottenot describe.  I try to install the certificate and still not able to add printer.  Is there a solution?

0
Avatar
Adam Throp
Aktionen für Kommentare Permalink

Apologies for resurrecting an old thread but we have just hit this problem with the latest driver for TEC printers, 2018.3

We've followed the above instructions to extract the code signing certificate from the drivers CAT file, and pushed it to all of our computers Trusted Publishers store, for both the computer certificates and user certificates side. The driver is installed on our print server and shows as packaged: True.

After rebooting all machines this works fine on Windows 8.1 and Windows 10 computers - the printer is deployed successfully using Group Policy, or can be manually connected to by a standard user, without elevation or prompting.

However on Windows 7 we still see the "Do you trust this printer" message when trying to connect manually to the shared printer, and when trying to deploy using Group Policy, the installation fails and we see errors in the event log advising that the download of the driver failed (because the trust prompt would normally appear at that stage).

The Windows 7 machines have other printers (e.g. Brother, Kyocera) deployed by group policy, and can successfully point and print to these other printers. The problem only exists when trying to deploy the Seagull driver to Windows 7 machines specifically.

Please advise if there are any solutions to this? Thanks. 

0
Avatar
Chris Ottenot
Aktionen für Kommentare Permalink

We pushed the cert to all our workstations but it did not help the "Do you trust this printer" popup box problem.  People have to request temporary admin rights on their workstations or contact our Helpdesk to get around it.

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.