30
Novell Client for Windows
Profile sets environments for several users at the same time. Profile login
script are executed after the container login script and are associated with
Profile objects. A user can be assigned only one profile login script but
can choose other profile login scripts.
User sets environments (such as printing options or an e-mail username)
specific to a single user. User login script are executed after any container
and profile login scripts and are associated with User objects. A user can
have only one user login script.
Default contains only essential commands, such as drive mappings to
NetWare utilities, and cannot be edited. The default login script runs if a
user (including user Admin) doesn't have a user login script, even if a
container or profile login script exists.
HINT:
If you don't 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.
Maintaining many user login scripts can be time consuming. Therefore, you
should try to include as much customization information as possible in the
container and profile login scripts, which are fewer in number and easier to
maintain.
For example, if all users need access to the NetWare utilities in the same
volume, 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 several users have identical login script needs.
Profile login scripts are sometimes thought of as group login scripts.
Finally, in user login scripts, include only those individual items that can't be
included in profile or container login scripts.
IMPORTANT:
Because up to three login scripts can execute whenever a user logs
in, conflicts can occur and drive mappings can be overwritten by consecutive login
scripts. It is important to note that the last login script to execute (usually the user
login script) overrides any conflicting commands in a previous login script.
HINT:
In Windows NT and Windows 2000, all drive mappings created using
NetWare LOGIN are root mapped. Because of this, programs cannot access
directories above the directory that the drive is mapped to. If necessary, you can
turn off the default by adding SET MAPROOTOFF="1" as the first line in the login
script. This will globally force all NT/2000 workstations using the login script to not
map root drives.
WARNING:
Don't delete the login directory (SYS:LOGIN) created during network
installation. It contains the Novell LOGIN and NLIST utilities. If users run command
line utilities, they can use these utilities to log in and view a list of available NetWare
servers.
Need help?
Do you have a question about the NETWARE 6-DOCUMENTATION and is the answer not in the manual?