Run the SolarWinds Installer in silent mode
Run the SolarWinds Installer in silent mode, without displaying the user interface. Adjust the configuration file, and run the installer with the /s parameter.
This article applies to SolarWinds Platform products installed with the SolarWinds Installer.
Before you begin
Silent mode means that the installer runs silently, without displaying the user interface.
If you have deployed scalability engines (additional web servers, additional polling engines, or high availability backup servers), upgrade your main SolarWinds Platform server first, and then upgrade your scalability engines.
You can upgrade your product using a properly configured config file.
Centralized Upgrades are available. As long as your scalability engines are reachable, the installer can upgrade all scalability engines from your SolarWinds Platform server in parallel. Upgrade your main SolarWinds Platform server first. If the installer encounters issues with a scalability engine, it will not upgrade that engine but will continue the process and upgrade as many scalability engines as possible. A scalability engine is not upgraded if:
- The scalability engine is unreachable
- The preflight check discovers an issue that blocks the upgrade
Before you run the scripts, make sure the SQL Server is installed and accessible from the server where the software is installed.
The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.
Known limitations
- You cannot specify proxy settings in the silent installation mode.
- You cannot change the installation language in silent mode. When installed using the silent mode, your SolarWinds Platform Web Console is in English.
- You cannot run the SolarWinds Installer with enabled Windows Defender in silent mode. Windows Defender causes the Configuration Wizard to fail.
Installation overview
To install SolarWinds Platform products in the unattended mode, complete the following steps:
- Adjust the configuration file.
- Run the silent installation commands to install SolarWinds Platform products or scalability engines.
- If you have deployed scalability engines, run the silent installation command to upgrade existing scalability engines.
Step 1: Adjust the configuration file
2024.1
You can generate the configuration file for the silent run by launching the Configuration wizard with a specific parameter. The Configuration wizard collects the custom settings and generates a new SilentConfig.xml
file usable for running the Configuration wizard in silent mode.
-
Launch the Configuration wizard with the
-CreateSilentConfig
parameter and specify the PATH to save theSilentConfig.xml
file in the-cfgOutput
parameter.Replace the entries in bold red with your data and run the following commands from a command prompt on the main SolarWinds Platform server. The
SilentConfig.xml
file will be stored in the location you specified.cd SW-INSTALL-FOLDER, such as "C:\Program Files (x86)\SolarWinds\Orion" ConfigurationWizard.exe -CreateSilentConfig -cfgOutput:PATH
-
Adjust the config file if necessary.
2023.4.2 and earlier
- Review the following configuration examples (XML).
- Copy the example that suits your environment and save it.
- Adjust the file as needed.
Parameters
- Parameters for installing SolarWinds Platform products
- Parameters for running the Configuration wizard
- Parameters for installing a scalability engine
Parameters for installing SolarWinds Platform products
The following parameters can be specified in the <InstallerConfiguration>
section. Additional parameters can be found in the examples below.
To install EOC, you must download the EOC installer, which is the SolarWinds installer renamed to include -EOC at the end of the file name. The silent installer automatically selects EOC during the installation.
Parameters | Values | Description |
---|---|---|
<InstallPath>
|
Example: C:\OrionSetup |
Specify where you want to install SolarWinds Platform products. When upgrading, the installation path is reused from the existing installation, and this parameter does not have any effect. |
<AdvancedInstallMode>
|
True |
True: All information required by the Configuration wizard must be provided in the XML configuration file, including the SQL Server instance details. False: (For evaluations only.) The installer runs in the Express mode, it installs SQL Express, and runs the Configuration wizard with default configuration values. If you specify the values in the config file, the defaults are overwritten with your input. |
Parameters for running the Configuration wizard
Parameters used by the Configuration wizard are specified in the following sections:
<Host> <Info> <Database>...</Database> <Website>...</Website> </Info> </Host>
The following parameters can be specified in the <Info>
section, as needed.
Parameters | Values | Description |
---|---|---|
<ReconfigureDatabase>
|
True/False | Specifies whether the Configuration wizard configures the database. |
<ReconfigureWebsite>
|
True/False | Specifies whether the Configuration wizard configures the website. |
<ReconfigureServices>
|
True/False | Specifies whether the Configuration wizard configures services. |
<ReconfigurePermissions>
|
True/False | Specifies whether the Configuration wizard configures permissions. |
The following parameters can be specified in the <Database>
section, as needed. Additional parameters can be found in the examples below.
These parameters should also be specified in the <OrionLogConfiguration>
and <NetFlowConfiguration>
sections to configure the databases used to store log files and NetFlow data.
Parameters | Values | Description |
---|---|---|
<CreateNewDatabase>
|
True/False | For upgrades, specify False. |
<UseSQLSecurity>
|
True/False |
Specify True to authenticate to the database server using SQL Server authentication. Specify False to authenticate with Windows credentials. |
<DatabaseName>
|
string | The name of the SolarWinds Platform database. |
<ServerName>
|
string | A name or IP address to identify the server, such as localhost . |
<UserPassword>
|
string | The password of the SQL Server user if UseSQLSecurity is set to True. |
<User>
|
string | The SQL Server user name. For a new installation, this user must have the right to create a database. |
<AccountType>
|
NewSql ExistingSql ExistingWindows |
The type of account used to access the SolarWinds Platform database. |
<SqlServerAuthenticationType>
|
WindowsAuthentication SqlAuthentication ActiveDirectoryIntegrated ActiveDirectoryPassword |
The type of authentication used to access the SolarWinds Platform database. |
<Account>
|
string | The name of the SolarWinds Platform database account. |
<AccountPassword>
|
string |
The password to the SolarWinds Platform database account. Azure does not support non-secure passwords. |
<EncryptConnection>
|
True/False | Encrypt the connection to SQL Server with SSL. |
<TrustServerCertificate>
|
True/False | Skip SQL server certificate validation. Specify for example when self-signed SQL Server connection certificate is used. |
The following parameters can be specified in the <Website>
section, as needed. Additional parameters can be found in the examples below.
If you have your own certificate, specify CertificateHash
, CertificateName
, and CertificateResolvableCN
in your config.
With SolarWinds Platform 2023.2 and later, you can specify only the CertificateResolvableCN
property and leave CertificateHash
and CertificateName
empty. If you do this, the self-signed certificate is generated.
Parameters | Values | Description |
---|---|---|
<Folder>
|
string | The location of the SolarWinds Platform website folder (for example, C:\InetPub\SolarWinds). |
<Port>
|
numeric | The SolarWinds Platform website port number. |
<EnableHTTPS>
|
True/False | If this is set to True, HTTPS will be enabled. |
<EnableCentralizedCertificateStore>
|
True/False |
If this is set to True, the Centralized Certificate Store will be enabled. Also requires Ensure that the certificate is valid, not expired, and stored in the Centralized Certificate Store. |
<LaunchWebConsole>
|
True/False | Specifies whether the SolarWinds Platform Web Console will be launched after the Configuration wizard runs. |
<ConfigurationSkipped_IISNotInstalled>
|
True/False | If this is set to False and IIS is not installed, it will be installed. |
<DefaultAdminPassword>
|
string |
The password that the Admin account uses to log in to the SolarWinds Platform Web Console. For Orion Platform 2019.2 and later, this value can be specified the first time you install a SolarWinds Platform product in a new environment. If this element is not present and no password is specified for a new installation, the user is prompted to change the password during the first login. |
<CertificateHash>
|
string | The certificate hash. |
<CertificateName>
|
string | The certificate name. |
<CertificateResolvableCN>
|
string | The certificate resolvable common name. |
<SkipHTTPBinding>
|
True/False |
If this is set to True, IIS website configuration will be skipped. Set this parameter to False if you want to reconfigure website. |
Parameters for installing a scalability engine
If you are installing a scalability engine, specify the following parameters.
Parameters | Values | Description |
---|---|---|
<MainPollerHostname>
|
Example: 1.1.1.1 |
Specify the IP address or domain name of the main SolarWinds Platform server. |
<ServerType>
|
AdditionalPoller AdditionalWebsite MainPoller |
Specify the type of scalability engine to be installed. If |
<IsStandby>
|
True/False |
Specify whether the installation should be a High Availability standby server. This applies only when the |
<WebConsoleUserName>
|
string | This value is required when you are installing a scalability engine. It is the user name that the scalability engine can use to connect to the main polling engine. |
<WebConsolePassword>
|
string | This value is required when you are installing a scalability engine. It is the password that the scalability engine can use to connect to the main polling engine. |
Examples
- Example A: Standard fresh installation
- Example B: Standard fresh installation, configure 443 port
- Example C: Configuration files for installing scalability engines
- Example D: Upgrades
Example A: Standard fresh installation
To provide the SQL Server instance name and/or port, use the following syntax.
<ServerName>hostname\instance,port</ServerName>
The example config is below. Environment-specific values are in RED.
<?xml version="1.0" encoding="utf-8"?> <SilentConfig> <InstallerConfiguration> <InstallPath>C:\Program Files\SolarWinds\Orion</InstallPath> <AdvancedInstallMode>True</AdvancedInstallMode> <SkipConfigurationWizardRun>False</SkipConfigurationWizardRun> <!-- CW Error handling --> </InstallerConfiguration> <Host> <Info> <ReconfigureDatabase>true</ReconfigureDatabase> <ReconfigureWebsite>true</ReconfigureWebsite> <ReconfigureServices>true</ReconfigureServices> <ReconfigurePermissions>true</ReconfigurePermissions> <Database> <CreateNewDatabase>true</CreateNewDatabase> <!--(Sets flag to create new database during CW)--> <UseExistingSqlAccount>False</UseExistingSqlAccount> <UseSQLSecurity>true</UseSQLSecurity> <!--(Enables SQL Server authentication)--> <DatabaseName>SolarWindsOrion</DatabaseName> <!--(Orion database name)--> <DatabasePath/> <ServerName>127.0.0.1</ServerName> <!--(SQL server name for silent config wizard, e.g.: localhost)--> <InstanceName/> <!--(SQL instance name for silent config wizard)--> <UserPassword>Password</UserPassword> <!--(SQL account password, when you enabled UseSqlAuthentication)--> <User>sa</User> <!--(SQL account username, when you enabled UseSqlAuthentication)--> <AccountType>NewSql</AccountType> <!--(Orion database account access type. Other possible values: ExistingSql, ExistingWindows)--> <Account>SolarWindsOrionDatabaseUser</Account> <!--(Name of Orion database account, e.g.: SolarwindsOrionDatabaseUser)--> <AccountPassword>a</AccountPassword> <!--(Password to Orion database account)--> <NeedSQLServerSecurity>false</NeedSQLServerSecurity> <NeedToChangeSAPassword>false</NeedToChangeSAPassword> <AddServiceDependencies>false</AddServiceDependencies> <RemoveServiceDependencies>false</RemoveServiceDependencies> <FailureInfo/> </Database> <Website> <Folder>C:\InetPub\SolarWinds</Folder> <Address>(All Unassigned)</Address> <Port>80</Port> <ApplicationName>SolarWinds NetPerfMon</ApplicationName> <LaunchWebConsole>false</LaunchWebConsole> <ConfigurationSkipped_IISNotInstalled>false</ConfigurationSkipped_IISNotInstalled> <EnableWindowsLogin>true</EnableWindowsLogin> </Website> <OrionLogConfiguration> <StorageConfig> <CreateNewDatabase>True</CreateNewDatabase> <UseSQLSecurity>true</UseSQLSecurity> <AccountType>NewSql</AccountType> <UseExistingSqlAccount>False</UseExistingSqlAccount> <DatabaseName>SolarWindsOrionLog</DatabaseName> <DatabasePath /> <ServerName>127.0.0.1</ServerName> <InstanceName /> <User>sa</User> <UserPassword>Password</UserPassword> <Account>SolarWindsOrionDatabaseUser</Account> <AccountPassword>a</AccountPassword> <NeedSQLServerSecurity>false</NeedSQLServerSecurity> <NeedToChangeSAPassword>false</NeedToChangeSAPassword> <SAPassword /> <AddServiceDependencies>false</AddServiceDependencies> <RemoveServiceDependencies>false</RemoveServiceDependencies> <FailureInfo /> </StorageConfig> </OrionLogConfiguration> <NetFlowConfiguration> <FlowStorageConfig> <CreateNewDatabase>True</CreateNewDatabase> <UseSQLSecurity>True</UseSQLSecurity> <UseExistingSqlAccount>False</UseExistingSqlAccount> <DatabaseName>SolarWindsFlowStorage</DatabaseName> <DatabasePath /> <ServerName>127.0.0.1</ServerName> <InstanceName /> <UserPassword>Password1</UserPassword> <User>sa</User> <Account>SolarWindsNtaDatabaseUser</Account> <AccountType>NewSql</AccountType> <AccountPassword>123</AccountPassword> </FlowStorageConfig> </NetFlowConfiguration> </Info> </Host> <Plugins> <Plugin Assembly="SolarWinds.ConfigurationWizard.Plugin.LogMgmt" FactoryType="SolarWinds.ConfigurationWizard.Plugin.LogMgmt.SilentConfigureFactory" /> <Plugin Assembly="SolarWinds.ConfigurationWizard.Plugin.NetFlow" FactoryType="SolarWinds.ConfigurationWizard.Plugin.NetFlow.SilentMode.NetFlowSilentConfigureFactory" /> </Plugins> </SilentConfig>
Example B: Standard fresh installation, configure 443 port
Use the config from Example A, but change the <Website>
section to the following. Environment-specific values are in RED.
<Website> <Folder>C:\InetPub\SolarWinds</Folder> <Address>(All Unassigned)</Address> <Port>443</Port> <EnableHTTPS>true</EnableHTTPS> <CertificateHash>environment specific</CertificateHash> <CertificateName>environment specific</CertificateName> <CertificateResolvableCN>environment specific</CertificateResolvableCN> <ApplicationName>SolarWinds NetPerfMon</ApplicationName> <LaunchWebConsole>false</LaunchWebConsole> <ConfigurationSkipped_IISNotInstalled>false</ConfigurationSkipped_IISNotInstalled> <EnableWindowsLogin>true</EnableWindowsLogin> </Website>
Example C: Configuration files for installing scalability engines
Configuration file for installing SolarWinds High Availability when using Windows Authentication
This example installs SolarWinds High Availability when using Windows Authentication. Windows Authentication requires you to set a few more options. Environment-specific values are in RED.
<?xml version="1.0" encoding="utf-8"?> <SilentConfig> <InstallerConfiguration> <MainPollerHostname>1.1.1.1</MainPollerHostname> <ServerType>MainPoller</ServerType> <IsStandby>True</IsStandby> <WebConsoleUserName>Admin</WebConsoleUserName> <!--Enter user name and password only for first installation of SE.--> <WebConsolePassword>Password</WebConsolePassword> </InstallerConfiguration> <Host> <Info> <Database> <AccountType>ExistingWindows</AccountType> <SqlServerAuthenticationType>WindowsAuthentication</SqlServerAuthenticationType> </Database> </Info> </Host> </SilentConfig>
Configuration file for installing an additional website
This example installs an additional website. Environment-specific values are in RED.
<?xml version="1.0" encoding="utf-8"?> <SilentConfig> <InstallerConfiguration> <MainPollerHostname>1.1.1.1</MainPollerHostname> <ServerType>AdditionalWebsite</ServerType> <IsStandby>false</IsStandby> <WebConsoleUserName>Admin</WebConsoleUserName> <!--Enter user name and password only for first installation of SE.--> <WebConsolePassword>Password</WebConsolePassword> </InstallerConfiguration> </SilentConfig>
Example D: Upgrades
The following examples upgrade your product to a newer version.
You can use a shortened version of the config (below) if you don't want to change anything. During the upgrade, all required values are taken from the registry.
<?xml version="1.0" encoding="utf-8"?> <SilentConfig> <InstallerConfiguration> <SkipConfigurationWizardRun>False</SkipConfigurationWizardRun> </InstallerConfiguration> <Host> <Info> <ReconfigureDatabase>true</ReconfigureDatabase> <ReconfigureWebsite>true</ReconfigureWebsite> <ReconfigureServices>true</ReconfigureServices> <ReconfigurePermissions>true</ReconfigurePermissions> </Info> </Host> <Plugins> <Plugin Assembly="SolarWinds.ConfigurationWizard.Plugin.LogMgmt" FactoryType="SolarWinds.ConfigurationWizard.Plugin.LogMgmt.SilentConfigureFactory" /> <Plugin Assembly="SolarWinds.ConfigurationWizard.Plugin.NetFlow" FactoryType="SolarWinds.ConfigurationWizard.Plugin.NetFlow.SilentMode.NetFlowSilentConfigureFactory" /> </Plugins> </SilentConfig>
If you want to reconfigure certain databases or a website, include in the config only those sections that are related to the element you want to reconfigure.
The following example reconfigures the website to use port 443 and the NetFlow database. Environment-specific values are in RED.
<?xml version="1.0" encoding="utf-8"?> <SilentConfig> <InstallerConfiguration> <SkipConfigurationWizardRun>False</SkipConfigurationWizardRun> <!-- CW Error handling --> </InstallerConfiguration> <Host> <Info> <ReconfigureDatabase>true</ReconfigureDatabase> <ReconfigureWebsite>true</ReconfigureWebsite> <ReconfigureServices>true</ReconfigureServices> <ReconfigurePermissions>true</ReconfigurePermissions> <Website> <Folder>C:\InetPub\SolarWinds</Folder> <Address>(All Unassigned)</Address> <Port>443</Port> <EnableHTTPS>true</EnableHTTPS> <SkipHTTPBinding>false</SkipHTTPBinding> <CertificateHash>environment specific</CertificateHash> <CertificateName>environment specific</CertificateName> <CertificateResolvableCN>environment specific</CertificateResolvableCN> <ApplicationName>SolarWinds NetPerfMon</ApplicationName> <LaunchWebConsole>false</LaunchWebConsole> <ConfigurationSkipped_IISNotInstalled>false</ConfigurationSkipped_IISNotInstalled> <EnableWindowsLogin>true</EnableWindowsLogin> </Website> <NetFlowConfiguration> <FlowStorageConfig> <CreateNewDatabase>False</CreateNewDatabase> <UseSQLSecurity>True</UseSQLSecurity> <UseExistingSqlAccount>True</UseExistingSqlAccount> <DatabaseName>SolarWindsFlowStorage</DatabaseName> <DatabasePath /> <ServerName>127.0.0.1</ServerName> <InstanceName /> <UserPassword>Password</UserPassword> <User>sa</User> <Account>SolarWindsNtaDatabaseUser</Account> <AccountType>ExistingSql</AccountType> <AccountPassword>123</AccountPassword> </FlowStorageConfig> </NetFlowConfiguration> </Info> </Host> <Plugins> <Plugin Assembly="SolarWinds.ConfigurationWizard.Plugin.LogMgmt" FactoryType="SolarWinds.ConfigurationWizard.Plugin.LogMgmt.SilentConfigureFactory" /> <Plugin Assembly="SolarWinds.ConfigurationWizard.Plugin.NetFlow" FactoryType="SolarWinds.ConfigurationWizard.Plugin.NetFlow.SilentMode.NetFlowSilentConfigureFactory" /> </Plugins> </SilentConfig>
The following upgrade examples use a full config. Environment-specific values are in RED.
<?xml version="1.0" encoding="utf-8"?> <SilentConfig> <InstallerConfiguration> <SkipConfigurationWizardRun>False</SkipConfigurationWizardRun> <!-- CW Error handling --> </InstallerConfiguration> <Host> <Info> <ReconfigureDatabase>true</ReconfigureDatabase> <ReconfigureWebsite>true</ReconfigureWebsite> <ReconfigureServices>true</ReconfigureServices> <ReconfigurePermissions>true</ReconfigurePermissions> <Database> <CreateNewDatabase>False</CreateNewDatabase> <!--(Sets flag to create new database during CW)--> <UseSQLSecurity>true</UseSQLSecurity> <UseExistingSqlAccount>True</UseExistingSqlAccount> <!--(Enables SQL Server authentication)--> <DatabaseName>SolarWindsOrion</DatabaseName> <!--(Orion database name)--> <DatabasePath/> <ServerName>127.0.0.1</ServerName> <!--(SQL server name for silent config wizard, e.g.: localhost)--> <InstanceName/> <!--(SQL instance name for silent config wizard)--> <UserPassword>Password</UserPassword> <!--(SQL account password, when you enabled UseSqlAuthentication)--> <User>sa</User> <!--(SQL account username, when you enabled UseSqlAuthentication)--> <AccountType>ExistingSql</AccountType> <!--(Orion database account access type. Other possible values: ExistingSql, ExistingWindows)--> <Account>SolarWindsOrionDatabaseUser</Account> <!--(Name of Orion database account, e.g.: SolarwindsOrionDatabaseUser)--> <AccountPassword>a</AccountPassword> <!--(Password to Orion database account)--> <NeedSQLServerSecurity>false</NeedSQLServerSecurity> <NeedToChangeSAPassword>false</NeedToChangeSAPassword> <SAPassword>Password</SAPassword> <AddServiceDependencies>false</AddServiceDependencies> <RemoveServiceDependencies>false</RemoveServiceDependencies> <FailureInfo/> </Database> <Website> <Folder>C:\InetPub\SolarWinds</Folder> <Address>(All Unassigned)</Address> <Port>443</Port> <EnableHTTPS>true</EnableHTTPS> <SkipHTTPBinding>false</SkipHTTPBinding> <CertificateHash>environment specific</CertificateHash> <CertificateName>environment specific</CertificateName> <CertificateResolvableCN>environment specific</CertificateResolvableCN> <ApplicationName>SolarWinds NetPerfMon</ApplicationName> <LaunchWebConsole>false</LaunchWebConsole> <ConfigurationSkipped_IISNotInstalled>false</ConfigurationSkipped_IISNotInstalled> <EnableWindowsLogin>true</EnableWindowsLogin> </Website> <OrionLogConfiguration> <StorageConfig> <CreateNewDatabase>False</CreateNewDatabase> <UseSQLSecurity>true</UseSQLSecurity> <AccountType>ExistingSql</AccountType> <UseExistingSqlAccount>True</UseExistingSqlAccount> <DatabaseName>SolarWindsOrionLog</DatabaseName> <DatabasePath /> <ServerName>127.0.0.1</ServerName> <InstanceName /> <User>sa</User> <UserPassword>Password</UserPassword> <Account>SolarWindsOrionDatabaseUser</Account> <AccountPassword>a</AccountPassword> <NeedSQLServerSecurity>false</NeedSQLServerSecurity> <NeedToChangeSAPassword>false</NeedToChangeSAPassword> <SAPassword /> <AddServiceDependencies>false</AddServiceDependencies> <RemoveServiceDependencies>false</RemoveServiceDependencies> <FailureInfo /> </StorageConfig> </OrionLogConfiguration> <NetFlowConfiguration> <FlowStorageConfig> <CreateNewDatabase>False</CreateNewDatabase> <UseSQLSecurity>True</UseSQLSecurity> <UseExistingSqlAccount>True</UseExistingSqlAccount> <DatabaseName>SolarWindsFlowStorage</DatabaseName> <DatabasePath /> <ServerName>127.0.0.1</ServerName> <InstanceName /> <UserPassword>Password1</UserPassword> <User>sa</User> <Account>SolarWindsNtaDatabaseUser</Account> <AccountType>ExistingSql</AccountType> <AccountPassword>123</AccountPassword> </FlowStorageConfig> </NetFlowConfiguration> </Info> </Host> <Plugins> <Plugin Assembly="SolarWinds.ConfigurationWizard.Plugin.LogMgmt" FactoryType="SolarWinds.ConfigurationWizard.Plugin.LogMgmt.SilentConfigureFactory" /> <Plugin Assembly="SolarWinds.ConfigurationWizard.Plugin.NetFlow" FactoryType="SolarWinds.ConfigurationWizard.Plugin.NetFlow.SilentMode.NetFlowSilentConfigureFactory" /> </Plugins> </SilentConfig>
Step 2: Run the silent installation commands
Replace the entries in bold red with your data, and run the following commands using the command prompt.
The /s
flag makes the installer run in silent mode. You might need to add ""
before /wait
: ""/wait
cd "FOLDER-WHERE-INSTALLER-IS" start /wait "PRODUCT-INSTALLER-EXE" /s /ConfigFile="FULL-PATH-TO-CONFIGURATION-FILE"
You must use the full path to the configuration file, not a relative path, for the command to work properly.
Skip validation of the configuration file
Starting with 2023.4, a simple validation of the config is run by default. However, the validation does not guarantee that the configuration is correct. You can find the output in the logs. You can skip the validation by adding the SkipValidation
argument:
cd "FOLDER-WHERE-INSTALLER-IS" start /wait "PRODUCT-INSTALLER-EXE" /s /ConfigFile="FULL-PATH-TO-CONFIGURATION-FILE" /SkipValidation
Step 3: Run the silent installation command to upgrade existing scalability engines
If you are upgrading products in an existing deployment that includes scalability engines, you can run a Centralized Upgrade in silent mode after the main polling engine is upgraded. The Centralized Upgrade does the following:
- Contacts all reachable scalability engines and performs preflight checks.
If any scalability engine is not reachable or has a blocking issue, the issue is logged and that scalability engine is not upgraded. - Downloads the installer to each scalability engine without blocking issues, and runs the installers in parallel.
- The silent centralized upgrade requires the main polling engine to be updated so that the user can update outdated scalability engines to the main polling engine version.
- Do not stop the SolarWinds Administration Service on your scalability engines before the centralized upgrade. If you stop this service, the scalability engines are not reachable.
To start the Centralized Upgrade, replace the entries in bold red with your data, and run the following commands from a command prompt on the main SolarWinds Platform server.
cd "FOLDER-WHERE-INSTALLER-IS"
start "PRODUCT-INSTALLER-EXE" /silentcentralizedupgrade
As the upgrade progresses, you can track progress from the SolarWinds Platform Web Console.