Where Different Types of Login Scripts Can Reside
Figure 1-1
Organization:
Holds container script.
Organizational Units:
Hold container scripts.
User:
Holds user script.
In the figure, there are three users: ESAYERS, SWILLIAMS, and MRICHARD. The following
explains which login scripts execute when each of these users logs in:
User ESAYERS: The SALES_PV container login script executes first, followed by
ESAYERS's user login script.
User SWILLIAMS: The SALES_PV container login script executes first, followed by the
default login script.
User MRICHARD: The ACCOUNTING container login script executes, followed by the
CLERKS profile login script, and then the MRICHARD user login script.
Container login scripts affect only users immediately below the Organization or Organizational Unit
that contains the login script.
For example, in the previous figure, although there are two levels of container objects above users
ESAYERS and SWILLIAMS, only the script for the container they are in (OU=SALES_PV)
executes when they log in.
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.
Because user MRICHARD belongs to the profile CLERKS, the CLERKS profile login script
executes before the MRICHARD user login script. Users can be assigned to only one Profile object,
but there are ways to get around this restriction. See
Login Script Restriction" on page
(OU)=Sales
(OU)=Sales PV
(CN)=ESAYERS
(CN)=SWILLIAMS
"Getting Around the One User and One Profile
15.
[ROOT]
[ROOT]
(O)=Novell US
(OU)=Accounting
(CN)=MRICHARD
Holds profile script.
User:
Holds user script.
Belongs to "CLERKS"
Profile object.
(CN)=CLERKS
Profile:
Using Login Scripts
11
Need help?
Do you have a question about the LOGIN SCRIPTS - 08-2008 and is the answer not in the manual?