Difference between revisions of "Printer configuration"
m |
m |
||
Line 22: | Line 22: | ||
<package | <package | ||
id="printer-kyocera" | id="printer-kyocera" | ||
− | name="Kyocera printer"> | + | name="Kyocera printer" |
+ | execute="always"> | ||
<install cmd='rundll32 printui.dll,PrintUIEntry /q /y /ga /in /n \\server\kyocera' /> | <install cmd='rundll32 printui.dll,PrintUIEntry /q /y /ga /in /n \\server\kyocera' /> |
Revision as of 19:30, 12 March 2008
WPKG can be used for configuring printers, too.
When a new printer is configured on a server, it still has to be "installed" on a workstation.
A simple way to do it is the usage of startup scripts: executed with Administrator or SYSTEM rights - to install a printer on a workstation, and, user logon scripts, to install a printer for a user.
First, install a printer on a server and make sure it prints.
If it prints, add a line like this to /home/samba/unattended/packages/wpkg/wpkg-start.bat
(the batch file where the WPKG is started):
rundll32 printui.dll,PrintUIEntry /q /y /ga /in /n \\server\kyocera
with the appropriate servername and printername.
This has a drawback, that it'll be used by all machines.
To install a printer on certain workstations only, a WPKG entry like below could be used:
<package
id="printer-kyocera"
name="Kyocera printer"
execute="always">
<install cmd='rundll32 printui.dll,PrintUIEntry /q /y /ga /in /n \\server\kyocera' />
</package>
This ensures that it will be executed each time the workstation is booted.
Then, add the same line (rundll32 printui.dll,...) to user logon scripts.
After the machine is restarted, it should be able to use a new printer.