I'm trying to find a way to install network printers as part of a scripted install. Currently I use a batch file as a post install task and that does succeed in getting the printers installed for the local admin account, however those printers do not show up when another user logs in. Is there a way I can install these printers for all users other than making them local printers or relying on group policy?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Here is one method I have found to work - after you login it takes a few seconds before showing up so give it a little time to run.

rundll32 printui.dll PrintUIEntry /ga /n "\\SERVERNAME\PRINTER SHARE NAME"

Example:

rundll32 printui.dll PrintUIEntry /ga /n "\\ps0\Lab Color"

Dennis
Answered 10/05/2011 by: ddevore
Fourth Degree Green Belt

Please log in to comment
0
Yep, we rely on the PrintUI commands including /ga. Here's the documentation:

http://download.microsoft.com/download/8/2/c/82cffcfa-56f6-4fc3-bfa5-80cd84793871/PrintUIUsersGuide.doc

Note one thing: if you add per-machine printers using /ga, you have to remove them from the machine with /gd; a user can't remove the per-machine printer from the Windows user interface. Sande
Answered 10/05/2011 by: snissen
Fourth Degree Green Belt

Please log in to comment
0
This method works great until you have to make a change to the print server that would effect client connections. I have found that if the driver changes on the print server, you need to change the share name of the printer, apply this change, then change it back to the original share name for the driver update to deploy to already connected clients.
Answered 10/12/2011 by: bgraham
Yellow Belt

Please log in to comment
0
In several years of using the PrintUI techniques with our Windows Server for printing, I've never seen this problem. When I update a driver on the server, the client computers get the new driver as they check in. I don't have to change the share or anything else to make this happen.With Windows 7 clients, I did have to set a registry value in the client computers so standard users would not be prompted to update the driver.

The biggest problem I've seen is this: as much as possible, I'm using universal or global print drivers from the major manufacturer, which means one driver across most printer models. But when I update this global driver on one printer, all the other printers than use the same driver also switch to the new driver at the same time. So that means I cannot test a new driver: put it on one printer and it applies to all of them. Despite this, I think the global/universal print drivers are a great innovation, and they have reduced the support load substantially. I'm even using the Xerox Global Print Driver on an HP printer too old for the HP Universal Printing Driver, a LaserJet 5M!. Sande
Answered 10/17/2011 by: snissen
Fourth Degree Green Belt

Please log in to comment
0
Do a search for Printer Migrator from Microsoft, not supported with Windows 7, but I have seen it work.
Answered 10/19/2011 by: cserrins
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity

Share