MFD Drivers - GPO

[T_Lister]

Hi All,

 

Over the holidays we have updated to Windows 10 and changed our printer GPOs from scripts to GPPs. Any printer connects fine, however I am unable to get any MFD to apply to a user. When I go to add it manually, it requires administrator authentication. It seems to be that once the driver is installed the PC has no issue attaching the printer, and so the driver installation clearly seems to be the problem.

 

Any advise would be appreciated, thanks in advance.

[Michael]

This is related to Point and Print Restrictions which you can set via GPO in both user and computer contexts.

[IrritableTech]

It's also worth checking for a windows update which causes issues with point and print restrictions... KB3170455

[Davit2005]

This is related to Point and Print Restrictions which you can set via GPO in both user and computer contexts.

 

Also stops people sharing Parinters from local PC's which can be handy :-) as you can restrict to certain servers if you want.

[T_Lister]

Doesn't seem to work... Although adding that update has made all the printers vanish from Print Management (they're still working though)

 

It seems to specifically be the driver that belongs to the MFD that has the authentication when you click print. Sharp and Konica devices

[IrritableTech]

Doesn't seem to work... Although adding that update has made all the printers vanish from Print Management (they're still working though)

 

It seems to specifically be the driver that belongs to the MFD that has the authentication when you click print. Sharp and Konica devices

 

If you're referring to the update for KB3170455 - I was suggesting to remove it. We've had to as it was causing an issue with some printer drivers being installed by normal users under point and print restrictions.

[T_Lister]

ahhh. Well everything is back in Print Management after a reboot. And still no luck getting it to work.

[Benji2665]

Hi, see https://support.microsoft.com/en-us/kb/3170005 which details what's wrong. You can remove the update as suggested but it's going to bite you sometime. Another example of MS screwing the enterprise...