As part of the process of distributing the application, Novell® Application LauncherTM can launch a script engine to execute a "before distribution" script and an "after distribution" script (for details about the order of script execution, see Script Execution Order). This property page defines the script engine that you want Application Launcher to use and the scripts you want executed.
On Windows* NT*/2000/XP, distribution scripts are run in the secure system space, which means that users do not see any of the script commands or command results. Therefore, you should not include any commands that require or initiate user interaction. If you do so, the script halts at that point. For example, you would not want to include a command to run a program that requires user interaction because the program, which will run in secure system space, will never be displayed to the user. On Windows 98, distribution scripts are run in the user space (because there is no system space).
Run Before Distribution
Use this text window to enter any script commands you want executed before the
application is distributed. Do not use extended characters in the script; extended
characters are not supported.
Run After Distribution
Use this text window to enter any script commands you want executed after the
application is distributed. Do not use extended characters in the script; extended
characters are not supported.
If an error occurs with the Run After Distribution script, the distribution fails and the application does not launch. However, Application Launcher does not remove files, shortcuts, or registry settings that were distributed.
Script Engine Location
The script engine determines the script commands and scripting language you
need to use. If you do not define a script engine in the Script Engine Location
field, Application Launcher uses the Novell ClientTM
as the script engine (if the workstation has the Novell Client installed), which
means that you can use most Novell Client login
script commands.
If you want to use a script engine other than the Novell Client, specify the script engine that you want to use. The script engine must reside in a location that is always available to users, such as the local drives. The script engine can reside on a network server only if users can map a drive to the server (for example, through the Novell Client or the Client for Microsoft* Networks). If Application Launcher cannot find the script engine, it displays an error to the user and fails to distribute the application.
If you use the Windows command interpreter as the script engine, you must include the /C switch, as shown in the following examples:
The %*WINSYSDIR% and %*WINDIR% variables specify the Windows system directory, and the /C switch instructs the command interpreter to execute the script and then stop. If the /C switch is not used, the script will not complete.
Script File Extension
This applies only if you specified a script engine in the Script Engine Location
field.
When the application is distributed, Application Launcher creates temporary script files for the Run Before Distribution scripts and Run After Distribution scripts. These files are passed to the script engine, which then executes the script. You need to specify the file extension that the script engine requires for its script files.
ZENworks Desktop Management Online Documentation
A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk denotes a third-party trademark. For more information, see Legal Notices.