A logon script is an executable or batch file composed of
operating system commands that runs automatically when a user logs
on to a computer running Advanced Server/9000, Windows NT Server,
or Windows NT Workstation. Logon scripts are used to configure users'
working environments, make network connections, and start applications.
They also can be used to run programs that scan for viruses on client
computers.
There are several advantages to using logon scripts:
You can manage parts of users'
environments, such as network connections, without managing every
aspect of the environment.
You can use them to create common network connections
for multiple users.
Logon scripts are easy to create and maintain.
You can continue to use logon scripts that were
created in LAN Manager, Version 2.2.
 |
| |
|
 | NOTE: User profiles can restore network connections at logon
that were established prior to logging off but they cannot be used
to create new network connections at logon. |
|
| |
|
Creating Logon Scripts |
|
You can create logon scripts using a text editor and then
use User Manager for Domains to assign different logon scripts to
different users or to assign the same logon script to multiple users.
There are several special parameters you can use when creating
logon scripts:
Assigning Logon Scripts to User or Group Accounts |
|
You can assign a logon script to a user account or group account
by entering a path in the logon script file in User Manager for
Domains. When a user logs on and a path to a logon script is present
in the user account, the file is located and run.
In the User Environment Profile dialog box, you can assign
logon scripts to user accounts by typing the file name (for example,
clerks.bat) in the Logon Script Name box. At logon, the server authenticating
the logon locates the logon script by looking for the specified
file following that server's local logon script path (usually
/var/opt/asu/lanman/shares/asu/repl/import/scripts on import computers
or /var/opt/asu/lanman/shares/asu/repl/export/scripts on export
servers). If a relative path is provided before the file name (for
example, admins/cristalw.bat), the server looks for the logon script
in that subdirectory of the logon script path.
The entry in the Logon Script Name box specifies only the
file name (and option ally the relative path); it does not create
the actual logon script. You create the logon script and place it
in the appropriate directory on the replication export server.
You can place a logon script in a local directory on a user's
computer but usually this location is used when administering user
accounts that exist on a single computer rather than in a domain.
In this case, the logon script following the logon script is placed
after the computer's logon script path or in a subdirectory
of that path.
For more information about configuring a user environment
profile, see User Manager for Domains Help.
Setting Up Replication of Logon Scripts |
|
A logon script always is downloaded from the server that validates
a user's logon request. For users with accounts in Advanced
Server domains that have one or more backup domain controllers,
any one of the domain controllers can authorize a user's
logon attempt. To be certain that logon scripts always will work
for users, ensure that the logon scripts for every user account
in a domain exist on every primary and backup domain controller
in the domain.
The best way to ensure that logon scripts always are available
is to use the Directory Replicator service. This service maintains
identical copies of a directory tree on multiple computers. When
you make a change to a file in the master copy of the tree (located
on the export server), the Directory Replicator service automatically
copies the change to the import computers.
When the Directory Replicator service is used with logon scripts,
set up one domain controller as the export server and all of the
other domain controllers in the domain as import computers.
The logon script path can be configured for every server in
a domain using either Server Manager (locally or remotely) or the
Server option in each server's Control Panel. Use the Directory
Replication dialog box to set up replication export and import and
to specify a local path to user logon scripts.
Generally, a master collection of logon scripts is maintained
by an administrator in an export directory (usually /var/opt/asu/lanman/shares/asu/repl/export/scripts
and its subdirectories) of one replication export server in the
domain, and this master collection is replicated to all the servers
in the domain so that each server has its own local copy of all
logon scripts.
For more information about the Directory Replication service,
see Chapter 5, "Managing Shared Resources and Resource
Security." Also, see "Managing Export Replication"
and "Managing Import Replication" in Server Manager
Help.
Printable version
