InstallShield 静默安装 Command-Line Parameters

心已赠人 2023-10-02 13:15 9阅读 0赞

InstallShield setup.exe files can accept a number of command-line parameters. Using these parameters, administrators can specify details like where to install, if it should reboot the system, or what (if anything) should be displayed during installation.

Command-line options that require a parameter must be specified with no space between the option and its parameter. Quotation marks around an option's parameter are required only if the parameter contains spaces.

Several of the command-line options apply only to MSI projects or InstallScript projects.

What is the difference? InstallScript MSI setups are Windows Installer setups driven by InstallScript, whereas InstallScript setups are written purely in InstallShield Script. This is often revered to as a “legacy setup”.

Setup.exe accepts the following command-line parameters regardless of if it is an InstallScript or InstallScript MSI project.

<table style="margin-left:-2.75pt;width:495.05pt;"> 
 <tbody> 
 <tr> 
 <td style="border-color:#000000;vertical-align:top;width:92.7pt;"> Parameter </td> 
 <td style="border-color:#000000;vertical-align:top;width:216pt;"> Action </td> 
 <td style="border-color:#000000;vertical-align:top;width:81pt;"> InstallScript Supported? </td> 
 <td style="border-color:#000000;vertical-align:top;width:105.3pt;"> InstallScript MSI Supported? </td> 
 </tr> 
 <tr> 
 <td style="border-color:#000000;vertical-align:top;width:92.7pt;"> /uninst </td> 
 <td style="vertical-align:top;width:216pt;"> Uninstalls the product </td> 
 <td style="vertical-align:top;width:81pt;"> n </td> 
 <td style="vertical-align:top;width:105.3pt;"> n </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /uninst </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;border-color:#000000;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td style="border-color:#000000;vertical-align:top;width:92.7pt;"> /removeonly </td> 
 <td style="vertical-align:top;width:216pt;"> Also uninstalls the product, but depending upon how authored it may display the welcome/maintenance dialog </td> 
 <td style="width:81pt;"> n </td> 
 <td style="width:105.3pt;"> n </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /removeonly </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;border-color:#000000;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td style="border-color:#000000;vertical-align:top;width:92.7pt;"> /r </td> 
 <td style="vertical-align:top;width:216pt;"> Record the installation to create an ISS answer file which may be used in a silent installation command </td> 
 <td style="width:81pt;"> n </td> 
 <td style="width:105.3pt;"> n </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /r </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /r /f1”c:\temp\my-answer-file.iss” </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;border-color:#000000;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="border-color:#000000;vertical-align:top;width:308.7pt;"> /s Run the setup silently using a previously created ISS answer file (with the /r parameter). </td> 
 <td style="width:81pt;"> n </td> 
 <td style="width:105.3pt;"> n </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /s </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /s /SMS </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /s /f1”c:\temp\my-answer-file.iss” </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /s /f1”c:\temp\my-answer-file.iss” /f2”c:\temp\my-log-file.iss” </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;border-color:#000000;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 </tbody> 
</table>

