New answers tagged printing
Restarting Print Spooler service on the client did the job. Restarting the service on the server didn't work. Our network: Win7Ultimate 64bit + a bunch of Win7Pro 64bit without domain, only workgroup.
If you're not looking for advanced printing functions, try installing the printer locally with the simplest driver that comes pre-installed, HP Deskjet 600 for example, but make sure your server has the same driver pre-installed.
"Load and unload device drivers" should do the trick. (Computer Settings -> Policies -> Security Settings -> Local Policies -> Load and unload device drivers) Be aware that this may grant more privileges than you intend. That said, granting "Load and unload device drivers" to Power Users is arguably more secure than making your users local administrators. ...
After changing the permissions to allow 'Local Host' full access, instead of seeing documents with a status of 'spooling' and dissappearing from the print queue, there are '*.tmp' files now appearing in the 'printers' folder. My colleague has now confirmed that since altering the permissions of the 'printers' folder, prints have been flying out.
You may need to reinstall the print drivers. You can download and install them from here: http://support.hp.com/us-en/product/HP-Color-LaserJet-Pro-M170-Multifunction-Printer-series/5303438/model/5303443/drivers. Completely uninstall the drivers and delete the disconnected device by using the devmgr_show_nonpresent_devices 1 environmental variable. Then ...
Would love for this to be a comment - if only I had the rep. Would love even more for this to be a private message but apparently stackexchange doesn't and will not ever do those. SteadH: Wondering if you had any luck with this? I'm trying to do the same thing myself. I've used the tamperdata firefox plugin to see what happens during a login process (i.e. ...
Top 50 recent answers are included