VMGuru.nl – I choose (a virtual) life!

While I was updating the Determining VMware vCenter and ESX Build Numbers post I thought I would semi-automate the updating of the post with new build numbers for new releases, while working on it I started too fill an excel sheet and ended up with an excel sheet with the following products and build numbers for easy reference:

VMware vSphere 4 Suite (combines several products)
VMware Infrastructure 3 Suite (combines several products)
Cisco Nexus v1000 (1.0)
VMware ESXi (4.0, 3.5, 3.0)
VMware ESX  (4.0, 3.5, 3.0, 2.5, 2.0, 1.5, 1.0)
VMware Server (2.0, 1.0)
VMware vCenter Server (4.0, 2.5, 2.0)
VMware vCenter Converter Standalone (4.0, 3.0)
VMware vCenter Lab Manager (4.0, 3.0, 2.5, 2.4)
VMware vCenter Site Recovery Manager (4.0, 1.0)
VMware vCenter Server Heartbeat (5.5)
VMware vCenter Lifecycle Manager (1.0)
VMware vCenter CapacityIQ (1.0)
VMware vCenter AppSpeed (1.0)
VMware vCenter Chargeback (1.0)
(more…)

Update April 22th 2009: Today the rumor mentioned below was confirmed during the vSphere 4 launch.

Rumor in the VMware community has it that the next version of VMware ESX, vSphere, has very limited support for the VMware management and automation suite. vSphere will of course be available with vCenter for basic management and automation tasks but the rest of VMware’s great product suite is not supported in the initial release of vSphere.

So there won’t be support for:

• VMware vCenter Site Recovery Manager
• VMware vCenter Lab Manager
• VMware vCenter Lifecycle Manager
• VMware vCenter Stage Manager
• VMware View

In my opinion this is a mistake. I understand the pressure is on and VMware should  release a new version fast to challenge the competition. But releasing a product which does not support the majority of your former product suite is not a clever move.

From what I understand this is also a discussion within VMware so let’s hope VMware gets wiser and postpones the release or add support for the VMware Management & Automation suite soon.