I am trying to assign network printers to XP clients from a W2K server using the program Discover. I have built the package (before snapshot,installed the driver and set up the port and after snapshot)and assigned it to a client. The package is picked up by the client but the printer does not appear in the Printers folder, however the port is picked up OK. Can anyone help?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Assigning network printers to clients using an msi file
- Thread starter FredNoB
- Start date
It doesn't work that way. Printers are assign per user so you can't create an MSI for a profile that is not gonna be the same when you run the package. That's why the port makes it, but never the printer.
here is a message that Dillanger99 posted:
I have users run the following batch file that corresponds to the network printer that they want to install.
rem /y makes printer default
rundll32 printui.dll,PrintUIEntry /in /n \\server\printername
rundll32 printui.dll,PrintUIEntry /in /n \\server\nextprintername /y
If I have 20 printers, I have 20 batch files. That way when users go from one machine to another they can install whatever printer they want without asking me to do it for them. The batch file can also install all twenty printers if I put them all in there. This has saved me LOTS of time.
"In space, nobody can hear you click..."
here is a message that Dillanger99 posted:
I have users run the following batch file that corresponds to the network printer that they want to install.
rem /y makes printer default
rundll32 printui.dll,PrintUIEntry /in /n \\server\printername
rundll32 printui.dll,PrintUIEntry /in /n \\server\nextprintername /y
If I have 20 printers, I have 20 batch files. That way when users go from one machine to another they can install whatever printer they want without asking me to do it for them. The batch file can also install all twenty printers if I put them all in there. This has saved me LOTS of time.
"In space, nobody can hear you click..."
- Thread starter
- #3
I can already assign a printer manually to a local workstation so that no matter who logs onto that computer they will only see that one particular printer. I can do this by setting up the network printer on a local port while logged on as local admin. It would make sense then that I should be able to apply a printer through a package.
Well, this topic comes back every day almost and the only solution that has seen the light is with the Rundll32. I'm not saying that it's impossible to use an MSI, but I've worked for corporations with 5000+ PCs and they couldn't get it done either.... so if there is a way, hope you find it and you can share it with us.
"In space, nobody can hear you click..."
"In space, nobody can hear you click..."
- Status
Similar threads
- Locked
- Question
- Locked
- Question