Uninstall Scripts

Windows NT 4 Info

As part of the process of uninstalling the application, Novell^® Application Launcher^TM can launch a script engine to execute a "before uninstall" script and an "after uninstall" script. 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, uninstall scripts always run in the user space for both user-associated applications and workstation-associated applications. This is the same behavior as launch scripts (Run Options tab > Launch Scripts) but different than the behavior for distribution scripts (Distribution Options tab > Distribution Scripts), which run in the secure system space.

Run Before Uninstalling
Use this text window to enter any script commands you want executed before the application is uninstalled. Do not use extended characters in the script; extended characters are not supported.

Run After Uninstalling
Use this text window to enter any script commands you want executed after the application is uninstalled. Do not use extended characters in the script; extended characters are not supported.

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 Client^TM 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 uninstall 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:

Windows NT/2000/XP: %*WINSYSDIR%\CMD.EXE /C
Windows 98: %*WINDIR%\COMMAND.COM /C

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 uninstalled, Application Launcher creates temporary script files for the Run Before Uninstall scripts and Run After Uninstall 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.