<table style="margin-left:-2.75pt;width:495.05pt;"> 
 <tbody> 
 <tr> 
 <td style="border-color:#000000;vertical-align:top;width:92.7pt;"> /f1 </td> 
 <td style="border-color:#000000;vertical-align:top;width:216pt;"> Specifies an alternative response file name and path; by default /s will look for setup.iss in the same directory as the setup executable and /r will create setup.iss in the Windows directory (%windir%). </td> 
 <td style="border-color:#000000;width:81pt;"> n </td> 
 <td style="border-color:#000000;width:105.3pt;"> n </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /r /f1”c:\temp\my-answer-file.iss” </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /s /f1”c:\temp\my-answer-file.iss” </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;border-color:#000000;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td style="border-color:#000000;vertical-align:top;width:92.7pt;"> /f2 </td> 
 <td style="vertical-align:top;width:216pt;"> Specifies an alternative log file name and path; by default the log file will be created in the same directory as the setup executable with the name setup.log. </td> 
 <td style="width:81pt;"> n </td> 
 <td style="width:105.3pt;"> n </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /s /f2”c:\temp\my-log-file.iss” </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /s /f1”c:\temp\my-answer-file.iss” /f2”c:\temp\my-log-file.iss” </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;border-color:#000000;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td style="border-color:#000000;vertical-align:top;width:92.7pt;"> /SMS </td> 
 <td style="vertical-align:top;width:216pt;"> Instructs a silent setup not to release the current session until the installation is complete. Without this switch a silent installation will immediately appear complete and run in the background. Use this switch to have any additional installations or script actions wait for installation to complete (such as in a batch file). The parameter was introduced to support MS Systems Management Server which would temporarily map a drive during installation to access source files (where it would immediately complete, and SMS would unmap the drive to the source files before the installation was complete.) </td> 
 <td style="width:81pt;"> n </td> 
 <td style="width:105.3pt;"> n </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /s /SMS </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /s /SMS /f1”c:\temp\my-answer-file.iss” </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /s /SMS /f1”c:\temp\my-answer-file.iss” /f2”c:\temp\my-log-file.iss” </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;border-color:#000000;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="border-color:#000000;vertical-align:top;width:308.7pt;"> /m Generate a .MIF file (used by SMS and some other management solutions to report status information). </td> 
 <td style="width:81pt;"> n </td> 
 <td style="width:105.3pt;"> n </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /m”MyMIF” </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;border-color:#000000;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td style="border-color:#000000;vertical-align:top;width:92.7pt;"> /m1 </td> 
 <td style="vertical-align:top;width:216pt;"> Specifies the serial number to be written to a .MIF file (used with /m parameter) </td> 
 <td style="vertical-align:top;width:81pt;"> n </td> 
 <td style="vertical-align:top;width:105.3pt;"> n </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /m”MyMIF” /m1”1111-2222-“ </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /m”MyMIF” /m1”1111-2222-“ /m2”ENU” </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;border-color:#000000;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td style="border-color:#000000;vertical-align:top;width:92.7pt;"> /m2 </td> 
 <td style="vertical-align:top;width:216pt;"> Specifies the locale string to be written to a .MIF file (used with /m parameter) </td> 
 <td style="vertical-align:top;width:81pt;"> n </td> 
 <td style="vertical-align:top;width:105.3pt;"> n </td> 
 </tr> 
 </tbody> 
</table>

<table style="margin-left:-2.75pt;width:495.05pt;"> 
 <tbody> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;border-color:#000000;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /m”MyMIF” /m2”ENU” </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /m”MyMIF” /m1”1111-2222-“ /m2”ENU” </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;border-color:#000000;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td style="border-color:#000000;vertical-align:top;width:92.7pt;"> /d </td> 
 <td style="vertical-align:top;width:216pt;"> Debug InstallScript portion of the setup with the InstallScript debugger (ISDbg.exe). This is intended for setup authors to troubleshoot a setup and not for admins- the action requires a setup.dbg file to be available. </td> 
 <td style="width:81pt;"> n </td> 
 <td style="width:105.3pt;"> n </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /d”&lt;path to folder containing setup.dbg&gt;” </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /v"ISSCRIPTDEBUG=1 ISSCRIPTDEBUGPATH=\"&lt;path to folder containing </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> setup.dbg&gt;\"" </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;border-color:#000000;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td style="border-color:#000000;vertical-align:top;width:92.7pt;"> /f </td> 
 <td style="vertical-align:top;width:216pt;"> Specify alternative compiled script. Setup.exe looks for a compiled script file named Setup.inx, this parameter may be used to specify a different name for the compiled script file. Note that in earlier versions of InstallShield (InstallShield - Windows Installer Edition), this parameter served to initiate a repair of the installation. </td> 
 <td style="width:81pt;"> n </td> 
 <td style="width:105.3pt;"> n </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /f”AlternateSetup.inx” </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;border-color:#000000;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td style="border-color:#000000;vertical-align:top;width:92.7pt;"> /L </td> 
 <td style="vertical-align:top;width:216pt;"> Specifies the language for the setup for those setups that support multiple languages. Language must be identified by decimal (LCID). </td> 
 <td style="width:81pt;"> n </td> 
 <td style="width:105.3pt;"> n </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /L1031 </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /L0007 </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;border-color:#000000;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="border-color:#000000;vertical-align:top;width:308.7pt;"> /delayedstart Delay initialization of the installation. With this parameter, specify the amount of time (in seconds) by which initialization of the installation is to be delayed after Setup.exe is launched. </td> 
 <td style="width:81pt;"> n </td> 
 <td style="width:105.3pt;"> o </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /delayedstart:10 </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;width:495.05pt;"> Setup.exe /s /delayedstart:900 </td> 
 </tr> 
 <tr> 
 <td colspan="4" style="background-color:#f3f3f3;border-color:#000000;width:495.05pt;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td style="border-color:#000000;vertical-align:top;width:92.7pt;"> /deleter </td> 
 <td style="vertical-align:top;width:216pt;"> Do not clone a second Setup.exe process when debugging. By default, Setup.exe clones a second process so that it properly uninstalls applications from machines on which no InstallScript installation had previously been run. Use this option when debugging a DLL function that is called from your own authored installation script. </td> 
 <td style="width:81pt;"> n </td> 
 <td style="width:105.3pt;"> o </td> 
 </tr> 
 </tbody> 
