I had to abandon the log in script as it was intermitant whether or not the script ran ok even with a pause of 30 seconds (you also have to use a 3rd party util to run setprinter as an admin in command line). I had to revert to running scheduled tasks.
Log in to the server via RDP so the printer maps.
Log in to the server locally and Edit the security of the printer to allow "Every one" Print, Manage Printers and manage documents.
open up CMD and type 'setprinter -show "printer name" 3' (3 is for security information)
now you need to use that security info for set security settings.
the command show look something like this
'setprinter "Samsung SCX-4300 Series (from COMPUTER_NAME) in session 1" 3 pSecurityDescriptor=O:BAG:SYD:(A;;LCSWSDRCWDWO;;;PU)(A;OIIO;RPWPSDRCWDWO;;;BA)(A;;LCSWSDRCWDWO;;;BA)(A;CIIO;RC;;;CO)(A;OIIO;RPWPSDRCWDWO;;;CO)(A;;LCSWSDRCWDWO;;;WD)(A;OIIO;RPWPSDRCWDWO;;;WD)(A;OIIO;RPWPSDRCWDWO;;;S-1-5-21-2644465320-2441601434-3013455542-1121)(A;;LCSWSDRCWDWO;;;S-1-5-21-2644465320-2441601434-3013455542-1121)' (dont use this command as it contains users specific to our server).
there are a few problems with this. It only fixes session 1 so you'll need to run it multiple times changing the session number. the terminal server we have only has a few users so I only need to run it up to session 12.
now add into scheduled tasks as many as you need changing the session number. tweak the job to what will suit your needs this may be to run every 5 minutes or every hour. but remember the printer wont work until this job has run.
it is a pain and to be honest it is now taking up too much admin time when it doesn't work so we are now looking into replacing this printer (the 4200 series doesn't have these problems).
