[WP_IMAGE]VMware vSphere 5.0 does away with the ESX hypervisor. Starting now, the name of the game is ESXi. VMware has neatly outlined the differences here.Bottom line: if your organization was using third-party tools that plugged in via the ESX Service Console, you should check to see if those tools have been approved for use in the VMkernel in ESXi.I have to admit that until vSphere 5.0 was released, I had only passing experience with ESXi. When it was released as a free, standalone hypervisor in 2008, in my mind that meant it was inferior to the not free ESX. It turns out that was a mistaken impression. During my recent tests with vSphere 5.0, I was easily able to use my ESX-honed skills in the ESXi environment.I
’
ll reiterate here that I
’
m generally in favor of VMware taking greater control of the hypervisor environment in the form of approving third party tools for use in the VMkernel environment provided by the ESXi hypervisor. As long as technical
–
not competitive or marketing
–
hurdles must be cleared to gain acceptance, I think the change to the ESXi-only environment is a good one.