Step 2. Install VE Service, Web UI and Veeam Data Collector for vSphere

To install the VE Service, web UI and Collector, do the following:

1. Log in to the machine where you want to install Veeam MP for VMware using an account with the local Administrator rights.
2. Mount the installation image.
3. On the splash screen, click Install.
4. Complete the Veeam Management Pack Setup wizard:
   1. At the License Agreement step, read and accept the Veeam license agreement, the licensing policy, the 3rd party components license agreement and the license agreement of the required software.

      If you reject the agreements, you will not be able to continue installation.

   2. At the Program Features step, make sure that the Veeam Virtualization Extensions Service and Web UI and Veeam Data Collector for vSphere check boxes are selected.

      If the setup wizard detects Veeam Backup & Replication running on your machine, it will offer to install a Veeam Data Collector for Veeam Backup & Replication on this machine. However, you can clear the check box since this feature is optional.

      Tip

      If you keep the Veeam Data Collector for Veeam Backup & Replication check box selected, a number of management packs for Data Collector for Veeam Backup & Replication will be installed on your Management Server as well. For more information on the managements packs, see the Veeam MP for Veeam Backup & Replication User Guide.

   3. At the License step, browse to a local folder on your workstation to locate the license file provided to you by Veeam. To do that, click Browse to local license file.

      Note that you will not be able to continue installation without providing a license.

   4. At the Service Account step, enter credentials of an account under which the Veeam Virtualization Extensions Service will run. The account must be a member of the local Administrators group. The user name must be specified in the DOMAIN\USERNAME format.

      For more information on accounts and privileges, see Required Permissions.

      Tip

      By default, the Veeam Data Collector for vSphere service will run under an account that differs from the VE Service account. However, it is recommended that you use the same account.

   5. [This step applies only if you have not selected the Use the same account for Veeam VMware Collector service check box at the Service Account step]

      At the Data Collector Service Account step, enter credentials of an account under which the Collector services will run. The account must be a member of the local Administrators group. The user name must be specified in the DOMAIN\USERNAME format.

      For more information on accounts and privileges, see Required Permissions.

      Note

      After you click Next, the setup wizard will run the system configuration check and will automatically install the missing ASP.NET Core Runtime and .NET runtime components (if any).

   6. At the Ready to Install step, review the default installation configuration. Click Install to begin installation. Wait for the installation process to complete and click Finish to exit the setup wizard.

When installation completes, log out and then log in again to create the Veeam Virtualization Extensions Users local group that will be used to accommodate the service account. If there are other users who will need access to the web UI to configure the VMware monitoring, add these user accounts to this group in System Center Operations Manager manually.

Customizing Settings

If you have clicked Customize Settings at the Ready to Install step of the wizard, do the following:

1. At the Data Locations step, specify a path to the folder where Veeam MP for VMware components will be installed.
2. At the Port Configuration step, customize ports used by Veeam MP for VMware. For the full description of ports and their default values, see Network Protocols and Ports.
3. At the Certificate Selection step, choose a TLS certificate that will be used to secure traffic between the web UI and a web browser. Veeam MP offers the following options: use an existing TLS certificate located in the certificate store, or keep the default self-signed TLS certificate that will be generated during installation (this is the recommended option).