Supervising the Network

5-4
Customizing the User Environment
About Login Scripts
The LOGIN utility executes the user login script after any container and profile
login scripts have executed. A user can have only one user login script.
• The default login script is precoded into the LOGIN.EXE command and is not
editable. It executes if a user doesn’t have his or her own user login script, even
if a container or profile login script exists.
The default login script is executed for all users (including user ADMIN) unless
you create a user login script. The default login script contains only essential
commands, such as drive mappings to the NetWare utilities.
To see the commands in the default login script, see “Default Login Script” in
this chapter.
If you do not want to create any user login scripts and you don’t want the
default login script to execute for any users, you can disable the default login
script by including the NO_DEFAULT command in the container or profile
login script.
To use the login script from an Organization, Organizational Unit, or Profile
object, users must have the Browse right to the object and the Read right to
the object’s Login Script property.
NOTE: For more information on Browse or Read rights for a file, object, or property, see
“Browsing” and “Rights” in Concepts.
Deciding Which Login Scripts to Create
Maintaining many user login scripts can be time consuming. Therefore, you
should try to include as much customizing information as possible in the
container and profile login scripts.
Here are some suggestions:
• If all users need access to the NetWare utilities in the same volume, for example,
put the search drive mapping to that volume in a single container login script
rather than in every user login script.
• Create profile login scripts if there are several users with identical login script
needs.
• In user login scripts, include only those items that cannot be included in profile
or container login scripts.