Guy Recommends
A solution to monitor, manage and archive thousands of
events that are generated by devices across the entire network.
Download FREE
trial
Group Policy - User Logon Scripts
Creating Logon Scripts to map network drives and map printers, have been around since the dawn of networking. Microsoft's Group
policy embraces this Logon Script concept by supplying not one but 4 settings: Logon and Logoff policies are found in
the User Configuration. In addition Windows Server 2003 Group Policies have Startup and Shutdown scripts, but these settings are found in the Computer Configuration section of Group Policy.
Windows Server 2003 Group Policy Topics
User Configuration
Windows Settings
Scripts (Logon
/ Logoff)
Logon Scripts
Logoff Scripts
‡
Scripts (Logon / Logoff)
There are several reasons that I am particularly interested in scripting policies. Firstly,
I use logon scripts as one of my 'Litmus Tests' to judge amateurs and
professionals. If
you use Windows Server 2003 policies to assign VBScript Logon Scripts, then I consider you a professional, whereas if you prefer adding batch files to a user's
property sheet, then I consider you an old fashioned 'Luddite'.
Next, I would like to identify three different tasks for logon
scripts:
- Set the scope of the logon script. By that I mean which drives
and which printers to map in the VBScript.
- Write the script using VBScript or JScript.
See Logon Script Section.
- Assign the Logon scripts via Windows Server 2003 Group Policies. It is this assigning of the script, that I am going to explain on this page.
Troubleshooting
Group Policies is tricky
As an MCT trainer, I can thoroughly recommend TrainSignal because they
provide practical hands on training. In particular, I like the way TrainSignal cover all learning methods, instructor lead, video and of course text material. You can either take one module, for example Group Policy or go for
a combination of modules.
See more about Group Policy training here
Presuming that you have written or copied the VBScripts, all we have to do in Group Policy is add the .VBS file to the appropriate dialog box. I find that it is much better to
copy the .VBS file into memory before you open the policy box, than to try and
navigate once the dialog box is open.
My point is that I would prefer to right click and paste, rather than use the Open
and Browse option. See picture opposite.
If you do experiment with the 'Browse' and 'Look in' buttons, then you
will see the very long path where Group Policies in general and Logon
Scripts in particular are stored. \Windows\sysvol\sysvol\domain\policies.
Professional administrators use these logoff scripts to remove network
drives and to disconnect printers. An up-and-coming use of Group Policies is to create
logoff scripts is to delete temporary files and perform other house keeping
tasks. The script executes while the user logs off - I like it!
|