Using Container Profile Login Scripts in the Place of Group Login Scripts
Articles and Tips: qna
01 Nov 2002
Q.
I'm trying to set up a particular group of individuals with specific login scripts. However, I've not found any information that will allow me to do
this.
The group object I created (as well as the other already in existence) doesn't have the option for a login script. I have created a profile login script to resolve this issue but the profile won't allow me to assign member to use it's login script--I have to visit each user's object.
Do you have any suggestions that can help me resolve this issue? Or, can you refer me to some information that can help me? Any help would be appreciated.
Scripting in Salerno
A.
Dear Scripting: NetWare 4 and above provides three types of login scripts. When a user logs in, the LOGIN utility executes the appropriate login scripts. Three types of login scripts can be used together to specify a custom environment for your users. All three types of login scripts are optional.
Container login scripts set general environments for all users in a container (such as an Organizational Unit). These login scripts execute first. Profile login scripts set environments for multiple users. These login scripts execute after a container login script. User login scripts set environments specific to a single user, such as menu options or a username for electronic mail. These login scripts execute after container and profile login scripts.
The LOGIN utility also contains a default login script. This login script executes the first time you log in as User object ADMIN. It contains only essential commands, such as a drive mapping to NetWare utilities. This default login script also executes for any user who doesn't have an individual user login script.
If you don't want to create a user login script and you want to prevent the default login script from executing, you can disable the default script by including the NO_DEFAULT command in the container or profile login scripts.
Maintaining many user login scripts can be time consuming. Therefore, include as much customizing information as possible in the container and profile login scripts, which are fewer in number and are easier to maintain. For example, if all users need access to NetWare utilities in the same volume, put the search drive mapping to that volume/directory in a single container login script rather than in every user login script.
You can also create profile login scripts if there are multiple users with identical login script needs. These 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. 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.
From what I understand, putting a login script at a group level cannot be done, however, you can do so at the profile or container level.
* Originally published in Novell AppNotes
Disclaimer
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.