---
title: "Configure Run As Profile for vCenter Connection Failover"
description: "The vCenter Connection Failover functionality is available only in the Enterprise Plus Edition. Skip this step if you do not plan to use the vCenter Connection Failover feature."
canonical: "https://helpcenter.veeam.com/docs/mp/vmware_guide/configure_run_as_profile.html"
breadcrumb: "Veeam MP for VMware User Guides > Installation Guide > Installing Veeam MP for VMware > After You Install > Configure Run As Profile for vCenter Connection Failover"
dateModified: "2026-10-13"
---

# Configure Run As Profile for vCenter Connection Failover

::: note

The vCenter Connection Failover functionality is available only in the Enterprise Plus Edition. Skip this step if you do not plan to use the vCenter Connection Failover feature.

:::

After you install Veeam MP for VMware components, the *Veeam VMware Collector: vCenter connection failover errors and warnings* alert will be fired in the OpsMgr console:

[![Configure Run As Account](images/vcenter_failover_warning.png "Configure Run As Account")](images/vcenter_failover_warning.png){.toggle scale=60}

The *Veeam VMware Direct ESX(i) Connection Account* is required for the vCenter Connection Failover feature implemented to allow VMware vSphere hosts and VMs monitoring to continue, even if vCenter Server goes offline. For more information about vCenter Connection Failover, see [vCenter Connection Failover](vcenter_connection_failover.md).

To configure the *Veeam VMware Direct ESX(i) Connection Account*:

1. Log in to the OpsMgr console using an account with the local Administrator rights. 
2. Go to the **Administration** section.
3. Expand the **Run As Configuration** node.
4. Select **Profiles**.
5. In the list of profiles, double-click the inbuilt *Veeam VMware Direct ESX(i) Connection Account*.
6. Click **Next** to begin the **Run As Profile Wizard**.
7. At the **Add Run As Accounts** step of the wizard, click **Add**. 
8. In the **Add a Run As Account** window, click **New** and complete the **Create Run As Account** wizard:

   1. At the **General Properties** step, choose *Basic Authentication* as the account type. Specify the account display name and description.
   2. At the **Credentials** step, specify credentials of the user account that will be used for direct-to-host connections. 

      ::: note

      You can create several Run As accounts, but only the first one will be used for connection to the managed vSphere hosts. For this reason, you must specify the same credentials for all vCenter Server-managed ESXi hosts in your environment (even hosts in different vCenter Servers). For more information, see [Required Permissions](accounts_and_privileges.md).

      :::

   3. At the **Distribution Security** step, choose the necessary distribution security level. 

      If you choose the *More secure* level, you will need to [manually distribute the account credentials](#distribute_credentials) to the Management Server where the VE Service runs (in case of the single-server installation, this is the server where all Veeam MP for VMware components are installed).

   4. Click **Create** to save the account.
   5. Click **Save** to save the profile.

<a id="distribute_credentials"></a>To distribute the account credentials to the Managements Server where the VE Service runs:

1. Log in to the OpsMgr console using an account with the local Administrator rights.
2. Go to the **Administration** section.
3. Expand the **Run As Configuration** node.
4. Select **Accounts**.
5. Double-click the created Run As account. 
6. In the **Run As Account Properties** window, switch to the **Distribution** tab. 
7. Click **Add**. In the **Computer Search** window, search and add the required Management Server.

::: note

The vCenter Connection Failover script runs under the Agent Action Account on the VE Service server. For the script to function properly, this Agent Action Account must also be a member of the *Veeam Virtualization Extensions Users* local group on the server.

Keep in mind that the vCenter Connection Failover feature will not work if you use Local System as the default Agent Action Account.

:::