Client Management Suite

 View Only

WiseScript Command Line Options 

Jan 02, 2009 10:39 AM

You can apply the following command line options to the WSE file. Command line options let you compile as well as set properties.

  • /c file.wse
    Compiles the installation script.
  • /c /s file.wse
    Compiles the installation script silently. You can use this option with the /d option.

WiseScript Installations Command Line Options

You can apply the following command line options to compiled .EXE files.

  • /M
    Runs the installation in manual mode, prompting for system directories (examples: Windows, System).
  • /M=filename
    Specifies a value file for installation.
  • /S
    Installs in silent (automatic) mode with no end user choices.

Uninstall Command Line Options

You can apply the following command line options to the WiseScript Express uninstall executable file, unwise.exe or unwise32.exe.

  • /Z
    Removes empty directories, including the one containing Unwise.
  • /A
    Automatic mode. The Wise splash screen appears on the destination computer, and the uninstall proceeds immediately with no end user choices, except for questions about uninstalling shared files.
  • /S
    Silent mode. The uninstall proceeds silently with no splash screen, no dialogs, and no end user choices.
  • /R
    Rollback mode.
  • /U
    Removes the Select Uninstall Method dialog, which means the end user does not see options for a custom, automatic, or repair uninstall.

When you use command line options for the uninstall program, you must send it the path to the log file as a parameter. It must be the log file that is in the same folder as unwise.exe. If the path to the log file contains spaces, it must be surrounded by quotation marks.

Example: "C:\Program Files\Application\UNWISE.EXE" /A "C:\Program Files\Application\INSTALL.LOG" Application Uninstall

0 Favorited
1 Files
jpg file
6770.jpg   3 KB   1 version
Uploaded - Apr 10, 2020

Tags and Keywords


Jan 03, 2009 11:35 PM

Its great to have all the parameters for Wise Script listed here. Great Job..
I have a small suggestion (after looking at the example) here would be, to use Wisescripts only for stacking registries, making user level changes, making clean un-installtions etc.. but do not use unwise.exe as a Custom action in the package, this does not check for the dependency/shared counts of the dlls.
Moreover, this file should be removed from the MSI we handle un-installation using Windows Installer concepts.

Related Entries and Links

No Related Resource entered.