[1703, cu] Printer not deploying.

[newpersn]

Got an issue with a OKI B412 not deploying it drivers.

 

I've checked event viewer and no real error message appeared there.

 

The user 'LANGOFFICE' preference item in the 'Win10 Default Computer ' Group Policy Object did not apply because it failed with error code '0x80070bcb The specified printer driver was not found on the system and needs to be downloaded.' This error was suppressed.

 

Event ID: 4098

 

I've checked the registry and have and have changed PrinterDriverAttributes to "5" and its still not deploying?

 

What am i doing wrong?

[newpersn]

Anyone?

[dapaulio]

Have you installed both x64 and x86 drivers (if you have a mixed architecture between server and client.

[Sheridan]

I've had weird things like this before and sometimes the fix is to use an alternative driver, or preload the driver onto the pc image, which isn't always practical.

 

I think there is also a group policy setting to allow pcs to download printer drivers from the internet if it can't find them on the server?

[newpersn]

Have you installed both x64 and x86 drivers (if you have a mixed architecture between server and client.

 

Yep both drivers are installed on the print server.

 

I've had weird things like this before and sometimes the fix is to use an alternative driver, or preload the driver onto the pc image, which isn't always practical.

 

I think there is also a group policy setting to allow pcs to download printer drivers from the internet if it can't find them on the server?

 

Be nice to know but the drivers are on the print server. I can add the printer via control panel and it will install. (Does ask admin right during install for driver)

[dapaulio]

Have you tried script installing the printer then linking it to a group policy.

 

All my printers use scripts because of old print drivers where I had similar issue with some drivers

 

Whilst printers were being installed it would take a lot longer than script installed

Edited August 31, 2017 by dapaulio

[Sheridan]

Are you using Printer Deployment, or adding them by Preferences?

 

The Policy I had to change was Computer\Administrative Templates\Printers\Extend Point and Print connection to search Windows Update - Allowing this seemed to help where it didn't think the right driver was on the server, even though I had the latest x86 and x64 drivers on there. Another foible of W10.

[newpersn]

Are you using Printer Deployment, or adding them by Preferences?

 

The Policy I had to change was Computer\Administrative Templates\Printers\Extend Point and Print connection to search Windows Update - Allowing this seemed to help where it didn't think the right driver was on the server, even though I had the latest x86 and x64 drivers on there. Another foible of W10.

 

I just changed that and will try once I get in to work.

 

All printers are set via gpp.

[dapaulio]

Try using adprintx.exe see if that works

[SuperduperPackager]

All printers are set via gpp.

 

I was using gpp too before and was having problems with printers not installing sometimes.

 

I converted everything to a powershell script and realised that the problem was still happening. So I did more research and unfortunately it seems to be something with the HP universal drivers.

 

The solution was to still use the powershell script but send the command to install the printer 3 times in a row instead of just once. That fixed everything.

 

When the printer is already installed, it doesn't matter if you send the command to install it again, it just skips it. It's not the cleanest solution but it works.

[skell]

Make sure the packaged driver state in the print server is true. If it isn't you can hack the registry a bit to make them true.

 

Since KB3170455 we need to enable point and print restrictions and specify our print servers in the GPO. For most of our printers there were no issues, however a couple of printers were not being pushed out by Group Policy Prefs since the update, even though the print server was listed in the point and print GPO.

Browsing the print share and trying to connect the printer manually would result in the "Do you trust this printer" pop up which will then prompt for admin creds to install the driver. Looking at Print Management on the server in question shows that the problem printer drivers have a "Packaged" status of false.

Now apparently if you are pushing out printers via GP or GP Prefs and they are of Non-Packaged type you will always get a prompt to install, ignoring the point and print GPO, which will obviously cause the install to fail.

A solution to this is a registry edit on the print server - obviously test this first before putting it into production.

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

Change the value from 0 to 1, and reboot the print server.

Back in Print Management you will see the Packaged status is now change to true, and the printer will now deploy.

Obviously if you can find packaged print drivers then use those, but some manufacturers haven't bothered.

EDIT: The value for other print drivers may not be 1, but to make this work the value needs to be set to an odd number.

[bigal06]

I was using gpp too before and was having problems with printers not installing sometimes.

 

I converted everything to a powershell script and realised that the problem was still happening. So I did more research and unfortunately it seems to be something with the HP universal drivers.

 

The solution was to still use the powershell script but send the command to install the printer 3 times in a row instead of just once. That fixed everything.

 

When the printer is already installed, it doesn't matter if you send the command to install it again, it just skips it. It's not the cleanest solution but it works.

 

Funny - I got this issue testing Win 10 (1607) and printers only install after logoff and on again. Updated drivers and tweaked registry key to stop searching internet for Icons and still very intermittent. Our printers are deployed via login script and works fine with Win 7 but Win 10 is problem.

 

After adding the printer to install twice in the script it works flawlessly every time so seems the solution is to install printers more than once. It works but would love to fix this without installing twice.

 

 

Many thanks for your idea.