Printers not applying..... GPO

[newpersn]

Me again... Having a nightmare with Windows 10 so far this week.

 

Printer arnt installing and get this error in the event viewer.

 

 

What am i missing.... I'm going to hide and cry now

[DalekSec]

I thought that with the new 1607 printers could not be pushed out easily as they now require UAC to install the drivers?

 

We had to do our suite manually.

[newpersn]

I hope not.... I'm just hope im missing a setting somewhere else.

[6Foot2]

Me again... Having a nightmare with Windows 10 so far this week...

 

After a little Googling I found this:

 

Link: windows server 2008 - Not all printers are deployed on the client using Group Policy - Server Fault

 

Ok, after some hours spending and searching I have found the solution. All of my printers are now deployed on the Win7 and Win10 computers.

 

The fix was to update the ADM files on my Windows server because the setting Point and print restrictions wasn't available under Computer configuration.

 

Then set this also disabled, did a gpupdate /force and voila, all printers deployed!

 

I can't say if this is accurate as we haven't deployed Windows 10 yet.

 

HTH.

 

DaveP.

 

[JamboD]

We’ve come up against this issue with Win 10 1607, the Event Viewer errors said that the printers couldn’t map because there were no drivers installed.

 

It turns out that MS have patched an attack that has existed since Win 95 but was only reported/discovered in July. Their solution has been to release an update which has broken the group policy setting that allows drivers to be installed without elevation.

 

I tried changing the settings as suggested in Microsoft’s guidance but can't get it to work, we had to install the printer manually by clicking through the UAC prompt. The printers map with no issues since that process installed the drivers .

 

You could uninstall the update from Win 7 & 8 but with Win 10 it's all cumulative now

Edited September 6, 2016 by JamboD

[newpersn]

I noticed this has seemed to effect Windows 7 as well. I'm guessing I may have missed a setting somewhere.

 

I got a list of printers in the gpp and got item level targeting set on some printers. (Library and staff room printer installed on all computers. And then any computers in (let's say DT1 or DT2 OU) install all the DT printers.

[newpersn]

Just to add:

 

I just added the printer script (and disabled the printers part of the GPP (for now, Would like it back at some point)

 

I noticed its asking for Admin rights to install.. (I'm guessing that why its not installing the printers during login though GPP)

 

Edited September 7, 2016 by newpersn

[JamboD]

As I said in my last post, this behaviour seems to be by design. As long as Microsoft Update KB3163912 is installed on a client you will get the UAC/Admin prompt.

 

The only we found to get it working was to manually install the drivers on every computer which meant clicking the Install Driver button on that prompt. After we did that the printers map for non-admin users.

Edited September 7, 2016 by JamboD

[mowgli82]

Has anyone come up with a solution for this for Windows 10 1607?

[newpersn]

Has anyone come up with a solution for this for Windows 10 1607?

 

I log in as me and install the printers when it prompts.. Seems long winded but not any problem.. (still using the vbs script in GP)

[birchanger]

Has anyone come up with a solution for this for Windows 10 1607?

 

When we upgraded from Win 7 to Win 10 1607 we moved printer deployment to user GPPs and item-level targetting based on the name of the computer. This works for us as the room a machine is in forms part of its name. This seems, so far, more reliable then the old deploy-to-device way. Driver install times haven't been a problem as almost all of our printers are using the same drivers (generic PCL5).

[Sheridan]

We get an error when deploying printers through GPP (machine) and I can't get around it, has anyone scripted a printer install for W10?

 

Group Policy was unable to add per computer connection \\server\printer. Error code 0x57. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server

 

This is on 1607 with recent updates. What an utter POS W10 is turning out to be.

Edited September 29, 2016 by Sheridan

[mowgli82]

This is on 1607 with recent updates. What an utter POS W10 is turning out to be.

 

I can't believe how hard i'm having to work to get basic things to work........I mean printer deployment....seriously!

[Sheridan]

I can't believe how hard i'm having to work to get basic things to work........I mean printer deployment....seriously!

 

Same here, W10 has been such a waste of time. Its not a case of configuring it to suit your environment, more like a desperate fight to get the crappy thing to work for some of the most basic tasks. And then going back a couple of days later to do it again!

[mikeglover]

Had this similar Error 0x80070bcb but on Windows 7 clients and 2012R2 print server. In the end it is because the printer driver being used on the server was not packaged and a recent Windows update has broken stuff. This can be found under Print Management > Drivers and will be set to false for packaged? In our case Canon driver are not updated to be packaged drivers.

On the print server I had to change in the registry

HKLM\System\CurrentControlSet\Control\Print\Enviroments\Windowsx64\Drivers\...\Driver name\PrinterDriverAttributes

If the driver is false PrinterDriverAttributes will be an even number and needs to be incremented by 1 to make it odd. This then makes it think its a packaged driver.

A hack but it worked for me. I can find the original post I found this on but I have found this that should explain it a bit more:

https://community.usa.canon.com/t5/Office-Printers/Package-Aware-Print-Drivers/td-p/180787

[profit10]

My print server does not have that registry key for any of the drivers. Can it just be created with a value of 1?

[mikeglover]

My print server does not have that registry key for any of the drivers. Can it just be created with a value of 1?

 

Thats odd. Havn't seen a driver without one so can't comment on whether it should be added. What make is it?

[profit10]

HP, Brother, Ricoh. None of them have it.

[JackT]

Had this similar Error 0x80070bcb but on Windows 7 clients and 2012R2 print server. In the end it is because the printer driver being used on the server was not packaged and a recent Windows update has broken stuff. This can be found under Print Management > Drivers and will be set to false for packaged? In our case Canon driver are not updated to be packaged drivers.

On the print server I had to change in the registry

HKLM\System\CurrentControlSet\Control\Print\Enviroments\Windowsx64\Drivers\...\Driver name\PrinterDriverAttributes

If the driver is false PrinterDriverAttributes will be an even number and needs to be incremented by 1 to make it odd. This then makes it think its a packaged driver.

A hack but it worked for me. I can find the original post I found this on but I have found this that should explain it a bit more:

https://community.usa.canon.com/t5/Office-Printers/Package-Aware-Print-Drivers/td-p/180787

 

 

Tested that out last night with our print server, came back today and its successfully applying the mono printer again!

 

Thank you soo bloody much, was pulling my hair out over this one.