Veeam Service Provider Console Web UI

To install Veeam Service Provider Console web UI, use a command with the following syntax:

msiexec.exe [/L*v "<path_to_log>"] /qn /i "<path_to_msi>" [ACCEPT_THIRDPARTY_LICENSES="1"][ACCEPT_EULA="1"][VAC_SERVER_NAME="<product_server_name>"] [VAC_SERVER_PORT="<port_number>"] [VAC_RESTAPI_PORT="<port_number>"] [VAC_WEBSITE_PORT="<port_number>"] [VAC_CONFIGURE_SCHANNEL="1"]

The command has the following parameters:

Option

Parameter

Required

Description

/L

*v logfile

No

Creates an installation log file with the verbose output.

Specify an existing path to the log file as the parameter value. A setup log file created during the previous installation is cleared.

Example: /L*v ”C:\ProgramData\Veeam\Setup\Temp\Logs\VACServerSetup.txt”

/q

n

Yes

Sets the user interface level to “no”, which means no user interaction is needed during installation.

/i

setup file

Yes

Installs Veeam Service Provider Console web UI. Specify a full path to the setup file as the parameter value.

Example: /i “C:\Veeam\VAC\VAC.WebUI.x64.msi”

ACCEPT_THIRDPARTY_LICENSES

0/1

Yes

Specifies if you want to accept the terms of the license agreement for the 3rd party components. Specify 1 if you want to accept the terms and proceed with installation.

Example: ACCEPT_THIRDPARTY_LICENSES="1"

ACCEPT_EULA

0/1

Yes

Specifies if you want to accept the terms of the Veeam license agreement.

Specify 1 if you want to accept the terms and proceed with installation.

Example: ACCEPT_EULA="1"

VAC_SERVER_NAME

server name or address

Yes

Specifies FQDN or IP address of the server where Veeam Service Provider Console server is deployed.

Example: VAC_SERVER_NAME=“vac.cloudprovider.com"

VAC_SERVER_PORT

port

No

Specifies the port number that the Veeam Service Provider Console Web UI component uses to communicate with the Server component.

If you do not use this parameter, Veeam Service Provider Console Web UI component will use the default port 1989.

Example: VAC_SERVER_PORT="102"

VAC_RESTAPI_PORT

port

No

Specifies the port number used to exchange RESTful API requests and responses between Veeam Service Provider Console Web UI component and a client application.

If you do not use this parameter, Veeam Service Provider Console Web UI component will use the default port 1281.

Example: VAC_RESTAPI_PORT="105"

VAC_WEBSITE_PORT

port

No

Specifies the port number used to transfer traffic between Veeam Service Provider Console Web UI component and a web browser.

If you do not use this parameter, Veeam Service Provider Console Web UI component will use the default port 1280.

Example: VAC_WEBSITE_PORT="106"

VAC_CONFIGURE_SCHANNEL

0/1

No

Specifies if the High security mode option must be used for the Veeam Service Provider Console Web UI installation. The option enforces TLS 1.2 encryption protocol and disables using weak ciphers for all communications with the machine on which Veeam Service Provider Console Web UI component runs.

Specify 1 to enable High security mode. Specify 0 to proceed with installation without enabling High security mode.

If you do not use this parameter, Veeam Service Provider Console Web UI component will use the High security mode by default.

Example: VAC_CONFIGURE_SCHANNEL="1"

Example

Suppose you want to install Veeam Service Provider Console web UI with the following configuration:

  • Installation log location: C:\ProgramData\Veeam\Setup\Temp\Logs\VACWebUISetup.txt
  • No user interaction
  • Path to the MSI file: C:\Veeam\VAC\VAC.WebUI.x64.msi
  • Accept 3rd party license agreement
  • Accept Veeam license agreement
  • Communication ports: default
  • Secure connection: enabled

The command to install Veeam Service Provider Console Web UI with such configuration will have the following parameters:

msiexec /qn /l*v C:\ProgramData\Veeam\Setup\Temp\Logs\VACWebUISetup.txt /i "C:\Setup\VAC.WebUI.x64.msi"  VAC_SERVER_NAME="vac.cloudprovider.com" ACCEPT_THIRDPARTY_LICENSES="1" ACCEPT_EULA="1" VAC_CONFIGURE_SCHANNEL="1"

I want to report a typo

There is a misspelling right here:

 

I want to let the Veeam Documentation Team know about that.