2008r2 Print Server problem when adding new printer

ajf · 2 Dec 2013 at 12:01

We have a 2008r2 based print server with around 40 networked printers installed, mostly HP models.
I recently added two new printers and after each one experienced what I would class as odd behavior.

I started getting users of existing printers, even ones using different models to the new one, getting a request to 'update driver'.
If they accept this and let it go through then their printer starts working again.

Obviously something in the new drivers is changing existing ones, but why and how can I stop it?
The oddest thing is it even affected HP printers when I added a NON HP printer!

anything I don't mind · 2 Dec 2013 at 12:07

First thing make sure you disable or configure point and print restrictions in group policy.

Is print management installed on the print server? Make sure each printer has the correct drivers associated, add the printers through group policy and use item targeting. Easier that way.

Hellsmk2 · 4 Dec 2013 at 17:13

My advice is to take all your HP printers outside and burn them. The drivers are the worst I have ever had to work with, and are the cause of 99.99999999% of printer issues at any sites/ companies I've worked with ( a lot!).

Alternatively, this article may provide a bit of help:

http://technet.microsoft.com/en-us/library/cc753269.aspx

kirbz · 4 Dec 2013 at 22:26

I would deploy them using goo. Go to print management, right click on the printer and select deploy using gpo.

You don't need to install drivers and you won't be prompted they will just install in the back ground. You can use gpp to delete them when you replace them.

Just bear in mind that vista and XP machines need client side extension update installing and you will need to use the pushprinterconnections.exe on XP machines.

ajf · 16 Dec 2013 at 14:38

Thank you for the replies and apologies as I forgot I had posted this!
I will look into the GPO options. Not sure if there is a reason we haven't done this or not.
From what is said here and on the web with GPO does it not actually install a driver onto the print server in the normal then?
Is GPO and Point and Print suggested because it can avoid the elevation request on driver updates?

We just install the print and share at the moment.

Interesting comment about HP drivers, although not one I can actually disagree with! However as devices they always seem to be pretty solid when you go for the lasers.

Long term we are likely to replace with a few large MFDs but that is a slow process due to costs of the devices.

#Chri5# · 16 Dec 2013 at 15:10

I think I saw the same problem recently when I replaced a LaserJet MFP with an OfficeJet X. IIRC, when printing to a different printer (a DeskJet), a W7 PC had stuck up a UAC type prompt to update the DeskJet driver.

JonnyT · 16 Dec 2013 at 22:40

Do you use the HP Universal Printer Driver (UPD) or device-specific drivers? In my experience using the UPD makes life a lot easier. I manage a printer estate of over 350 printers, the vast majority of which are HP using the UPD. Once a PC has got the driver installed (we use the PCL5 and PS drivers installed as separate print queues for each printer on the print server(s)) then it will not need to install all the files again for each printer, making installation a lot quicker.

JonnyT · 16 Dec 2013 at 23:04

The request to update files on existing PCs is probably because there are common files amongst even the device-specific HP drivers, and if you have different versions of the drivers - and therefore those files - Windows will then prompt to update them.

Windows exhibits some slightly odd behaviour when it comes to updating installed drivers on clients when the version is updated on the server; supposedly the client is meant to 'check in' upon first daily login with the server and then verify all the files for all the installed printers are correct and up to date. In practice it's not quite as obvious as that...

I'd recommend installing the version-specific model (I think the latest is 5.7.0) of the UPD drivers on your print server, and then slowly migrating your printers across to it as it makes management of drivers so much easier

www.hp.com/go/upd

covenantuk · 17 Dec 2013 at 11:58

Hellsmk2 said:
My advice is to take all your HP printers outside and burn them. The drivers are the worst I have ever had to work with, and are the cause of 99.99999999% of printer issues at any sites/ companies I've worked with ( a lot!).

The grass is not greener elsewhere. Windows doesn;t handle printing particularly well.

At least HP hardware is generally reliable, which is more than I can say for some other suppliers.

kirbz · 17 Dec 2013 at 22:33

http://technet.microsoft.com/en-us/library/cc722179(v=WS.10).aspx

As I said above this is the method I use.

The procedure for a new printer is to install it as normal on the server, with x86 & x64 drivers and then follow the above guide. It just makes life easier to let the server do the work. The drivers get installed automatically on the client computers without prompts. If the printer needs deleting I use group policy preferences to delete it.

I hope this makes sense.

ajf · 18 Dec 2013 at 23:06

I am certainly going to look more into the GPO options you link to in the new year. Helpful for a number of reasons anyway.
I think we did use the UPD software at one point but moved away from it for some reason. I did not build the print server so i will have to check the reasons for that.