Package-Aware Print Drivers?

[itangir]

So the recent print server vulnerability caused Microsoft to patch up Point and Print. Now package-unaware V3 drivers do not play nice with Group Policy.

A lot of the network printers on our print server already have packaged drivers and aren't affected. All of our Canon drivers do not, however, and this means we need to go to each user and put in administrator credentials in order for them to make a (new) printer connection to our Canon imageRunners...

Even the latest UFRII drivers for our models appear to still be unpackaged...

Does Canon offer package-aware V3 drivers? If not, do they plan to offer them? We'd like to know what Canon's doing about this so we can take the appropriate steps.

[jrhoffman75]

This is an end-user supported forum. You are best served by calling 1-800-OK-CANON.

[OCDGeek]

Same issue here, We have lexmark's and Canon's we pushed the win updates for July on the 21st, Came in Monday morning to find all the canon's were gone. Manualy mapped them on about 2 dozen just to relize we had the GP on replace, it deleted all of them that we bandaid'd. About to rollback the windows updates that were fixing the 20 year old bug. Couldn't beleive lexmark drivers worked over Canon's. SMH!

Updates to uninstall:

Windows 10 - 1511

KB3172985

Windows 10

KB3163912

Windows 8.1 and older

KB3170455

[Ink]

This is a huge issue for many. Canon need to urgently release packaged drivers for Windows servers. They appear to be the only vendor that does not.

[LJS576]

I'm a technician working on Canon products. Canon is aware of the problem and is working on a fix. Unfortunately, it may be end of September before the fix is ready.

As usual, MS tried to fix something and broke something else in the process.

[tolvajp]

In other words Microsoft told, please make packaged drivers since vista, and Canon did not made this.,

Anyways. If you set the right GPO at Computer settings/administrative templates/printers/point and print restrictions the issue seems solved.

[tolvajp]

It seems, if you set this GPO right, the problem will be solved. )Disabled is now not a right setting) Computer settings/administrative templates/printers/point and print restrictions

[Morotalizer]

If i understand U correctly, only setting GPO "Computer settings/administrative templates/printers/point and print restrictions" to disabled will not solve the problem, you will have to specify the settings in the policy to make it work?

[grei_70]

By the power of a tweak, thou shall pass the dreaded MS16-087 and letters will be put on paper once again.
You need to register at your local servant that does all your writing. See if he is current in control of his enviroment - there might be an attribute in need of a change. The attribute shall be in form of 16 and Douglas Adams was almost right, he miss it by an inch and odd the answer should be.

Enough rubbish:
If you have trouble deploying printers after applying critical updates according to MS16-087 (KB3170455) try this tweak: Edit the register on your print server. If you change the value of the key PrinterDriverAttributes under HKLM\System\CurrentControlSet\Control\Print\Enviroments\Windowsx64\Drivers\...\Driver name\ and restart the print server, you are able to make Windows treat the driver as packaged, and it will install unattended with gpo. The hex number has to be odd, i.e. 41
Restart server .

According to MS the 1 flag for PrinterDriverAttributes stands for PRINTER_DRIVER_PACKAGE_AWARE. This will treat the driver as package aware, which means a CAB package will be created, including the inf and the catalog. The package will be installed through setupapi.dll when installing the driver, validating that the catalog is trusted, and that hashes for all files are included in the catalog.

[frank_net]

Disable Point and Print restrictions work only is the driver respect this criteria :
Package aware
Digitally signed
Catalogue print drivers

It’s functional for my with HP and Dell printer

This is not the case for some driver Canon (ImageRunner in my case) "NON PACKAGED"

printmanagement.msc:

I contact Canon today there are already aware of the problem and they will probably reissue driver in September