Yes, I do this. The print server is a Linux box using Samba + Cups. I installed the cups-pdf package which sets up the printer queue for me in Cups. I then had to customise /etc/cups/cups-pdf.conf and change the following settings:
Then samba needs to be told about the new printer and windows drivers need to be loaded.
#label file names with unique jobid to avoid overwriting jobs with the same filename
#Disable anonymous use
At which point you can add it to your printer scripts and you are able to print to the pdf printer. However there's no way to access the PDF files it produces yet, so we need to make a new share in samba for that. I did mine like this:
cupsaddsmb -v -H hermes -U 'hermes\root' PDF
Users can now access this share however they like. I'd suggest either a drive mapping or a shortcut on their desktop. Personally, I map the P: drive in the login scripts.
comment = PDF files
path = /var/spool/cups-pdf/out
browsable = yes
read only = yes
hide unreadable = yes
guest ok = no
Also note, because of the umask we set in cups-pdf.conf and the 'hide unreadable' setting being enabled here, users will only see their own pdf prints. eg.
The final thing you need to do, is clean things up on a regular basis to stop your print servers disk becoming full of useless pdf files. I do this nightly in a cronjob
root@hermes:/var/spool/cups-pdf/out# ls -l
-rw------- 1 mmilne domain users 36334 2008-03-05 08:14 job_10031-tmp7.pdf
-rw------- 1 dstephenson domain users 17119 2008-03-05 09:15 job_10055-Microsoft_Word_-_Dulce_et_decorum_est.pdf
you might want to run rm verbosely (with the -v option) for the first few nights to check it's working ok. Also tell your users when and how often you clean up.
0 0 * * * rm /var/spool/cups-pdf/out/*.pdf