> ## Content Index > Fetch the complete content index at: https://www.mohammadsiddiqui.com/llms.txt > Use this file to discover other available public pages before exploring further. # Cloud Director 10.6.2: A Migration Release, and a Lifecycle Statement - URL: https://www.mohammadsiddiqui.com/cloud-director-10-6-2-a-migration-release-and-a-lifecycle-statement/ - Published: 2026-09-08T04:50:24.000Z - Updated: 2026-09-19T04:51:14.000Z - Description: 10.6.2 shares its end-of-life date with VCF 9.1. The migration timeline is no longer entirely yours to set - Author: Mohammad Siddiqui - Tags: lifecycle, architecture VMware Cloud Director 10.6.2 is generally available, and Broadcom's own summary of it is unusually direct: this is a migration release. It hardens the platform and prepares your infrastructure for VCF 9.1 and the move to VCF Automation. If you run VCD, either as a service provider or as a large enterprise with VCD-based multi-tenancy, there is one fact in this release that matters more than the feature list. Cloud Director 10.6.2 shares its end-of-life date with VCF 9.1 That is a lifecycle statement, not a footnote. VCD's runway is now explicitly tied to a VCF version rather than running on its own schedule. Whatever your migration timeline was, check it against the VCF 9.1 EOL date rather than against a VCD roadmap. ## What changed Three things, in order of how much they should affect your planning. **The migration path to VCF Automation 9.1 is now fully supported, documented and UI-based.** Previously this was a construct-mapping exercise you worked through with your account team. It is now a tool-assisted path with a defined sequence. **Security patches and defect fixes.** The release closes vulnerabilities identified since the previous version and resolves issues reported by providers running VCD in production. If you are staying on VCD for a while yet, that alone justifies the upgrade. **Interoperability validation.** Compatibility with related VMware products is validated for this release, which matters because a migration is exactly the moment you cannot afford an unsupported combination. ## The migration sequence Broadcom describes the path in defined steps. The first one is the interesting one. 1 **Run the Environment Assessment Tool** Collects environment-specific metadata from your VCD deployment. This is the discovery step, and it is what turns a generic migration guide into advice about your estate. 2 **Upgrade to Cloud Director 10.6.2** The hardened baseline. You migrate from here, not from wherever you happen to be now. 3 **Connect the VCF Automation Migration Service to Cloud Director** Then work through the migration step by step through the UI. Run the assessment tool early, well before you plan to migrate anything. It costs nothing, it produces an inventory you will need regardless of when you move, and its output is what tells you whether your construct mapping is straightforward or has awkward corners in it. ## What this means if you carry VCD customers - **The construct-mapping work is now worth starting.** VCD organisations and vDCs onto VCF Automation orgs and projects. That design exercise is independent of when you execute, and doing it early surfaces the tenancy decisions rather than leaving them to migration day. - **The EOL alignment changes the conversation.** "We will look at it eventually" is harder to sustain when the platform's support window is pinned to a specific VCF release. Get the actual date from the Product Lifecycle Matrix and work backwards. - **Upgrade to 10.6.2 even if migration is years away.** Security fixes plus a validated interoperability baseline is worth having regardless, and you cannot start the migration path from an older release. - **Greenfield or in-place remains the first decision.** The tooling supports the move, but it does not make that choice for you, and it is the choice that shapes everything downstream. ## The wider picture Read alongside the VCF Automation work covered earlier in this series, the direction is clear. VCD-based multi-tenancy converges onto VCF Automation's organisation and project model, and Broadcom is now building the tooling to carry people across rather than leaving it as a re-platforming exercise. For service providers that is a significant piece of work with real customer impact, and the migration service maturing is genuinely good news. For enterprises running VCD internally it is a smaller job but the same direction of travel. Either way, the EOL alignment means the timeline is no longer entirely yours to set. ## Sources - [Announcing VMware Cloud Director 10.6.2, Enabling Your Migration to VMware Cloud Foundation 9.1](https://blogs.vmware.com/cloudprovider/2026/09/announcing-vmware-cloud-director-10-6-2-enabling-your-migration-to-vmware-cloud-foundation-9-1.html?ref=mohammadsiddiqui.com) - [VMware Product Interoperability Matrix](https://interopmatrix.broadcom.com/Interoperability?ref=mohammadsiddiqui.com) - [VMware Product Lifecycle Matrix](https://support.broadcom.com/group/ecx/productlifecycle?ref=mohammadsiddiqui.com) \- for the actual EOL dates *Views expressed here are my own and do not represent those of my employer.*