Setup.exe command line parameters

Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. Any additional feedback?

Note Depending on how you received the software for example, through Microsoft volume licensing , your use of the software may be subject to additional terms and conditions. Note For local installations, you must run Setup as an administrator. Note The relational server values support the additional terminating backslash formats backslash or two backslash characters for the path.

Important All failover cluster installation commands require an underlying Windows cluster. Note To add more nodes after the installation, use Add Node action. Note When you use a managed service account, virtual account, or a built-in account, you should not specify the corresponding password parameters.

Submit and view feedback for This product This page. View all page feedback. In this article. Required to indicate the installation workflow. Supported values: Install. Suppresses the privacy notice statement. By using this flag, you are agreeing with the privacy notice. Use this parameter to install the English version of SQL Server on a localized operating system when the installation media includes language packs for both English and the language corresponding to the operating system.

Specify whether SQL Server setup should discover and include product updates. The valid values are True and False or 1 and 0. By default, SQL Server setup will include updates that are found. Specify the location where SQL Server setup will obtain product updates. The valid values are "MU" to search Microsoft Update, a valid folder path, a relative path such as.

Specifies the ConfigurationFile to use. Has no effect in SQL Server In older versions this specifies the error reporting for SQL Server. Specifies the components to install. For more information, see Feature Parameters below.

Setup roles install SQL Server in a predetermined configuration. Specifies a nondefault installation directory for bit shared components. Supported only on a bit system. Specifies a nondefault value for an InstanceID. Specifies a SQL Server instance name. For more information, see Instance Configuration. Specifies the account for the engine service. Specifies the password for the engine service account. This parameter can be omitted when using a managed service account, virtual account, or built-in account.

Specifies the startup mode for the PolyBase engine service: Automatic default , Disabled, and Manual. Specifies a port range with at least 6 ports for PolyBase services. Use this option if you are configuring a PolyBase Scale-out computational group including the head node.

Supported values: True , False. Specifies the product key for the edition of SQL Server. If this parameter is not specified, Evaluation is used. Specifies that Setup runs in a quiet mode without any user interface. This is used for unattended installations. Specifies that Setup runs and shows progress through the UI, but does not accept any input or show any error messages. Specifies whether to present only the minimum number of dialog boxes during setup.

In older versions this specifies feature usage reporting for SQL Server. Supported values: Automatic Disabled Manual. Specifies the directory for Analysis Services backup files.

Specifies the collation setting for Analysis Services. Specifies the directory for Analysis Services configuration files. Specifies the directory for Analysis Services data files. Specifies the directory for Analysis Services log files. Specifies the server mode of the Analysis Services instance.

All values must be expressed in upper case. For more information about valid values, see Install Analysis Services. Specifies the password for the Analysis Services service.

Specifies the startup mode for the Analysis Services service. Specifies the directory for Analysis Services temporary files. Specifies a domain user account for running SharePoint Central Administration services and other essential services in a farm. Specifies a password for the farm account. Specifies a passphrase that is used to add additional application servers or Web front-end servers to a SharePoint farm.

Specifies a port used to connect to the SharePoint Central Administration web application. Specifies the data directory for SQL Server data files. Specifies the security mode for SQL Server. If this parameter is not supplied, then Windows-only authentication mode is supported.

Supported value: SQL. Specifies the directory for backup files. Specifies the collation settings for SQL Server. The default installation setting is determined by the operating system OS locale. The server-level collation can either be changed during setup, or by changing the OS locale before installation. The default collation is set to the oldest available version that is associated with each specific locale. This is due to backwards compatibility reasons.

Therefore, this is not always the recommended collation. To take full advantage of SQL Server features, change the default installation settings to use Windows collations. For more information, see Collations and Unicode support. Adds the current user to the SQL Server sysadmin fixed server role. Specifies the startup mode for the SQL Server service.

Project: Some of the command-line options apply to only certain project types. Project-specific information is listed for each option. This section describes valid command-line parameters for Setup. The parameters are organized into the following categories:. Silent Installations. If you configured the password-related settings for your release on the Setup. A typical command is as follows:. Basic MSI projects do not create or use a response file for silent installations.

