As part of the process of launching the application, Novell® Application LauncherTM can run a script engine to execute a "before launch" script and an "after termination" 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, launch scripts always run in the user space, meaning that they inherit the file system rights assigned to the logged-in user. This is true even if the application's executable is configured to run in the system space (Run Options tab > Environment page > Executable Security Level option). This behavior is different than the behavior for distribution scripts (Distribution Options tab > Distribution Scripts page), which run in the secure system space.
Run Before Launching
Use this text window to enter any script commands you want executed before launching
the application. Do not use extended characters in the script; extended characters
are not supported.
Run After Termination
Use this text window to enter any script commands you want executed after the
user closes the application. Do not use extended characters in the script; extended
characters are not supported.
IMPORTANT: The Run After Termination script is executed before the network resources are cleaned up (Run Options > Environment page). However, the Clean Up Network Resources option does not clean up drive mappings or port captures created by the Run Before Launching script. To clean up these resources, enter the appropriate commands in the Run After Termination script.
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 their 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 does not complete.
Script File Extension
This applies only if you specified a script engine in the Script Engine Location
field.
When the application is launched, 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 information on trademarks, see Legal Notices.