Silent Installation File Parameters
The following command-line options are used to run the silent installation file:
Option | Parameter | Required | Description |
|---|---|---|---|
ACCEPT_EULA | 0/1 | Yes | Specifies if you want to accept the Veeam license agreement. To accept the license agreement and to proceed with installation, set the parameter value to 1. Example: ACCEPT_EULA="1" |
ACCEPT_THIRDPARTY_LICENSES | 0/1 | Yes | Specifies if you want to accept the license agreement for 3rd party components that Veeam incorporates. To accept the license agreement and to proceed with installation, set the parameter value to 1. Example: ACCEPT_THIRDPARTY_LICENSES="1" |
ACCEPT_LICENSING_POLICY | 0/1 | Yes | Specifies if you want to accept the Veeam licensing policy. To accept the licensing policy and to proceed with installation, set the parameter value to 1. Example: ACCEPT_LICENSING_POLICY="1" |
ACCEPT_REQUIRED_SOFTWARE | 0/1 | Yes | Specifies if you want to accept the license agreements for each of the required software that Veeam will install. To accept the license agreement and to proceed with installation, set the parameter value to 1. Example: ACCEPT_REQUIRED_SOFTWARE="1" |
VRO_LICENSE_FILE | path | Yes | Specifies a full path to the license file. You will not be able to perform installation without providing a license. Example: VRO_LICENSE_FILE="C:\Users\Administrator\Downloads\vro_nfr.lic" |
VRO_LICENSE_AUTOUPDATE | 0/1 | No | Specifies if the license is updated automatically. If you do not specify this parameter, automaticlicense update will be enabled by default. For the Community Edition, NFR and Evaluation licenses, set the parameter value to 1. For licenses without the license ID information, the parameter value to 0. Example: VRO_LICENSE_AUTOUPDATE="1" |
VRO_PROACTIVE_SUPPORT | 0/1 | No | Specifies if you want to receive proactive support and to enable diagnostic data sharing. If you do not specify this parameter, proactive support will be enabled by default. For the Community Edition, NFR and Evaluation licenses, set the parameter value to 1. For licenses without the license ID information, the parameter value to 0. Example: VRO_PROACTIVE_SUPPORT="1" |
VRO_SERVICE_USER | user | Yes | Specifies an account under which the Veeam Orchestrator Server Service will run. For more information on the required account permissions, see Planning and Preparation. Along with this parameter, you must define the VRO_SERVICE_PASSWORD parameter. Example: VRO_SERVICE_USER="srv\Administrator" |
VRO_SERVICE_PASSWORD | password | Yes | Specifies a password for the account under which the Veeam Orchestrator Server Service will run. Example: VRO_SERVICE_PASSWORD="1234" |
VRO_SQLSERVER_INSTALL | 0/1 | Yes | Specifies if an existing Microsoft SQL Server instance will be used to host the Orchestrator database or a new Microsoft SQL Server instance will be created locally. To create a new Microsoft SQL Server instance, set the parameter value to 1. If you want to use the existing Microsoft SQL Server instance, set this parameter to 0 and define the following parameters for the existing database: VRO_SQLSERVER_SERVER and VRO_SQLSERVER_DATABASE. Example: VRO_SQLSERVER_INSTALL="1" |
VRO_SQLSERVER_SERVER | SQL Server\instance | No | Specifies a Microsoft SQL Server instance where the Orchestrator configuration database will be deployed. By default, (local)\VEEAMSQL2017. Example: VRO_SQLSERVER_SERVER="localhost\VEEAMSQL2017" |
VRO_SQLSERVER_DATABASE | database | No | Specifies a name of the Orchestrator configuration database to be deployed. By default, VAO. Example: VRO_SQLSERVER_DATABASE="OrchestratorDB" |
VBR_SQLSERVER_DATABASE | database | No | Specifies a name of the Veeam Backup & Replication configuration database. Keep in mind that both the Veeam ONE configuration database and the Orchestrator database must be hosted on the same Microsoft SQL Server instance. Example: VBR_SQLSERVER_DATABASE="VBR" |
VO_SQLSERVER_DATABASE | database | No | Specifies a name of the Veeam ONE configuration database. Keep in mind that both the Veeam ONE configuration database and the Orchestrator database must be hosted on the same Microsoft SQL Server instance. Example: VO_SQLSERVER_DATABASE="VeeamOne" |
VRO_SQLSERVER_AUTHENTICATION | 0/1 | No | Specifies if you want to use the SQL Server authentication mode to connect to the Microsoft SQL Server where the Orchestrator configuration database is deployed. To use the SQL Server authentication mode, set the parameter value to 1. If you do not define this parameter, Orchestrator will connect to the Microsoft SQL Server in the Microsoft Windows authentication mode (default value, 0). Along with this parameter, you must define the following parameters: VRO_SQLSERVER_USERNAME and VRO_SQL_PASSWORD. Example: VRO_SQLSERVER_AUTHENTICATION="1" |
VRO_SQLSERVER_USERNAME | user | No | [Applies only if you have defined the VRO_SQLSERVER_AUTHENTICATION parameter] Specifies a LoginID to connect to the Microsoft SQL Server in the SQL Server authentication mode. Example: VRO_SQLSERVER_USERNAME="sa" |
VRO_SQLSERVER_PASSWORD | password | No | [Applies only if you have defined the VRO_SQLSERVER_AUTHENTICATION parameter]. Specifies a password to connect to the Microsoft SQL Server in the SQL Server authentication mode. Example: VRO_SQLSERVER_PASSWORD="1234" |
VBR_ENTRAID_DATABASE_INSTALL | 0/1 | No | Specifies if a PostgreSQL Server for the Microsoft Entra ID database will be installed. To install the PostgreSQL Server for the Microsoft Entra ID, set the parameter value to 1. If you do not define this parameter, the PostgreSQL Server will not be installed (default value, 0). |
VO_POSTGRESQL_INSTALL | 0/1 | Yes | Specifies if a new PostgreSQL server used for the Veeam ONE reporting database will be installed. To install a new PostgreSQL database, set the parameter to 1. If you want to use the existing PostgreSQL database, set this parameter to 0 and define the following parameters for the existing database: VO_POSTGRESQL_SERVER and VO_POSTGRESQL_DATABASE. Example: VRO_POSTGRESQL_INSTALL="1" |
VO_POSTGRESQL_SERVER | PostgreSQL Server:instance | No | Specifies a PostgreSQL Server instance where the Veeam ONE reporting database will be deployed. By default, (local):5432. Example: VO_POSTGRESQL_SERVER="localhost:5432" |
VO_POSTGRESQL_DATABASE | database | No | Specifies a name of the Veeam ONE reporting database. Keep in mind that both the Veeam ONE reporting database and the Orchestrator database must be hosted on the same machine. Example: VO_POSTGRESQL_DATABASE="VeeamOne" |
VO_POSTGRESQL_AUTHENTICATION | 0/1 | No | Specifies if you want to use the PostgreSQL Server authentication mode to connect to the PostgreSQL Server where the Veeam ONE reporting database is deployed. To use the PostgreSQL authentication mode, set the parameter value to 1. If you do not define this parameter, Orchestrator will connect to the PostgreSQL Server in the Microsoft Windows authentication mode (default value, 0). Along with this parameter, you must define the following parameters: VO_POSTGRESQL_USERNAME and VO_POSTGRESQL_PASSWORD. Example: VO_POSTGRESQL_AUTHENTICATION="1" |
VO_POSTGRESQL_USERNAME | user | No | [Applies only if you have defined the VO_POSTGRESQL_AUTHENTICATION parameter] Specifies a LoginID to connect to the PostreSQL Server in the PostreSQL Server authentication mode. Example: VO_POSTGRESQL_USERNAME="sa" |
VO_POSTGRESQL_PASSWORD | password | No | [Applies only if you have defined the VO_POSTGRESQL_AUTHENTICATION parameter]. Specifies a password to connect to the PostreSQL Server in the PostreSQL authentication mode. Example: VO_POSTGRESQL_PASSWORD="1234" |
VRO_SERVICE_PORT | port | No | Specifies a TCP port that will be used by the Veeam Orchestrator Server Service to connect to Orchestrator agents running on remote Veeam Backup & Replication servers. By default, 8888. Example: VRO_SERVICE_PORT=”8884” |
VRO_SERVICE_WCF_PORT | port | No | Specifies a WCF port that will be used to connect to the Veeam Orchestrator Server Service. By default, 12348. Example: VRO_SERVICE_WCF_PORT=”12247” |
VRO_WEBSITE_PORT | port | No | Specifies an IIS port that will be used to connect to the Orchestrator UI website from a web browser. By default, 9898. Example: VRO_WEBSITE_PORT=”9998” |
VRO_MONITORING_SERVICE_PORT | port | No | Specifies a port that will be used to communicate with the Veeam ONE Monitoring service. By default, 2714. Example: VRO_WEBSITE_PORT=”2715” |
VO_CACHING_SERVICE_PORT | port | No | Specifies a port that will be used to communicate with Veeam ONE Caching service. By default, 2714. Example: VO_CACHING_SERVICE_PORT=”2743” |
VO_REPORTING_SERVICE_PORT | port | No | Specifies a port that will be used to communicate with Veeam ONE Reporting service. By default, 2742. Example: VO_REPORTING_SERVICE_PORT=”2745” |
VO_INTERNAL_WEB_API_PORT | port | No | Specifies a port that will be used by Veeam ONE Monitoring service and Veeam ONE Web Services to communicate with Veeam ONE Reporting service. By default, 2741. Example: VO_REPORTING_SERVICE_PORT=”2745” |
VO_WEBSITE_PORT | port | No | Specifies an IIS port that will be used to connect to the Veeam ONE Web Client from a web browser. By default, 1239. Example: VO_WEBSITE_PORT=”1234” |
VO_AGENT_SERVICE_PORT | port | No | Specifies a port that will be used by Veeam Analytics service to collect data from the connected Veeam Backup & Replication servers. By default, 2805. Example: VO_AGENT_SERVICE_PORT=”2808” |
VBRC_SERVICE_PORT | port | No | Specifies a TCP port that will be used by the Veeam Guest Catalog Service. By default, 9393. Example: VBRC_SERVICE_PORT=”9394” |
VBR_SERVICE_PORT | port | No | Specifies a TCP port that will be used by the Veeam Backup Service. By default, 9392. Example: VBR_SERVICE_PORT=”9395” |
VBR_SECURE_CONNECTIONS_PORT | port | No | Specifies a TCP port that will be used for communication between the mount server and the backup server. By default, 9401. Example: VBR_SECURE_CONNECTIONS_PORT=”9402” |
VBR_RESTSERVICE_PORT | port | No | Specifies an HTTPS port that will be used to connect to the Orchestrator REST API website from a web browser. By default, 9419. Example: VBR_RESTSERVICE_PORT=”9999” |
VRO_CERTIFICATE_THUMBPRINT | hash | No | Provides a thumbprint of an SSL certificate that will be used to secure traffic between the Orchestrator UI and a web browser. Example: VRO_CERTIFICATE_THUMBPRINT="a909502dd82ae41433e6f83886b00d4277a32a7b" |
INSTALLDIR | path | No | Installs the component to the specified location. By default, Orchestrator uses a subfolder in the C:\Program Files\Veeam\Orchestrator\ folder. Example: INSTALLDIR=”C:\Veeam\” |
REBOOT_IF_REQUIRED | 0/1 | No | Specifies if the machine where you are installing Orchestrator will be rebooted after the installation process completes. To reboot the machine, set the parameter to 1. If you do not specify this parameter, the machine will be rebooted automatically. Example: REBOOT_IF_REQUIRED="1" |
LOGOFF_IF_REQUIRED | 0/1 | No | Specifies if the session is logged off after the installation process completes. To log off the session, set the parameter to 1. If you do not specify this parameter, the session will not be logged off automatically. Example: LOGOFF_IF_REQUIRED="1" |