Response files are created by running Setup. The command Setup. To run a Basic MSI installation silently, use the following command line:. To specify the values of public properties for a silent Basic MSI installation, you can use a command such as the following one:. Note: Using this command-line parameter to launch an installation that includes an InstallShield prerequisite does not automatically run the prerequisite installation silently.

You may also need to specify a valid silent command-line parameter for the InstallShield prerequisite in the Specify the command line for the application when the setup is running in silent mode setting on the Application to Run tab in the InstallShield Prerequisite Editor. Specify an absolute path; using a relative path gives unpredictable results.

Special Installation Modes. An administrative installation copies and uncompresses your data files to a directory that is specified by the user, but it does not create shortcuts, register COM servers, or create an uninstallation log. Tip: If an installation contains InstallShield prerequisites and you want to extract them from Setup.

A sample command is Setup. An advertised installation creates shortcuts, registers COM servers, and registers file types, but does not install your product's files until the user invokes one of these "entry points. Whenever you use this option and include a valid InstanceId value, the installation suppresses the instance selection dialog.

For example, the following sample command line installs the instance that has 2 as the value of the InstanceId property:. Use default to identify the instance that is installed by the base installation package, as in the following example:. Passing Data to the Installation. If you want to pass more than one argument to Msiexec.

For example:. To learn more, see Setup. This option specifies command-line parameters to be passed to the script. Note also that as with any public Windows Installer property, this property should be specified with all uppercase letters. Note: You must specify the full URL with the parameters.

In the Release Wizard, for a Web Downloader build, you can specify a download location for your. Note: You must specify the full URL with the parameter. In the Release Wizard, for a Downloader build, you can specify whether to cache the contents of a compressed package on the local system. For more information, see Windows Setup Automation Overview. The default value is , but can also be set to or If ei.

See Windows Setup Exit Codes below. This is not a change in Windows Setup support policy but instead a clarification:. This exported image must be named install. You must also remove install. You should only export to install. The exported image will be smaller, but will not be mountable. Remarks The bus , device , and function numbers must be in decimal format. Remarks If you include an option on the command line and the same option in the setupconfig file, the setupconfig file option and value has precedence.

Remarks By default, Windows Setup determines whether to use this feature automatically. This command works with other switches. To run Windows Setup in the background without any UI:. Remarks This option is available starting in Windows 10 and above. Remarks Accepted parameters are local file paths and UNC network paths. Execution runs in the system context, so it may not have permissions to copy to locations that require user permissions.

Specifies whether Windows Setup will perform Dynamic Update operations search, download, and install updates. Instructions Windows Setup to suppress the Windows Setup end user license agreement user experience. Remarks This option is new starting with Windows To learn more about licensing, see Microsoft License Terms.

Instructions Windows Setup to finish previously started update operations on the down-level OS, followed by an immediate reboot to start the offline phase. Remarks This option is new for Windows 10, version Instructions Windows Setup which OS image to install from install. Remarks If multiple images are applicable, Windows Setup will prompt the user to select. Remarks This option is new starting in Windows The driver. The command will recurse through the specified location.

This option also be used with split image files. Select the first split image file in the series. Remarks This enables you to use a single preinstallation environment to install multiple versions of Windows images. For example, you can use a bit version of Windows Setup to deploy a bit Windows image.

You can also use an answer file for cross-platform deployments. The command installs all lp. Language capabilities may have be dependent on other language capabilities.

For example, Text-to-speech is dependent on the Basic component of the same language. In Windows 10, version and later, install failures will cause Windows Setup to fail and rollback.

Instructs Windows Setup to copy alternate files from an alternate location. This option instructs Windows Setup to look in the alternate location first, and, if files are present, to use them instead of the files from the default location.

If you replace a file that Windows file protection protects, you must also copy the updated file to the local sources to be installed with Windows. The file name must be the same as the name that is used in Windows Setup.