You could use a combination of providing...
- ...a shared hotfolder,
- ...a task scheduler job and
- ...batch (or other) scripting
...to serve your Macs. I would create such a functionality manually like this:
- Create a folder share on the windows print server that is accessible to your Macs. (This one will receive the PDFs from the Macs.)
- Setup the Mac queues to print to a "file" backend targetting the shared hotfolder on Windows. (Look here for an example how to create such a file backend: 2dir backend (Bash script, easy to adapt to Mac OS X environments). Make sure that the backend first writes the PDF under a different file suffix (such as *.pdf__), and only after completing the write operation rename the job to *.pdf. Make sure that the 2dir backend has file permissions of 700.
- On Windows, create a scheduled task that runs once a minute [*]. This tasks can be a batch file. The batch file's job is to move the 10 oldest (or newest) *.pdf files it can find in the hotfolder into a separate folder. That separate folder should be unaccessible for outsiders. It should only write to the separate folder, if no unprocessed PDFs from previous operations are left over there.
- Again on Windows, create another scheduled task [**]. This one also runs once a minute. It prints all PDFs it can find in the separate folder to your real Windows printer. Once sent to printer, it should also delete each PDF.
On Windows, you cannot run scheduled tasks more frequently.
[**] Why use 2 separate scheduler jobs? It introduces a certain buffering into the system. The second job never has more than 10 jobs to handle at once, even if the real hotfolder would receive thousands of jobfiles at once.