VeeamVES64.msi allows you to install VE Service on a machine that does not run the Operations Manager SDK. However, it will not be able to support the following Veeam MP 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>"
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 “no”.
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.
Specify the service account in the DOMAIN\USERNAME format. The account will be used for running the Veeam Virtualization Extensions service. The account must have administrative privileges on the computers hosting the Veeam Virtualization Extensions Service and the Collector(s).
Specify the password for the Veeam Virtualization Extensions service user.
Specify TCP port that will be used by the Veeam Virtualization Extensions service. By default, port number 8084 is used.
Management Server resource pool
Specify name of the Management Server resource pool for Collector auto-deployment. Specify name of the Management Server resource pool for Collector auto-deployment. The name must be the same as the resource pool name in the Ops Mgr.
If the parameter is not specified, auto-deployment is disabled.
After installation is complete, log off the server, then log on again. Or, in case you are installing Veeam UI remotely with Windows PowerShell, you will need to close the remote PowerShell session and initiate a new one.
Confirm installation and operation of the Veeam Virtualization Extensions service by checking the Windows Event Viewer. A new application logs called Veeam Virtualization Extensions will be created when the Veeam Virtualization Extensions service starts, and events from the Veeam Virtualization Extensions source should appear in this log.