ESX 4.1 is the Last ESX

Thought I would write this post to let people know about VMware’s plans to drop ESX. It has been in the pipeline for quite some time, but I know it is still a surprise to some people.

This is an extract from the VMware Blog Site that clarifies the end of ESX. “ESX 4.1 is the last ESX! What do i do now?”

With the release of VMware vSphere 4.1, we announced that 4.1 will be the last vSphere version to support both the ESX and ESXi hypervisor architectures. Going forward customers will be able to deploy vSphere only using ESXi. Although the infrastructure management tasks once performed by the Service Console are now handled by tasks running under the VMkernel, some ESX users may still depend on the custom scripts, third-party products, or operational procedures that use the Service Console. This means that upgrading to vSphere 4.1 is the perfect time to start planning on migrating to the ESXi architecture and eventually break all dependencies on the Service Console once and for all. Here is a quick summary of what you should look into:

Replace COS-based hardware monitoring with CIM-based tools
Replace COS-based backup technologies with products that use the vStorage APIs
Replace COS-based scripts using the VMware Management Assistant, the vCLI, or vSphere PowerCLI

If you would like to read the whole blog article click here

, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

No comments yet.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Copyright David Hill

Powered by WordPress. Designed by Woo Themes