|
|
United States-English | |
|
|
 |
|
HP 9000 Networking: Supervising the Network > Chapter 5 Customizing the User Environment
About Login Scripts |
|
|
You can use login scripts to automatically set up your users' workstation environments whenever they log in to the network. Login scripts are similar to configurable batch files and are executed by the LOGIN utility. You can use login scripts to
Login scripts work the same way for DOS and Windows workstations. When a user logs in, the LOGIN utility executes the appropriate login scripts. Four types of login scripts are available, and they can be used separately or together to tailor a custom environment for your users. All four types of login scripts are optional. They are described here in the order they are executed:
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.
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:
Since up to three login scripts can execute whenever a user logs in, conflicts can occur. If this happens, the last login script to execute (usually the user login script) overrides any conflicting commands in a previous login script. Login scripts are properties of objects. Table 5-1 shows which objects can contain which login scripts. Table 5-1 Objects that Contain Login Scripts
Figure 5-1 shows where the different types of login scripts can reside in a Directory tree. In the previous figure, there are three users: ESAYERS, SWILLIAMS, and MRICHARD. The following table shows which login scripts execute when each of these users logs in.
Container login scripts only affect users in the Organization or Organizational Unit that contains the login script. For example, in Figure 5-1, although there are two levels of container objects above users ESAYERS and SWILLIAMS, only the container login script for the container they are in (OU=SALES_PV) executes. If the SALES_PV Organizational Unit had no container login script defined, no container login script would execute for ESAYERS and SWILLIAMS, even though a container login script exists at a higher level. Because user SWILLIAMS has no user login script defined, the default login script executes after the container login script. Since user MRICHARD belongs to the profile CLERKS, the CLERKS profile login script executes before MRICHARD's user login script. Users can be assigned to only one Profile object, but other profile login scripts can be specified at the command line, for example,
You can, however, assign users to more than one Group object. Then use the MEMBER OF "group" identifier variable to specify that different parts of a login script execute, depending on the Group objects to which the user belongs. For more information about using the MEMBER OF "group" identifier variable in login scripts, see "IF...THEN" and "Identifier Variables" in this chapter. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 Printable version |
|
|
|
|
|
|||||||||||||||
|
|||||||||||||||
