I'm working on packaging an app. A printer driver is installed during the manual installation of this application. The printer appears in the list of available Printers right after the install.
However, running my package, I have to reboot before the printer appears. Did I miss capturing a setting? What can I do? Are there a registry setting(s) to correct this? Thanks!
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


I have found that the best way to add a printer is not to capture the registry settings, but to create a custom action that installs via APIs (this is likely to be the same as the vendor installation uses).

Run "RUNDLL32 PRINTUI.DLL,PrintUIEntry /?" to find out the various command line options available (as well as a number of examples)
Answered 02/18/2004 by: mrtap
Senior Yellow Belt

Please log in to comment

I have the same issue. I use:

rundll32 PRINTUI.DLL,PrintUIEntry /ga /c%computername% /n"\\%VARSSERVER%\%VARSPRINTER%" /j"LanMan Print Services"

to add an networked printer for all users, works like a charm, but only after reboot.

I guess the GUI triggers a refresh... But I also have no clue on how to archieve this manually. For right now, I just reboot...
Answered 02/19/2004 by: KPrinz
Fourth Degree Green Belt

Please log in to comment

Since You have used /ga You have to stop and start the PrintSpooler service

I could be done from a custom action.

Test it, instead of reboot stop the service and start it againg and see it works

sc \\targetcomputername stop spooler

sc \\targetcomputername start spooler

In the dos prompt try to run sc to se how to use it

Sweede :-)
Answered 04/22/2004 by: Sweede
Second Degree Green Belt

Please log in to comment