Subscribe to Our Youtube Channel
Related Manuals for Novell LOGIN SCRIPTS - 08-2008
Summary of Contents for Novell LOGIN SCRIPTS - 08-2008
- Page 1 AUTHORIZED DOCUMENTATION Login Scripts Guide Novell ® Login Scripts August 2008 www.novell.com Novell Login Scripts Guide...
- Page 2 Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
- Page 3 Novell Trademarks For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/ trademarks/tmlist.html). Third-Party Materials All third-party trademarks are the property of their respective owners.
- Page 4 Novell Login Scripts Guide...
-
Page 5: Table Of Contents
Contents About This Guide 1 Using Login Scripts Login Script Overview ............9 Where Login Scripts Should Be Located . - Page 6 December 23, 2005 ............63 Novell Login Scripts Guide...
-
Page 7: About This Guide
About This Guide ® This guide includes the following information on login scripts that can be used with Novell eDirectory user accounts and Novell Client software on Windows* and Linux* workstations: Chapter 1, “Using Login Scripts,” on page 9 Chapter 2, “Sample Login Scripts,” on page 21 Chapter 3, “Login Script Commands and Variables,”... - Page 8 Novell Login Scripts Guide...
-
Page 9: Using Login Scripts
1.1 Login Script Overview ® A login script is a set of instructions that is executed when a user logs in using the Novell Client for Windows, the Novell Client for Linux, or some other method of login that accesses Novell eDirectory object properties. -
Page 10: Where Login Scripts Should Be Located
User login scripts are executed after any container and profile login scripts and are associated with User objects. A user can have only one user login script. However, the User login script can be overwritten by selecting a different login script from the Novell Login window. - Page 11 Where Different Types of Login Scripts Can Reside Figure 1-1 [ROOT] [ROOT] Organization: (O)=Novell US Holds container script. (OU)=Sales (OU)=Accounting Organizational Units: Hold container scripts. (OU)=Sales PV (CN)=MRICHARD (CN)=CLERKS User: Profile: (CN)=ESAYERS (CN)=SWILLIAMS Holds user script. Holds profile script. User: Holds user script.
-
Page 12: Common Login Script Commands
1.4 Creating or Modifying Login Scripts ® You can use Novell iManager or ConsoleOne to create login scripts from scratch or from a sample login script that is provided for you. Using a sample login script can help reduce syntax errors and thus reduce the time it takes to create login scripts. -
Page 13: Creating Or Modifying Login Scripts In Imanager
1.4.1 Creating or Modifying Login Scripts in iManager “Creating or Modifying a User Login Script” on page 13 “Creating a Container Login Script” on page 13 “Creating a Profile Login Script” on page 13 Creating or Modifying a User Login Script 1 Click Roles and Tasks >... -
Page 14: Creating Or Modifying Login Scripts In Consoleone
3 Type the name of the Profile object in the Default Profile field located under the login script text box, then click OK. 4 Add the User object as a trustee of the Profile object by double-clicking the Profile object. Novell Login Scripts Guide... -
Page 15: Getting Around The One User And One Profile Login Script Restriction
Section 3.21, “PROFILE,” on page In addition to using the Novell Login Window or the PROFILE command, you can also assign users to more than one Group object. Use the MEMBER OF group identifier variable to execute different parts of a login script, depending on the Group objects that the user belongs to. To accomplish this, use the IF...THEN command (see... -
Page 16: Modifying User Login Scripts From The N Menu
1.6 Modifying User Login Scripts from the N Menu In addition to creating User login scripts in Novell iManager or ConsoleOne, you can also add user login scripts to User objects from the N menu in the system tray. This lets you customize the login script for the user that is currently logged in to the network, without running iManager or ConsoleOne. -
Page 17: Printing Login Scripts From Windows
1.8 Understanding How Login Scripts Work with Linux Workstations Novell has been able to port the vast majority of login script functionality over to the Linux platform. This means that the login scripts you create in your network will work for both Windows users and Linux users with very little difference in functionality. -
Page 18: Understanding How Login Scripts Work With Netstorage
These login scripts are the same scripts processed by the Novell Client. However, because login scripts were designed to be processed by the Novell Client on the user’s workstation, some of the defined statement types and script variables cannot be processed by NetStorage. -
Page 19: Additional Sources For Login Scripts Information
1.10 Additional Sources for Login Scripts Information Because login scripts have been used in multiple versions of Novell products over the past 10 years, there is a wealth of information about them available in other documentation. Here are a few sources to check for additional information: ®... - Page 20 This additional information, in conjunction with this manual, provides you the needed information to construct and troubleshoot login scripts. Novell Login Scripts Guide...
-
Page 21: Sample Login Scripts
Sample Login Scripts ® ® You can create login scripts from these sample login scripts using Novell iManager, ConsoleOne ® or NetWare Administrator. Using a sample login script can help eliminate syntax errors, reducing the time it takes you to create your login scripts. -
Page 22: Sample Profile Login Script
MAP O=SYS:DOC IF MEMBER OF “MANAGERS” THEN MAP *3:=VOL1:PROJECTS\REPORTS IMPORTANT: The Novell Client for Linux is designed to work with scripts that were written for the Windows Client, so if you already have Windows login scripts, Linux workstations logging in to the network will execute any part of the login script that is labeled IF OS=”WINNT”. -
Page 23: Sample User Login Script For Mapping Drives
The default login script executes the first time User object ADMIN logs in. It also executes for any users who do not have user login scripts. You can't modify the default login script because it is coded into the Novell LOGIN utility. Instead, you can create container, profile, or user login scripts. -
Page 24: Samples Of Login Script Commands
MAP K:=%HOME_DIRECTORY MAP DISPLAY OFF MAP INS F:=\\FILE_SERVER\SYS\LOGIN;H:=\\FILE_SERVER\SYS\LOGIN\;Y:=FILE_SERVER/SYS: MAP L:=\\FILE_SERVER\SYS\LOGIN\ MAP ROOT G:=FILE_SERVER/SYS: MAP ERRORS ON MAP DISPLAY OFF F:=FILE_SERVER/SYS: MAP DISPLAY OFF INS F:=FILE_SERVER/SYS: MAP DEL D: MAP L:=.FILE_SERVER_SYS.MYCOMPANY/LINUX MAP P:=.FILE_SERVER_SYS.MYCOMPANY:LINUX MAP Q:=.FILE_SERVER_SYS.MYCOMPANY:/LINUX MAP O:=X:=.CN=DATA.O=MYCOMPANY Novell Login Scripts Guide... -
Page 25: Identifier Variables Script Sample
2.5.3 Identifier Variables Script Sample The following is a sample of how identifier variables can be used in a script. For more information, on these variables, see Section 3.2, “Using Identifier Variables,” on page WRITE “DAY %DAY” WRITE “DAY OF WEEK %DAY_OF_WEEK”... -
Page 26: Display Script Sample
DISPLAY SYS:VOL1\LOGINSCRIPT.TXT DISPLAY SYS:/VOL1/LOGINSCRIPT.TXT DISPLAY /ETC/PAM.D/NWLOGIN DISPLAY .MYCOMPANY 2.5.5 Fdisplay Script Sample The following is a sample of how the FDISPLAY command can be used in a script. For more information, see Section 3.12, “FDISPLAY,” on page Novell Login Scripts Guide... -
Page 27: Include Script Sample
SET SERVER=”FILE_SERVER” FDISPLAY \\FILE_SERVER\SYS\VOL1\LOGINSCRIPT.TXT FDISPLAY \\%FILE_SERVER\SYS\VOL1\LOGINSCRIPT.TXT FDISPLAY FILE_SERVER\SYS:\VOL1\LOGINSCRIPT.TXT FDISPLAY %FILE_SERVER\SYS:\VOL1\LOGINSCRIPT.TXT FDISPLAY .MYCOMPANY 2.5.6 Include Script Sample The following is a sample of how the INCLUDE command can be used in a script. For more information, see Section 3.16, “INCLUDE,” on page SET SERVER=”FILE_SERVER”... - Page 28 Novell Login Scripts Guide...
-
Page 29: Login Script Commands And Variables
Login Script Commands and Variables This section lists login script commands alphabetically and by the type of tasks the commands perform. It also contains a list of identifier variables used in login scripts. Section 3.1, “Login Script Conventions,” on page 30 Section 3.2, “Using Identifier Variables,”... -
Page 30: Login Script Conventions
NOTE: Commands that work only on DOS or Windows 3.x workstations have not been included. These commands include CLS, COMSPEC, DOS VERIFY, MACHINE, NOSWAP, and SWAP. For ® information on using these commands, see the help file that accompanies the Novell Client DOS and Windows 3.x software. -
Page 31: Using Identifier Variables
(.). To map to a cluster-enabled volume, you would use the following syntax: N:=.eDirectory_object’s_fully_distinguished_name_including_context For example: MAP N:=.cluster2_vol1.xyz.provo.novell For more information on mapping, see Section 3.18, “MAP,” on page 3.2 Using Identifier Variables Many login script commands allow you to take advantage of identifier variables to make login scripts more efficient and flexible. - Page 32 Month number (01 through 12) MONTH_NAME Month name (January, February, etc.) NDAY_OF_WEEK Weekday number (1 through 7; 1=Sunday) SHORT_YEAR Last two digits of year (99, 00, 01) YEAR All four digits of year (1999, 2000, 2001) Novell Login Scripts Guide...
- Page 33 Category Identifier Variable Function DOS Environment variable Any DOS environment variable can be used in angle brackets. To use a DOS environment variable in MAP, COMSPEC, INCLUDE, DISPLAY, and FIRE PHASERS commands, add a percent sign (%) in front of the variable. Miscellaneous ACCESS_SERVER Shows whether the access server is functional...
-
Page 34: Login Parameters With %N Variables
Version of the workstation's DOS shell; supports NetWare 2 and NetWare 3 shells and NetWare 4 Requester for DOS. SHELL_VERSION The version of the Novell Client, as displayed in the property pages. Provides a more effective testing of the Novell Client version from the login script. -
Page 35: Login Scripts Commands By Task
Change the default drive while the login script is executing Section 3.10, “DRIVE,” on page 40 This is not available for Novell Client for Linux. Map drives and search drives to network directories or to map Section 3.18, “MAP,” on page 47... -
Page 36: Workstation Environment
Set a home server where the bindery login script is read from Section 3.24, “SCRIPT_SERVER,” on page 52 This is not available for Novell Client for Linux. Change the order in which %n variables are interpreted in the Section 3.27, “SHIFT,” on page 54 login script 3.3.3 Workstation Environment... -
Page 37: Other
Replace parameter with any parameters that must accompany the executable file. Example You can use Automatic Client Update (ACU) to update Novell Client software without having to physically visit each workstation and manually update the software. ACU uses a text file that can be called from the login script. To call this file from the login script for... - Page 38 If you do not have a search drive mapped to the directory where the program is located, include the path to that directory in the command. For example, if the program to run GroupWise is located in the APPS directory on drive G:, use the following command: @SYS:\APPS\GRPWISE Novell Login Scripts Guide...
-
Page 39: Attach
3.6 ATTACH Establishes a connection between a workstation and a NetWare server. If the server is not in the current tree, a bindery connection is made. In networks running NetWare 3 or earlier versions, use the ATTACH command to connect to multiple file servers. -
Page 40: Display
Use DRIVE to change the default drive while the login script is executing. NOTE: This is not fully functional for the Novell Client for Linux. If this command is not included in the login script, the default drive is set to the first network drive, which is often assigned to the user's home directory upon login. -
Page 41: Exit
Instead of specifying a drive letter such as F: or G:, you can use an asterisk followed by a number n to represent the nth network drive (for example, *3). This allows drive letters to reorder themselves automatically if previous drive mappings are deleted or added. Command Format DRIVE [drive |*n] Replace drive with a local or network drive letter, or replace n with a drive number. -
Page 42: Fire Or Fire Phasers
Use GOTO to execute a portion of the login script out of the regular sequence. Set BREAK ON in your login script before experimenting with GOTO loops so that you can break out of a login script if necessary. See Section 3.7, “BREAK,” on page Novell Login Scripts Guide... -
Page 43: If...then
IMPORTANT: Do not use GOTO to enter or exit a nested IF...THEN (page 43) statement. This usage causes problems for the program. Command Format GOTO label Use label to indicate where the login script should continue executing. In Windows, the label can take formats :label (colon before) or label: (colon after). When the colon comes before the label, any words may be used with the label. - Page 44 If you place the following command in a login script, the message Status report is due today appears when the user logs in on Monday and Have a nice day! on other days: IF DAY_OF_WEEK=”MONDAY” THEN WRITE “Status report is due today.” ELSE WRITE “Have a nice day!” Novell Login Scripts Guide...
-
Page 45: Include
The following lines mean “If the hour (on a 24-hour scale) is greater than or equal to 12, then write ‘afternoon'”: IF VALUE HOUR24>=”12” THEN WRITE “afternoon" The following command executes the CAPTURE utility on the fourth day of the week (Wednesday): IF NDAY_OF_WEEK=”4”... - Page 46 INCLUDE command to execute the entire SALES_PV login script as a part of the SALES_LA login script, as follows: 1. Create an alias for the SALES_PV Organizational Unit in the SALES_LA Organizational Unit. 2. Add this line to the SALES_LA Organizational Unit's login script: INCLUDE .SALES_PV_ALIAS.SALES.NOVELL_US Novell Login Scripts Guide...
-
Page 47: Lastlogintime
Command Format LASTLOGINTIME 3.18 MAP NOTE: This is not fully functional for the Novell Client for Linux. Use MAP to map drives and search drives to network directories or to map to eDirectory objects such as cluster-enabled volumes. If you use MAP to automate drive map assignments during execution of the login script, users don't need to map drives every time they log in. - Page 48 ERRORS ON|OFF determines whether MAP error messages are displayed when the user logs in. MAP ERROR OFF must be placed before MAP commands in the login script. The default setting is ON. This option is valid only in login scripts. Novell Login Scripts Guide...
-
Page 49: Map Command Differences On Linux
Replace parameter with one of the following: INS inserts a drive mapping between existing search mappings. This is not available on the Novell Client for Linux. DEL deletes a drive mapping, making that drive letter available for other mapping assignments. -
Page 50: Pause
To override the profile script assigned to a user, and to cause the user to execute a PROFILE script called team_profile, use the following command: PROFILE team_profile 3.22 REGREAD Use REGREAD to read values from the Windows registry through a Novell login script on Novell Clients 3.0x and 4.5 and higher for Windows. Command Format REGREAD “HIVE,KEY,VALUE"... -
Page 51: Remark
KEY is the path to the value. For example: Network\Novell\System Config\NetWare DOS Requester\Name Context. VALUE is the name of the value if you want to read (a value other than default); otherwise, leave it blank. Example REGREAD “HKLM,Network\Novell\System Config\NetWare DOS Requester\Name Context,0”... -
Page 52: Script_Server
TEMP. NOTE: In Linux, all of the SET commands are not persistent and only apply to the specific login session they are associated with, as is standard with Linux. Novell Login Scripts Guide... -
Page 53: Set_Time
Windows, or during an eDirectory-only login when the Clear current connections option is enabled and selected on the eDirectory tab of the Novell Login dialog box. In the absence of an explicit SET_TIME ON or SET_TIME OFF statement in the login script, the... -
Page 54: Shift
Rather than potentially cause a UAC elevation consent or credential prompt during login processing, the Novell Client simply attempts to synchronize time with the current Windows user permissions. If UAC is enabled, this attempt will likely be unsuccessful. - Page 55 Command Format SHIFT [n] Replace n with the number of places that you want the variable to shift. The default is SHIFT 1. Examples When Mary logs in, she wants to access her word processing program, change the way it is set up, and map a drive to her work directory called ACCNTS.
-
Page 56: Tree
CORP, add the following line to the login script: tree corp/.mrichard.acme;butterfly 3.29 WRITE Use WRITE to display messages on the workstation screen when a user logs in to the network. Text that you want to display must be enclosed in quotation marks (" "). Novell Login Scripts Guide... - Page 57 There are several ways to display variables in the text message. The way you enter the variable in the WRITE command determines the display format, as follows: If you type the identifier variable as shown, with no special punctuation, only the variable is displayed on the screen.
- Page 58 For example, either of the following lines displays Hello, Smith when user Bob Smith logs in: WRITE “Hello, “;LAST_NAME WRITE “Hello, %LAST_NAME” To make a beep sound occur while the phrase Good morning appears on the screen, add the following line to the login script: WRITE “Good %GREETING_TIME \7” Novell Login Scripts Guide...
-
Page 59: Troubleshooting Login Scripts
Troubleshooting Login Scripts Although login scripts are useful in setting up drive mappings, search mappings, the user's printing environment, and displaying important messages and other commands, they can sometimes be a source of frustration when they don’t work as expected. A majority of the problems that occur with login scripts are associated with mapping drives and capturing printers. -
Page 60: Turning Off The Maproot Function In Windows 2000/Xp
To log in to an additional NDS tree using a specific NMAS method, run loginw32.exe or right- click the Red N > Novell Login and log in to the additional NDS tree while specifying the required NMAS method on the NMAS page. -
Page 61: Losing Path Statements After Login
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. -
Page 62: Login Script Does Unexpected Things
The ATTACH command makes a bindery connection that causes any previous eDirectory connections to that server to be destroyed. Using CAPTURE with the Server parameter also causes a bindery attachment to occur. Novell Login Scripts Guide... -
Page 63: A Documentation Updates
Section 3.22, “REGREAD,” on page Updated Section 3.26, “SET_TIME,” on page Removed outdated TERM command from Chapter 3, “Login Script Commands and Variables,” on page A.3 December 23, 2005 Page design reformatted to comply with revised Novell documentation standards. Documentation Updates... - Page 64 Novell Login Scripts Guide...
Need help?
Do you have a question about the LOGIN SCRIPTS - 08-2008 and is the answer not in the manual?
Questions and answers
I just need a login code or name, How do I add one?
To add a login script in Novell LOGIN SCRIPTS - 08-2008, follow these steps:
1. Go to iManager.
2. Click Roles and Tasks > User > Modify User.
3. Enter the username and context, then click OK.
4. Click General > Login Script.
5. Type the desired login script commands in the login script text box.
You can include commands like:
- `WRITE "Hello"` – to display a message.
- `INCLUDE .ALIAS.CONTEXT` – to include another script.
- `LASTLOGINTIME` – to show the last login time.
Make sure the script matches your server names and directory paths.
This answer is automatically generated
I want to login but can't find out how. I need to add a password or ID
To log in using Novell login scripts:
1. If using the TREE command in the login script to log into an additional eDirectory (NDS) tree, note:
- You must use uppercase characters for the password. Lowercase passwords are not supported.
- If the TREE command fails, it will prompt for username and password but will not override NMAS login methods.
2. To log in using a specific NMAS method:
- Run loginw32.exe or
- Right-click the Red N > Novell Login
- Log in to the additional NDS tree and specify the NMAS method on the NMAS page.
3. To add or modify a password or ID in the login process, these are typically set in the user profile or passed during login, not directly written in the script. The script can reference variables like %LOGIN_NAME or use commands like TREE with credentials.
Note: Do not use lowercase passwords in the TREE command; they must be uppercase.
This answer is automatically generated