Previous Page
Next Page

Using Logon Scripts

In the old days, network administrators spent hours and hours trying to craft the perfect logon script. In the end, it was a fruitless effort, because needs were always changing and the capabilities of logon scripts were limited. Many networks today seem to run just fine without a logon script. With the widespread adoption of Group Policy, some people might question why we need logon scripts at all. However, when using Microsoft Visual Basic, Scripting Edition (VBScript) for your logon scripts, you can craft some very powerful solutions for configuring and maintaining your users' environments. In addition, because Group Policy is often handled by a separate department within enterprise networks, making a change to a logon script can be easier than talking another department into modifying its "perfect Group Policy." Logon scripts can be quickly called into service to perform several tasks:

  • Mapping network drives

  • Mapping printers

  • Collecting system information

  • Checking antivirus signatures

  • Checking hotfix and security updates

  • Checking security settings

Just the Steps

To create powerful and flexible logon scripts

1.
Use IADsADSystemInfo to determine user information.

2.
Use ADSI to query for group membership information.

3.
Use Windows Scripting Host (WSH) to map network drives.

4.
Use WSH to set default printers.



Previous Page
Next Page