Feizhou feizhou@graffiti.net wrote:
Er...those drivers are installed on the Windows client, not the samba server. Bryan's case is rather special. He is not talking about a raw queue but a postscript queue. Since it
is
postscript, all the Windows clients just need to install a postscript print driver (which of course will be downloaded from the Samba server) and then they are done. The printer settings will have been setup on the Samba server via CUPS as he said.
There are basically 4 ways you can setup Windows printer queues:
1. All Manual: Each one "raw" and go around manually installing drivers -- either SMB or an IPP/LPD/JetDirect port
2. Manual and Driver Share: Each one "raw" and setup Samba shares with the printer drivers (with associated settings in smb.conf)
3. CUPS, Postscript and Driver Share: Use CUPS so they are Postscript queues, use the Adobe Postscript driver, and setup Samba shares with the PPDs (with the associated settings in smb.conf)
4. CUPS-Samba, CUPS driver for Windows and Automated PPD Use CUPS so they are Postscript queues, use the CUPS drivers for Windows and use the CPUS-Samba script, which handles automatically publishing any CUPS changes into a fixed location the CUPS driver for Windows knows where to get PPD files for the printers without any manual intervention
#1 gives you manual fits
#2 and #3 has you setup a Samba share with printer info. #3 minimizes the printer setup by letting you merely plop out PPD files into the share. In either case, you _still_ have to edit smb.conf with the exact printer info, or use a separate GUI tool.
#4 takes #3 and puts it on steroids. Instead of using the non-CUPS aware Adobe Postscript driver, which still requires some manual intervention on the client side (like #2), you use the CUPS driver for Windows. Now you manage _everything_ from the CUPS interface, and run *1* command to update the PPDs to the share. The CUPS driver for Windows handles getting everything from the server, including updated PPDs.