On Mon, Mar 31, 2014 at 9:46 PM, J- P <[email protected]> wrote: > is it possible the driver is not "verified" or signed"
Sure it's possible. Where does that leave me? :) PDFCreator is published by an indie freeware author, who often don't have have the resources/desire to sign anything, so that counts against it. It does not (as far as I've been able to determine) include an INF, and I believe you need an INF to sign a driver package. I have not received any warnings/prompts about driver signing in the GUI, nor seen any in the logs I've looked at. I believe the actual printer "driver" part of PDFCreator is really just a PPD file (PostScript Printer Definition); it uses the generic PostScript engine that comes with Windows. > also any reason you > cannot do this via print management and deploy with GPO? (1) PDFCreator is a software kit installed from an EXE package, not just a simple print driver. (2) A new port monitor has to be installed, and then a port using it created. (3) The port monitor requires some registry entries be made (to setup paths to files). The above actions have to happen in that order, before the local "GSView" printer object is created. Can you do all that with a GPO printer deployment? -- Ben
