After you convert your vCenter Server to subscription, you can manage your vCenter Server updates from the VMC Console.

To manage updates for your vCenter Server from the VMC Console, as a one-time activity, you must provide the following network configuration details for each vCenter Server:
  • Temporary network: The network for communication between the new appliance and the appliance you want to update.
  • Troubleshooting network: The network for troubleshooting any update issues if the vCenter Server is unreachable.


  • Ensure that your vSphere environment meets all the requirements. See System Requirements for vSphere+.
  • The vCenter Server must be self-managed. It must manage its own ESXi hosts and virtual machines.

    For your vCenter Server deployment, take the appropriate action to convert it to a self-managed vCenter Server.

    Table 1. Converting a vCenter Server to a Self-Managed vCenter Server
    vCenter Server Deployment Action
    vCenter Server deployed on an unmanaged host Add the host to the management cluster. See Add a Managed Host to a Cluster.
    vCenter Server deployed on a standalone host managed by a different vCenter Server Remove the host from the managing vCenter Server and add the host to the management cluster. See:
    vCenter Server deployed on a cluster managed by a different vCenter Server Perform either of the following tasks:
  • Ensure that the vCenter Server is on the latest version with the latest patch.
    1. Download the latest version of the vCenter Server by using the Downloads option in the VMC Console. See Download Software Binaries.
    2. Update your vCenter Server to the latest version. See the vCenter Server Upgrade documentation.
    3. Depending on the upgrade path of your vCenter Server version, you might have to back up and restore the vCenter Server after the update. See
  • If you plan to choose DHCP for IP assignment, ensure that the MAC Address Changes policy is set for all the hosts in the management cluster. See Configure the Security Policy.
  • Verify that the network configuration meets the following requirements:
    Network Requirement
    Temporary Network The temporary network and the vCenter Server network must be in the same subnet.
    Troubleshooting Network
    • Choose a network that is not already connected to the vCenter Server for other purposes, such as backup and restore.
    • The troubleshooting network must be on a subnet and VLAN different than the vCenter Server and vCenter Cloud Gateway.
    • The troubleshooting network must be routable from the vCenter Server network.


  1. Log in to the VMC Console at
  2. Use either of the following methods to navigate to the Maintenance tab:
    • In the Enable Updates for vCenter Server notification, click Enable Updates.
    • Go to Inventory, select the vCenter Server, and then click Maintenance.
  3. Click Enter network details.
  4. Select the cluster where the vCenter Server and vCenter Cloud Gateway VMs are deployed.
    You cannot change the cluster selection after the settings are applied.
  5. Enter the network configuration details for both temporary network and troubleshooting network.
  6. Click Apply.


  • vSphere+ creates a management resource pool and reserves the required hardware in the management cluster for vCenter Server updates. The vCenter Server and vCenter Cloud Gateway, if deployed in the same vCenter Server, are moved to the management resource pool. Do not change these management resource pool configurations. Do not move the vCenter Server out of this cluster.
  • vSphere+ reserves the required CPU and memory in vCenter Server and vCenter Cloud Gateway VMs for future updates.
  • vSphere+ adds a secondary NIC to the vCenter Server for troubleshooting purposes.

What to do next

  • Monitor your vSphere inventory, and explore vSphere+ services. See Using and Managing vSphere+.
  • Whenever an update is available for your vCenter Server, vSphere+ displays a notification. You can update your vCenter Server from the VMC Console. See Update Your vCenter Server.