User manual NOVELL LOGIN SCRIPTS 08-2008

[. . . ] novdocx (en) 24 March 2009 AUTHORIZED DOCUMENTATION Login Scripts Guide Novell® Login Scripts August 2008 www. novell. com Novell Login Scripts Guide novdocx (en) 24 March 2009 Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. [. . . ] Otherwise, the login script remains open until that external program is closed. (Login scripts cannot be edited while they are open. ) Command Format # [path] filename [parameter] Replace path with a drive letter (Windows) or a valid path name (Linux) or, if you have specified NOSWAP on the command line or in the login script, you can replace variable with a full directory path beginning with the NetWare volume name. Replace filename with an executable file (files that end in . exe, . com, or . bat, for example). It isn't necessary to include the extension, but doing so can speed up the execution of the external program. 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 a workstation running Novell Client for Windows NT/2000, place one of the following commands in the login script: #Z:\PUBLIC\INSTALL\NTCLIENT\SETUPNW. EXE /ACU Login Script Commands and Variables 37 novdocx (en) 24 March 2009 or #\\[SERVER]\[VOLUME]\PUBLIC\INSTALL\NTCLIENT\SETUPNW. EXE /ACU 3. 5 @ Use the @ command to execute a program that is external to the login script and then continue with the script (similar to the Startup group). Enter the @ command followed by the name of the file that you want to execute. IMPORTANT: Use the @ command instead of the # command to run an external program from a login script if that external program will remain open for any length of time. Otherwise, the login script remains open until that external program is closed. (Login scripts cannot be edited while they are open. ) This command fails when The given directory is invalid. Insufficient workstation memory is available to load the file. Command Format @ [path] filename [parameter] Replace path with a drive letter (Windows) or a valid path name (Linux). Replace filename with an executable file (files that end in . exe, . com, or . bat, for example). Replace parameter with any parameters that must accompany the executable file. Examples If you want to start the GroupWise® program from within the login script, you must have a search drive mapped to where the GroupWise application is stored. Enter the following command in the login script: @GRPWISE You do not need to enter a path in this case, because the executable program file for GroupWise (grpwise. exe) is located in a search drive. 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 38 Novell Login Scripts Guide novdocx (en) 24 March 2009 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. [. . . ] To troubleshoot this problem, make sure the COMSPEC is set. Then, make sure login. exe is being swapped out correctly. 4. 5. 4 LOGIN. EXE Problems Because the language-enabled login. exe is so large, it must be swapped out before large executables can run. capture. exe is a good example of an external program frequently called in a login script. By default, login. exe tries to swap to extended memory first, then to expanded memory, and then to the current drive. [. . . ]