Microsoft update KB3159398 breaks gpo printer mapping

[dotdeas]

[habik]

Re: Microsoft update KB3159398 breaks gpo printer mapping

Thanks

Byting on bits.

[ApeosMan]

Re: Microsoft update KB3159398 breaks gpo printer mapping

KB3170455 is another bastard of an update...

[tonnerboy]

Re: Microsoft update KB3159398 breaks gpo printer mapping

KB3170455 is another bastard of an update...

Did someone manage this update?
One of my costumers are calling me with this issue. He tells me that it is related to the Digital Signature of the driver

Can same one help me with it? He is using a Ricoh MP6000 PCL6 driver

[rthonpm]

Re: Microsoft update KB3159398 breaks gpo printer mapping

Did someone manage this update?
One of my costumers are calling me with this issue. He tells me that it is related to the Digital Signature of the driver

Can same one help me with it? He is using a Ricoh MP6000 PCL6 driver

Here's Microsoft's mitigation for this issue: https://support.microsoft.com/en-gb/kb/2307161 If it's a small customer you could just have them turn off Point and Print restrictions entirely.

[amos.kaplan]

Re: Microsoft update KB3159398 breaks gpo printer mapping

I had this one stop smb to folder...

Security Update Capicom KB931906 2.1.0.2

[tonnerboy]

Re: Microsoft update KB3159398 breaks gpo printer mapping

Here's Microsoft's mitigation for this issue: https://support.microsoft.com/en-gb/kb/2307161 If it's a small customer you could just have them turn off Point and Print restrictions entirely.

Hi.
This is not a smaller customer and change the group policy restrictions it's out of the question.
This is related to the digital signature. How can I put a digital signature in printer driver?

[rthonpm]

Re: Microsoft update KB3159398 breaks gpo printer mapping

Unless you have a digital signature recognised by Microsoft, you can't. Just have the customer change the GPO to allow point and print printing from their specific print servers if possible, or at least let them know that it's a Windows issue. Have you checked for a newer print driver as well?

[emujo]

Re: Microsoft update KB3159398 breaks gpo printer mapping

KM drivers are digitally signed, this update add something called "driver package aware". I just went through this with another customer. They were able to go onto the print server and manually change the setting on the driver to "package aware".

From Google...

This tweak will get your Canon, Sharp or KonicaMinolta printers up and running again by making the drivers Package Aware.



Edit the register on your print server(s). If you change the
value of the key PrinterDriverAttributes under
HKLM\System\CurrentControlSet\Control\Print\Enviro nments\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.
To keep the original settings for the printer driver and only
make it Package aware you should add 1 to the original value of
PrinterDriverAttributes. In my print environment the original attribute
had the value 4, so I changed it to 5 and that made it
Package aware. Different versions of the driver (and different vendors)
might need other values.


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.



BTW: This is not a Microsoft problem, but a printer vendor problem!
Two lines of code in the *.inf file will make the driver Package aware
and fix the problem properly! Solution for vendors posted by Microsoft
here: https://msdn.microsoft.com/en-us/library/windows/hardware/ff559698(v=vs.85).aspx

[tonnerboy]

Re: Microsoft update KB3159398 breaks gpo printer mapping

KM drivers are digitally signed, this update add something called "driver package aware". I just went through this with another customer. They were able to go onto the print server and manually change the setting on the driver to "package aware".

Ernujo, Thank you so much for your info. Learn a lot.
I saw that the Ricoh MP6000 PCL6 Driver for Universal Print is Package-Aware since Version 3.8.0.0.
I do not know if it will solve the problem of this patch (KB-3170455) because this version has been released a long time ago... I will wait for the reply from costumer.
Once again thank you so much.

[tonnerboy]

Re: Microsoft update KB3159398 breaks gpo printer mapping

Update:

Even though the PCL6 Driver for Universal Print for MP6000 is Package-Aware since Version 3.8.0.0Release Date: 18/05/2016.

[slimslob]

Re: Microsoft update KB3159398 breaks gpo printer mapping

Update:

Even though the PCL6 Driver for Universal Print for MP6000 is Package-Aware since Version 3.8.0.0Release Date: 18/05/2016.

I my opinion, Universal Print drivers should only be used when you need to pool different models. Pooling requires that all printers in the pool use the same driver. I have a school district that recently updated their servers from Server 2008R2 to Server 2016. They have a MP 9001 and a MP C6501. Their IT service decided to use the Universal Print driver. Worked OK on their 64 bit computers once I showed them where to set their Used Code and Mailbox tray. The problem was that they have a number of 32 bit computers that could not print. When checking the one in the office, I found that there was no place the enter the user code because it was trying to use the Microsoft Point and Print driver. The IT service then tried to load the 32 bit driver as an additional driver and the server would not accept the 32 bit Universal driver as a compatible additional driver for the 64 bit. I gave them the machine specific drivers.

[tonnerboy]

Re: Microsoft update KB3159398 breaks gpo printer mapping

I my opinion, Universal Print drivers should only be used when you need to pool different models. Pooling requires that all printers in the pool use the same driver.

I agree with you 100%.
The attempt to use the PCL6 Driver for Universal Print was because it's more recente... and Package-Aware since Version 3.8.0.0. Even though it did not work...