Veeam Virtualization Extensions Service
VeeamVES64.msi allows you to install the VE Service on a machine that does not run the OpsMgr SDK. However, it will not be able to support the following Veeam MP for VMware features:
Open the command prompt and run the setup file VeeamVES64.msi using the following parameters:
msiexec.exe [/L*v! "<path_to_log>"] /qn /I "<path_to_msi>" [INSTALLDIR="<path_to_installdir >"] VES_LICENSE_FILE="<path_to_license_file>" VES_SERVICE_USER="<Veeam_Virtualization_Extensions_Service_account>" VES_SERVICE_PASSWORD="<Veeam_Virtualization_Extensions_Service_account_password>" [VES_SERVER_PORT="< Veeam_Virtualization_Extensions_Service_port>"] [VES_RES_POOL="<Management_Server_Resource_Pool>"]
The following command-line options are used to run the setup file:
Creates installation log file with the verbose output.
Specify a full path to the log file as the parameter value. Any setup log file created during the previous installation will be cleared.
Sets user interface level to None.
Installs the Veeam Virtualization Extensions Service component.
Specify a full path to the setup file as the parameter value.
Installs the component to the specified location.
Specify the full path to the license file.
Use the DOMAIN\USERNAME format to specify the service account. The account will be used for running the VE Service.
The account must have Administrator permissions on computers hosting the VE Service and Collectors.
Specify a password for the Veeam Virtualization Extensions Service user.
Specify a TCP port that will be used by the VE Service (by default, 8084).
Management Server resource pool
Specify a name of the Management Server resource pool for Collector auto-deployment. This name must match the resource pool name in the OpsMgr.
The parameter is required only for Veeam VMware Collector Auto-Deployment.
After installation completes, log off the server, then log on again. Or, in case you are installing the Veeam UI remotely with Windows PowerShell, close the remote PowerShell session and initiate a new one.
Confirm installation and operation of the VE Service by checking the Windows Event Viewer. As soon as the VE Service starts, a new application log called Veeam Virtualization Extensions will be created, and events from the Veeam Virtualization Extensions source will appear in this log.