</table>

<table style="margin-left:-2.75pt;width:495.05pt;"> 
 <tbody> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> Setup.exe /uninst </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td style="border-color:#000000;vertical-align:top;width:92.7pt;"> /p:&lt;password&gt; </td> 
 <td style="vertical-align:top;width:216pt;"> For a password protected setup, this option may be used to supply the password at the command line (normally in support of a silent installation). </td> 
 <td style="width:81pt;"> X </td> 
 <td style="width:105.3pt;"> X </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> Setup.exe /uninst </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="border-color:#000000;vertical-align:top;width:308.7pt;"> /s Install silently. By default the silent installation is based on the response file called Setup.iss in the same directory. (Response files are created by running Setup.exe with the /r option.) To specify an alternative file name or location of the response file, use the /f1 parameter. </td> 
 <td style="width:81pt;"> X </td> 
 <td style="width:105.3pt;"> X </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> Setup.exe /uninst </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td style="border-color:#000000;vertical-align:top;width:92.7pt;"> /ua:&lt;URL to InstMsiA.exe&gt;&nbsp; &nbsp; </td> 
 <td style="vertical-align:top;width:216pt;"> If download locations are specified in the setup, those paths may be overridden using this parameter. Note that only the path is required. </td> 
 <td style="width:81pt;"> o </td> 
 <td style="width:105.3pt;"> X </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> Setup.exe /uninst </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td style="border-color:#000000;vertical-align:top;width:92.7pt;"> /uw:&lt;URL to InstMsiW.exe&gt; </td> 
 <td style="vertical-align:top;width:216pt;"> If download locations are specified in the setup, those paths may be overridden using this parameter. Note that only the path is required. </td> 
 <td style="width:81pt;"> &nbsp; </td> 
 <td style="width:105.3pt;"> X </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> Setup.exe /uninst </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td style="border-color:#000000;vertical-align:top;width:92.7pt;"> /us:&lt;URL to ISScript.msi&gt; </td> 
 <td style="vertical-align:top;width:216pt;"> If download locations are specified in the setup, those paths may be overridden using this parameter. Note that only the path is required. </td> 
 <td style="width:81pt;"> &nbsp; </td> 
 <td style="width:105.3pt;"> X </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> Setup.exe /uninst </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td style="border-color:#000000;vertical-align:top;width:92.7pt;"> /um:&lt;URL to .MSI package&gt; </td> 
 <td style="vertical-align:top;width:216pt;"> If download locations are specified in the setup, those paths may be overridden using this parameter. Note that only the path is required. </td> 
 <td style="width:81pt;"> &nbsp; </td> 
 <td style="width:105.3pt;"> X </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> Setup.exe /uninst </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="border-color:#000000;vertical-align:top;width:308.7pt;"> /b&lt;local If a path to locally cache setup files is directory&gt; specified, this path may be overridden using this parameter.&nbsp; </td> 
 <td style="width:81pt;"> &nbsp; </td> 
 <td style="width:105.3pt;"> X </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> Setup.exe /uninst </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td style="background-color:#f3f3f3;width:81pt;"> </td> 
 <td style="background-color:#f3f3f3;width:105.3pt;"> </td> 
 </tr> 
 <tr> 
 <td style="border-color:#000000;vertical-align:top;width:92.7pt;"> /v:&lt;MSIEXEC parameters&gt; </td> 
 <td style="vertical-align:top;width:216pt;"> Pass command-line options and values of public properties through to Msiexec.exe. </td> 
 <td style="width:81pt;"> &nbsp; </td> 
 <td style="width:105.3pt;"> X </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td colspan="2" style="background-color:#f3f3f3;width:186.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> Setup.exe /uninst </td> 
 <td colspan="2" style="background-color:#f3f3f3;width:186.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td colspan="2" style="background-color:#f3f3f3;width:186.3pt;"> </td> 
 </tr> 
 <tr> 
 <td style="border-color:#000000;vertical-align:top;width:92.7pt;"> /w </td> 
 <td style="vertical-align:top;width:216pt;"> Forces Setup.exe to wait until the installation is complete before exiting (similar to /SMS). </td> 
 <td style="width:81pt;"> &nbsp; </td> 
 <td style="width:105.3pt;"> X </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td colspan="2" style="background-color:#f3f3f3;width:186.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> Setup.exe /uninst </td> 
 <td colspan="2" style="background-color:#f3f3f3;width:186.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td colspan="2" style="background-color:#f3f3f3;width:186.3pt;"> </td> 
 </tr> 
 <tr> 
 <td style="border-color:#000000;vertical-align:top;width:92.7pt;"> /h </td> 
 <td style="vertical-align:top;width:216pt;"> By default, the build engine automatically creates an installation that supports Setup.exe cloning in cases where cloning is required (such as in multi-disk installations). Specifiy this parameter to have Setup.exe clone itself to a temporary location and run from that location. </td> 
 <td style="width:81pt;"> &nbsp; </td> 
 <td style="width:105.3pt;"> X </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td colspan="2" style="background-color:#f3f3f3;width:186.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> Setup.exe /uninst </td> 
 <td colspan="2" style="background-color:#f3f3f3;width:186.3pt;"> </td> 
 </tr> 
 <tr> 
 <td colspan="2" style="background-color:#f3f3f3;width:308.7pt;"> &nbsp; </td> 
 <td colspan="2" style="background-color:#f3f3f3;width:186.3pt;"> </td> 
 </tr> 
 </tbody> 
