Problems adding network printer (via login script) to a domain computer

Dear experts,

I'm having trouble with one of my Vista clients in my SBS 2003 domain. I have a network printer installed on the server and I use a login script for all domain users that adds the network printer using this line:

AddPrinterConnection ("\\servername\printername")

This works fine for all users logging on to their XP machines, but after I got a new Vista machine for one of the users, it refused to add the printer when logging on. Instead, a popup appears asking the user to install the printer driver (OK / cancel). When I click OK, the client appears to be doing something, but no printer is added. Domain users have no installation rights.

I've disabled Windows Firewall in Group Policy for all clients when they are connected to the LAN by cable.

Any ideas how to solve this? Thanks!
Who is Participating?
mbootsConnect With a Mentor Author Commented:

The problem was that the domain user didn't have permissions to install the printer driver on the Vista machine. I already added the domain user to the local power users group on the client, but this turned to be insufficient. I made the domain user local administrator on the client and this did the trick! Clicked OK on all the popups and the printer was added flawlessly.

Thanks for your suggestions everyone.
what is the make/model of the printer, what version of vista
mbootsAuthor Commented:
Actually there are two printers: a Minolta C252 and a HP CP2025. For the sake of simplictiy I left this bit out.

The client is running Vista Business SP1.
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

JohnBusiness Consultant (Owner)Commented:
My experience with this (I run Vista Business 64-bit) is that you need to go to the Minolta and HP sites and download the 64-bit drivers to the Vista machine. Explode the drivers so you have them readily available. Then when you do the Network Install, choose the "I have my own drivers" dialogue and point to the drivers you downloaded. In one case, I had to point to the printer by IP address to get this done. This is a bit of a pain, but I have not yet found another way.
.... T
mbootsAuthor Commented:
Thanks for the suggestions, but I don't see why I should install drivers on the client, when the driver is installed and working on the server. Clients should be able to use any network printer through the printer server (in this case, the SBS 2003 machine), regardless of their Windows OS.

I think the problem must be in the way I add the printer (through login script) or some kind of Vista client setting. Perhaps I have to alter something through GPO?

Vista does not allow standard users to install printers. You could use printer deployment via GPO if you have at least one DC with 2003 R2(!) in place. You could also loosen the restrictions:
JohnBusiness Consultant (Owner)Commented:
I suppose the word "install" can have different interpretations.  I haven't had any difficulty with HP Printers (but still very limited Vista experience in clients at this point). I have had trouble with non-HP printers and with Vista 64-bit. Many of the 32-bit drivers on the server are just not compliant with Vista. The only way I have found is to have the driver available at the time of install. I think this may need admin rights. The drivers that are compliant seem to allow a normal network installation just like XP. .... T
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.