align="justify"> # be created dynamically by ntlogon (check that you have it in the correct
# location (the default of the ntlogon rpm available in contribs)
; root preexec=/ usr/bin/ntlogon -u% U -g% G -o% a -d/var/lib/samba/netlogon
; root postexec=rm -f /var/lib/samba/netlogon/%U.bat
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
; [Profiles]
; path=/ var/lib/samba/profiles
; browseable=no
; guest ok=yes
# This script can be enabled to create profile directories on the fly
# You may want to turn off guest acces if you enable this, as it
# has not been thoroughly tested.; root preexec=PROFILE=/ var/lib/samba/profiles /% u; if [!-e $ PROFILE];
; then mkdir -pm700 $ PROFILE; chown% u.% g $ PROFILE; fi
# NOTE: If you have a CUPS print system there is no need to
# specifically define each individual printer.
# You must configure the samba printers with the appropriate Windows
# drivers on your Windows clients or upload the printer driver to the
# server from Windows (NT/2000/XP). On the Samba server no filtering is
# done. If you wish that the server provides the driver and the clients
# send PostScript ( Generic PostScript Printer under Windows), you have
# to use printcap name=cups or swap the print command line below
# with the commented one. Note that print commands only work if not using
# printing=cups
[printers]
comment=All Printers
path=/ var/spool/samba
browseable=no
# to allow user guest account to print.
guest ok=yes
writable=no
printable=yes
create mode=+0700
# =====================================
# print command: see above for details.
# =====================================
print command=lpr-cups -P% p -o raw% s -r # using client side printer drivers.
; print command=lpr-cups -P% p% s # using cups own drivers (use generic PostScript on clients).
# This share is used for Windows NT-style point-and-print support.
# To be able to install drivers, you need to be either root, or listed
# in the printer admin parameter above. Note that you also need write access
# to the directory and share definition to be able to upload the drivers.
# For more information on this, please see the Printing Support Section of
# /usr/share/doc/samba-lt;versiongt;/docs/Samba-HOWTO-Collection.pdf
#
# A special case is using the CUPS Windows Postscript driver, which allows
# all features available via CUPS on the client, by publishing the ppd file
# and the cups driver by using the cupsaddsmb tool. This requires the
# installation of the CUPS driver (# justify gt; # on the server, but does not require you to use Windows at all: -).
[print $]
path=/ var/lib/samba/printers
browseable=yes
write list =adm root
guest ok=yes
inherit permissions=yes
# Settings suitable for Winbind:
; write list=@ Domain Admins root
; force group=+ @ Domain Admins
# A useful application of samba is to make a PDF-generation service
# To streamline this, install windows postscript drivers (preferably colour)
# on the samba server, so that clients can automatically install them.
# Note that this only works if printing is * not * set to cups
[pdf-generator]
path=/ var/tmp
guest ok=No
printable=Yes
comment=PDF Generator (only valid use...
