---
name: vmwaresolutions-vc_removingservers
title: Deleting ESXi servers from VCF for Classic - Automated instances
description: As of 17 July 2025, new automated installations of Red Hat® OpenShift® for VMware® are no longer available for new or existing deployments of VMware Cloud Foundation for Classic - Automated instances. You can still use or delete your existing Red Hat OpenShift for VMware automated installations until 16 July 2026. The service will no longer be available from 17 July 2026.
last-updated: 2026-01-21
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/vmwaresolutions?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Deleting ESXi servers from VCF for Classic - Automated instances
{: #vc_removingservers}

As of 17 July 2025, new automated installations of Red Hat® OpenShift® for VMware® are no longer available for new or existing deployments of VMware Cloud Foundation for Classic - Automated instances. You can still use or delete your existing Red Hat OpenShift for VMware automated installations until 16 July 2026. The service will no longer be available from 17 July 2026.
{: deprecated}

You can contract the capacity of your VMware Cloud Foundation for Classic - Automated instance according to your business needs by deleting VMware ESXi™ servers.

## Before you delete ESXi servers from Automated instances
{: #vc_removingservers-prereq}

CONTENT:

Whenever possible, add clusters by using the IBM Cloud® for VMware Solutions console and not the VMware vSphere® Web Client. Changes that you make on the vSphere Web Client are not synchronized with the VMware Solutions console. If you want to add clusters to VMware Cloud Foundation for Classic - Automated instances by using the vSphere Web Client, do so only for on-premises clusters or clusters that you don't manage in the VMware Solutions console.
{: important}

* For the gateway cluster, you cannot add or delete ESXi servers.
* When you delete ESXi servers, the servers are placed in maintenance mode, and then, all the virtual machines (VMs) running on the servers are migrated before they are deleted from vCenter Server. For maximum of control over the relocation of VMs, place the ESXi servers in maintenance mode and migrate the VMs running on them manually using the VMware vSphere Web Client. After that, delete the ESXi servers by using the VMware Solutions console.
* If you are using NFS storage, your instance requires at least three ESXi servers for a consolidated cluster or at least two servers for any other cluster.
* If you are using vSAN storage, at least four ESXi servers are required.

## Procedure to delete ESXi servers from Automated instances
{: #vc_removingservers-procedure}

1. In the VMware Solutions console, click **Licensing and metering > Add-on services** from the left navigation panel.
2. In the **VMware Cloud Foundation for Classic** table, click the instance for which you want to contract capacity.
3. Click the **Infrastructure** tab.
4. In the applicable cluster table, click the cluster from which you want to delete ESXi servers.
5. In the **ESXi servers** section, select the servers that you want to delete and click **Delete**.
6. Click **Delete** in the **Delete ESXi server** window.

## Results after you delete ESXi servers from Automated instances
{: #vc_removingservers-results}

1. You might experience a slight delay on the console, while the instance status changes from **Available** to **Modifying**. Allow the operation to complete before you make more changes to the instance.
2. You are notified by email that your request to delete ESXi servers is being processed. On the console, the status of the cluster that is associated with the ESXi servers is changed to **Modifying**.
3. The ESXi servers are fully reclaimed by IBM Cloud infrastructure at the end of the IBM Cloud infrastructure billing cycle, which is typically 30 days.

   You are billed until the end of the IBM Cloud infrastructure billing cycle for the deleted ESXi servers.
   {: note}

## Related links
{: #vc_removingservers-related}

* [VCF for Classic - Automated BOM](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_bom&format=markdown)
* [Planning for Automated instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_planning&format=markdown)
* [Ordering Automated instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-req&format=markdown)
* [Deleting clusters from Automated instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_deletingclusters&format=markdown)
* [Place a host in maintenance mode](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/esx-upgrade/upgrading-esxi-hosts-upgrade/how-to-upgrade-hosts-by-using-esxcli-commands-upgrade/place-a-host-in-maintenance-mode-upgrade.html){: external}
* [Enhanced vMotion Compatibility (EVC) processor support](https://knowledge.broadcom.com/external/article?legacyId=1003212){: external}