VMware Cloud Foundation 4.4 End of Life: 3-Month Action Plan

The Reality of the September 30, 2024 Deadline

VMware Cloud Foundation 4.4 reaches end of life (EOL) on September 30, 2024. After that date, Broadcom will no longer provide patches, bug fixes, or technical support for this release. Because 4.4 is not an LTS (long-term support) release, there is no extended support option from the vendor. The latest version in this line is 4.4.1, but that too will eventually reach EOL.

For most organizations, a full migration to a newer release before the deadline is no longer realistic given the typical timeframe. However, that does not mean you are out of options. With three months left, you can take focused steps to reduce risk and keep your environment running safely.

What Changes on September 30, 2024

On the EOL date, the following support services end:

• No more security patches or hotfixes.
• No more bug fixes for any issues discovered after that date.
• No access to technical support from Broadcom for version 4.4.
• No new feature updates.

Any systems still running 4.4 after September 30 will be operating without official vendor support. This introduces compliance, security, and operational risks that must be managed.

Immediate Actions: The Next Three Months

Use the following week-by-week checklist to get ahead of the deadline. Adjust based on your estate size and complexity.

Weeks 1–2: Inventory and Assess

• Identify every instance of VMware Cloud Foundation 4.4 in your environment. Include production, development, and testing instances.
• Document version numbers (4.4, 4.4.1, etc.) and any dependencies.
• Determine which workloads are running on those instances and their criticality.
• Check current support contract status and renewal dates.

Weeks 3–4: Risk Analysis and Planning

• Assess the impact of running unsupported software. Consider security vulnerabilities, compliance requirements (PCI-DSS, SOC 2, etc.), and insurance policies.
• Identify which workloads can be migrated to a supported version (4.5 or later) and which cannot due to technical constraints or time.
• For workloads that must remain on 4.4 post-EOL, plan isolation and hardening measures.

Weeks 5–6: Isolation and Hardening

• Place 4.4 instances in a restricted network segment with limited inbound/outbound access.
• Apply any available last patches (from 4.4.1) and configuration hardening.
• Implement additional monitoring and logging for anomalous activity.
• Review firewall rules, access controls, and authentication mechanisms.

Weeks 7–8: Documentation and Reporting

• Create a formal risk register entry for the EOL status. Document all affected systems, their criticality, and the mitigation steps taken.
• Update your business continuity and disaster recovery plans to account for unsupported software.
• Prepare a report for auditors, insurers, and management explaining the situation and your response.

Weeks 9–10: Secure Third-Party Support

• Evaluate third-party support providers, such as 3rd Party Support, that can continue to provide patches, security updates, and technical assistance for VMware Cloud Foundation 4.4 after the vendor's support ends.
• Ensure the third-party support covers the specific components and versions you are running.
• Finalize contracts so support is in place effective October 1, 2024.

Weeks 11–12: Final Testing and Cutover

• Test any remaining migrations to supported versions.
• Verify that third-party support activation is seamless.
• Confirm that monitoring, logging, and access controls are functioning as expected.
• Communicate the EOL status and your mitigation plan to all stakeholders.

Beyond September 30, 2024

Even with these measures, running an unsupported release carries inherent risk. Third-party support can address the most critical gap—access to patches and expert assistance—but it does not eliminate the need to plan a future migration. Use the breathing room provided by a third-party support contract to schedule an upgrade to a supported release within the next 6–12 months.

Next Steps

If you have not yet started your EOL preparation, begin with the inventory today. For organizations that need to keep VMware Cloud Foundation 4.4 running safely past September 30, 2024, a third-party maintenance agreement offers a viable path.

Contact us to discuss how we can help you bridge the gap from EOL to your next supported release.