Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

End of Availability and End of Support Life for VMware vCloud Director 5.1 Standalone (2057589)

Purpose

This article provides information on the End of Availability and End of Support Life for VMware vCloud Director 5.1 Standalone.

Details

About the End of Availability and End of Support Life

VMware is moving toward more simplified packaging and unified licensing of our cloud stack. Driven by this commitment, we're implementing an integrated approach to the packaging of all of the essential capabilities for building a software-defined data center.
 
As part of this key initiative, VMware is making these packaging changes to make this technology more easily accessible:
  • vCloud Director 5.5 will be available only as part of vCloud Suite 5.5. 
  • VMware has announced the End of Availability (“EOA”) of the VMware vCloud Director 5.1 for sale as a standalone product effective September 19, 2013.
  • Existing customers can maintain their vCloud Director through either the entitlement program or while converting to vCloud Suite with the Fair Value Conversion Program.

VMware will be extending the Support for vCloud Director 5.5. Generally, as per the VMware Enterprise Application Support Policy, VMware will support the current release of software for 2 years from the general availability of the Major Release, or the latest released version for 12 months. However, VMware will provide extended support for vCloud Director 5.5 with support available for 4 years from general availability. Customers will be able to get telephone and Internet support for vCloud Director 5.5 until their current contract expires or until Q3, 2017, whichever is earlier.

The End of Support date for vCloud Director 5.1 remains as September 10, 2014.

FAQs

Who is entitled to vCloud Director 5.5?
Existing customers of vCloud Director 5.1 who are currently under an active Support and Subscription (SnS) contract are entitled to upgrade to vCloud Director 5.5.
 
What license key is required to upgrade to vCloud Director 5.5? 
Existing customers who are currently under an active SnS contract can use their vCloud Director 5.1 license key.
 
What is the migration path for customers who own vCloud Director 5.1 standalone licenses?
There are two options for existing for customers of vCloud Director 5.1 standalone product SKUs: 
  • Existing customers can maintain their vCloud Director investment by taking their support and subscription (SnS) entitlement to vCloud Director 5.5. All existing customers with an active Support and Subscription contract are entitled to vCloud Director 5.5.
  • If the customer wants to upgrade to vCloud Suite, VMware offers customers a Fair Value Conversion process. For more information, see VMware Fair Value Conversion Program.
When is the last day that customers can purchase vCloud Director 5.1 standalone product? 
vCloud Director will no longer be available for sale as standalone SKUs as of September 19, 2013. After that, customers can access equivalent functionality in vCloud Suite Standard, Advanced or Enterprise editions.
 
When will support and subscription (SnS) services for vCloud Director 5.1 standalone product end? 
The End of Support for vCloud Director 5.1 remains as September 10, 2014. For more information, see the VMware Lifecycle Product Matrix.
 
Will vCloud Director continue to operate even after the end-of-support date is passed? 
Yes, the product will continue to function but VMware will not provide access to support services, patches or maintenance releases.

Additional Information

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 6 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 6 Ratings
Actions
KB: