Jump to content

Recommended Posts

Posted

Hi, One of out Techies has updated a printer driver on his machine for the Pool of MFD's this has resulted in all machines on the network now wanting to install an updated driver, when the user tries to print it advises to update the driver, they press ok and it tries but fails to install. This is both Win 7 and Win 10, tried permissions but not made a difference. Has anyone any ideas please?

 

Thanks

Posted
Point and print restrictions in GPO ?

 

They were set to disabled so I have enabled them and configured as Microsoft advise but no difference. When we try to print a dialogue box appears with Do you trust this printer, windows needs to download and install a software driver from the ...

We press install and it starts to install but then just reverts back to the dialogue box.

Posted
They were set to disabled so I have enabled them and configured as Microsoft advise but no difference. When we try to print a dialogue box appears with Do you trust this printer, windows needs to download and install a software driver from the ...

We press install and it starts to install but then just reverts back to the dialogue box.

 

Have you added the server(s) that host the printers into the GPO?

 

Administrative Template -> Printers -> Package Point and print - Approved servers

 

We needed to do that recently.

  • 2 weeks later...
Posted

Apologies if this isn't an answer for the OP, if I have got the 'wrong end of the stick', or if this is old news and there are better solutions now... As an aside to the answer below, I am quite interseted though in the fact it appears from the OP that changing a driver on a client machine, has prompted other clients to request a new driver from the server....?

 

Hi, hopefully the OP is sorted and I'm not even sure if my issue is the same, but just had a problem getting a printer to install automatically (well thinking about it iirc it has been an issue for quite a while, but only as I am testing a Win10 install has it come to prominence).

 

We rarely have to reinstall the OS and have very few printers and little movement between teachers needing different printers assigned to them.

 

They basically have a standard colour printer and a B/W MFD. The only thing that needs changing for most is a year group mono printer if they change year group (which is possibly only once a year). I began to realise that on some when I changed them into the correct year group in AD, the printer for that year group wouldn't install and on occasion they have tried themselves but it has prompted with either the 'Do You Trust?' dialogue box or flat out asked for Admin credentials... In the back of my mind I somehow knew that this shouldn't be happening but didn't pay much attention to it.

 

In any case it is only a couple of minutes job to add a printer for them manually. However, I did try to automate the process a while back, originally deployed through a script I changed to deploying them through GP and more recently changing to GPP. Within the GP PnP restrictions I thought I had set the correct server and selected no prompts etc.

 

In the new Win10 install, although the main printers were added fine, the year group one wouldn't. Originally I thought I would need new drivers (as the original ones on the server are Win7) so I downloaded the latest and added them to the server. Still no joy, so I decided to do some research. In amongst the answers was a suspect KB (3170455) mentioned in this EDUGEEK thread from LAST YEAR!:

 

http://www.edugeek.net/forums/windows-7/172860-kb3170455-preventing-printer-installation.html

 

But interestingly enough, that lead me onto other searches which yeilded other solutions (can't believe I haven't really looked into this before now), and apart from the PnP restriction settings in the GP (which made no difference) the answer was that the KB had an effect on printer drivers that were not 'package aware'.

 

Checking Print Management' on the server indeed showed me that the drivers (Brother) that I was having trouble with were NOT packaged. Although, this was from a while ago and I'm not sure if this is still how things should be done - the solution was to use regedit to fool Print Management into thinking that the drivers were 'Packaged' (these were the latest drivers from Brother as it's an older model printer, I presume they haven't bothere to make them packaged).

 

Sources:

 

Unable to Install Print Driver after KB3170455 | Windows OS Hub

https://www.reddit.com/r/sysadmin/comments/50gw1b/solved_deploying_nonpackaged_print_drivers_after/

Be aware of KB3170455,KB3172985,KB3163912 if you have printers ;) !!! (updated)

https://www.richardwalz.com/group-policy-printer-issue-print-and-point-restrictions-kb3170455/

https://community.spiceworks.com/topic/1741492-deploying-printers-with-kb3170455-applied (post on regedit is about half way down)

 

Now some just say it works just changing the GP, some say it works with ADDING a '1' to the reg key (as in 4+1=5), some say add a '1' (as in 4 add one = 41), some say just change it to '1'! I changed mine to '1' from '4' but YMMV!

 

There was also this 'solution' but I'm not keen on unistalling and reinstalling updates (especially once you read what it can break), so I can't tell you if it works:

 

Source:

 

Solved: Re: FYI - Unable to install client drivers in some... - Customer Support Forum

 

Solution;

 

- Remove hotfix KB3170455 from the 2012 R2 print server.

 

- Install hotfix KB300850 on the 2012 R2 print server.

 

- Re-install hotfix KB3170455 on the 2012 R2 print server.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...