GPO problem with scripts
I have a printer script (vbs) that 100% works when clicked via staff or admins but when I add the script to lets say 6thFormGPO under user config -> windows settings -> scripts -> logon it doesnt run, nor does anythig else I put in it ie .bat . Is this where I should put scripts or can anyone help me??
Also I use deploy printer (windows 2003 r2) but I mostly want to do a default printer and really run scripts from particular OU's
Software restriction policy set to allow it?
Anything in the event log?
Nothing in either client/ server event logs
I've relised where I've screwed up, it works in user config - script but not computer -> user config. What I want to script default printer per room ie 6th form printer for 6th form, admin printer for admin, how would I do this through computer config? Thanks
Run the script on the computer usinf loopback processing in Merg mode. That would allow you to apply a script to a Computer Account but using the User section of the policy.
To set it up what you need to do is:
1. Create a Group Policy with the Loopback Policy enabled:
Computer Configuration --> Administrative Templates --> System --> Group Policy
User Group Policy loopback processing mode: Enabled & Merge
2. Create a Group Policy attached to the OU containing the computer account with the script in the:
User Configuration --> Windows Settings --> Scripts Logon --> printers.vbs.
The Replace operation stops all other User based policies applying there and only uses those that would apply to the Computer OU.
The Merge operation uses the normal User based policies as well, but any policies set on the Computer OU take precedence.
Thanks, well my 6thform ou look lik ethis, if its correct?
6thformprinterinstall -> deploy printer mon + col
i just shove the actual printer scripts in netlogon\printers then write a script that copies a shortcut to the appropriate script (say 6th from) to c:\docs and settings\all users\start menu\programs\startup. that way it runs per machine for whoeve logs in
can't you use the Print Management features that are part of 2003 R2...
These allow you to deploy printers to OU's and either a user or machine via group policy.
Print management in r2 doesnt include default printers, its defaulting to col when I want to default to mon
Thanks Stuart, I did the group policy merge also with a 40 sec vb script delay and now it works :)