</table>

<table style="margin-left:-2.25pt;width:434.2pt;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;width:18pt;"> </td> 
 <td style="vertical-align:top;width:416.2pt;"> for the setup.exe call by creating a transform (MST) file </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:18pt;">  </td> 
 <td style="vertical-align:top;width:416.2pt;"> Tricking the MSI into thinking it is being called by the setup.exe using the ISSETUPDRIVEN property </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;width:18pt;">  </td> 
 <td style="vertical-align:top;width:416.2pt;"> Using the InstallScript Scan feature of AdminStudio to migrate the InstallScript to native Windows Installer (so InstallScript might be removed as a dependency) </td> 
 </tr> 
 </tbody> 
</table>

![watermark_type_ZHJvaWRzYW5zZmFsbGJhY2s_shadow_50_text_Q1NETiBAYWxsd2F5Mg_size_12_color_FFFFFF_t_70_g_se_x_16][]For more on how to work with InstallScript setups, see “Dealing with InstallScript for Administrators” in the AppDeploy Library (www.appdeploy.com/library). In this video presentation you will learn what InstallScript is, why it is still used and other general information on the topic before explaining the three ways of avoiding the need for running the setup from the provided setup.exe. Including video demonstrations of each:

 Removing the custom action that checks

[watermark_type_ZHJvaWRzYW5zZmFsbGJhY2s_shadow_50_text_Q1NETiBAYWxsd2F5Mg_size_12_color_FFFFFF_t_70_g_se_x_16]: https://img-blog.csdnimg.cn/c7e34d98b62c4071bd745e4bf720e682.png?x-oss-process=image/watermark,type_ZHJvaWRzYW5zZmFsbGJhY2s,shadow_50,text_Q1NETiBAYWxsd2F5Mg==,size_12,color_FFFFFF,t_70,g_se,x_16