Windows¶
This page provides download files and instructions for installing Salt on Windows.
Windows downloads¶
3006 LTS Downloads¶
Arch |
File type |
Salt Release Type |
Download install file |
---|---|---|---|
AMD64 |
exe |
LTS |
|
AMD64 |
msi |
LTS |
|
x86 |
exe |
LTS |
|
x86 |
msi |
LTS |
3007 STS Downloads¶
Arch |
File type |
Salt Release Type |
Download install file |
---|---|---|---|
AMD64 |
exe |
STS |
|
AMD64 |
msi |
STS |
|
x86 |
exe |
STS |
|
x86 |
msi |
STS |
Important information about installing on Windows¶
Windows has two installer options:
A Nullsoft (.exe) installer
An MSI (.msi) installer
If you are unsure which installer to use, use the Nullsoft (EXE) installer.
Onedir packages are currently only available for the Nullsoft (EXE) installer.
Install directory locations¶
In versions of Salt prior to Salt 3004, Nullsoft (EXE) Windows installer only
installed Salt in the root C drive directory: C:\Salt
.
In versions 3004 and later, the Nullsoft (EXE) installer defaults to installing
Salt in the C:\Program Files\Salt Project\Salt
directory path. The install
directory stores Salt binary data. If you choose a custom install directory
path, Salt registers that directory as the install_dir
.
Note
You can choose a custom install directory path from the command line using
the /install-dir
option. See Windows Nullsoft EXE install options
for more information.
Also in versions 3004 and later, the Nullsoft (EXE) installer creates a second
directory in C:\ProgramData\Salt Project\Salt
called the config directory.
The config directory is where Salt stores non-binary data such as configuration
files, logs, and the cache. This path cannot be customized. Salt registers that
directory as the root_dir
.
By default, the installer will not move configuration data that is stored in
the old C:\Salt
directory for older installations. However, the installer
can move an older, existing Salt configuration directory from the old location
to ProgramData
by passing the /move-config
option on the command line.
Additionally, if the installer detects an existing config in the old location,
the user interface displays a checkbox with the option to move the root_dir
to ProgramData
.
Before you start¶
Before installing Salt on your operating system, ensure that you first:
Install Salt on Windows¶
To install Salt on Windows:
Download the Salt installation file for Windows. See Windows downloads for a list of the latest downloads.
Run the file to install Salt with a graphical user interface.
You can optionally run the file from the command line. One advantage of running the file from the command line is that you can add various options for a custom installation. See Windows Nullsoft EXE install options or Windows MSI install options for more information.
The following is an example of running a silent installation from the command line:
Salt-Minion-3006.9-Py3-AMD64-Setup.exe /S /master=yoursaltmaster /minion-name=yourminionname
See Windows Nullsoft EXE install options for more information about options and additional examples.
msiexec /i Salt-Minion-3006.9-Py3-AMD64.msi /quiet /norestart MASTER=yoursaltmaster MINION_ID=yourminionname
See Windows MSI install options for more information about options.
Salt install directory
See Install directory locations for information about where Salt is installed by default and how you can customize that setting.
After installing Salt on your operating system, you need to complete the following post-installation steps:
Windows Nullsoft EXE install options¶
The most commonly used install options are:
/master
/minion-name
/S
Option |
Description |
Example input |
---|---|---|
|
Displays this help screen with the install option documentation. |
|
|
Pass in a string specifying the name of a custom configuration file. The file path must be in the same path as the installer or it should be the full path. If Any existing configuration files will be backed up by appending a timestamp
and a |
|
|
If any existing configuration files are present, this option will overwrite the existing configuration and replace it with the default Salt configuration file. The default is to use the existing configuration file if present. If
Any existing configuration files will be backed up by appending a
timestamp and a |
|
|
Specify the installation location for the Salt binaries. This option will be ignored for existing installations. See Install directory locations for information about where Salt is installed by default and how you can customize that setting. |
|
|
If a configuration file is found at |
|
|
Sets the master name or IP address. You may pass a single master or a comma-separated list of masters. Setting the master will cause the installer to use the default config or a custom config if provided. If no master is specified, the default value is Be aware that you can only use a master name if you have set up your DNS
server to resolve the master’s name to its IP address. For example, you
would need to set up |
|
|
Sets the minion name. If no minion ID is specified, the default will be
|
|
|
If you set the value to 1, the installer will start the minion service after installation. If set to, it 0 will not. The default is 1. |
|
|
Use this option to install Salt silently. |
|
|
Use this option to set the minion service to start after installation, but
to delay for 30-60 seconds, depending on the operating system settings. If
you use this option, the minion start type will be set to
|
|
Windows MSI install options¶
The most commonly used install options are:
MASTER
MINION_ID
/quiet
/norestart
Note
For more information about options for the MSI installer, see the readme https://github.com/saltstack/salt/blob/master/pkg/windows/readme.md.
The following table describes all available options, listed alphabetically:
Option |
Description |
Example values |
---|---|---|
|
Set to |
|
|
Set to |
|
|
Set to |
|
|
This option is only available from the command line and must be used along
with the Pass in the name of a custom configuration file. The file path must either be in the same path as the installer or it should be the full path. |
|
|
Use this option to install the binaries to a custom directory path. The
default value is |
|
|
Sets the master name or IP address. You may pass a single master or a comma-separated list of masters. If no master is specified, the default value is Be aware that you can only use a master name if you have set
up your DNS server to resolve the master’s name to its IP address. For
example, you would need to set up |
|
|
Sets the master public key. To use this option, first convert the public
key converted into one line by removing the first and last line:
|
Generally, most public keys start with |
|
Sets the content that will write to the minion configuration file. If you use this option, it operates the same as
|
master: Anna
id: Bob
|
|
Sets the minion name. If no minion ID is specified, the default will be the hostname or IP address. |
|
|
If a configuration file is found at |
|
|
Runs the installer silently. Usually used along with |
|
|
Runs the installer silently. Usually used along with |
|
|
Runs the installer silently, but displays a progress bar. Usually used
along with |
|
|
Set to |
|
|
Use this option to install the configuration files to a custom directory
path. The default value is |
|
|
Starts the minion service after installation. Set this value to In PowerShell, you must escape the quotes (`”`”) |
|
MSI installation scenarios¶
The CONFIG_TYPE
option can support three possible installation scenarios.
Existing¶
The Existing setting is recommended for simple upgrades. It makes no changes to the existing configuration and only upgrades Salt. For this type of installation, run the installer with a silent option. If there is no existing configuration, the installer creates a default configuration. The master and minion ID are applied if they are passed.
Custom¶
The Custom setting will apply a custom configuration file passed from the command line. To ensure the custom configuration is applied correctly, the installer backs up any existing configurations following this order of operations:
The minion configuration file is renamed to
minion-<timestamp>.bak
.The
minion_id
file is renamed tominion_id-<timestamp>.bak
.The
minion.d
directory renamed tominion.d-<timestamp>.bak
The custom config is applied by the installer. If the master and minion ID were passed, they will be to the custom configuration file.
Default¶
This setting will reset the configurations to the default configurations contained in the package. Therefore, all existing config files should be backed up first, including:
The minion configuration file
The
minion_id
fileThe
minion.d
directory
Warning
The MSI installer has a known issue that impacts installers with the -X
in the file name, such as 3005.1-4. When upgrading these builds, the
installer creates duplicate entries in Add/Remove Programs. For example, if
you have 3005.1-1 installed and you use the MSI to upgrade to 3005.1-4, the
upgrade will complete successfully, but both versions appear in Add/Remove
Programs.
The workaround when upgrading between these types of builds using the MSI is to uninstall the old version prior to installing the new version.
Upgrades to and from versions without the -X
will work as expected.
Browse the repo¶
Windows