A client of mine recently had their vCenter 5.0 appliance replaced with a new vCenter 5.1 appliance, something vCenter Operations Manager did not enjoy. In this case the original vCenter 5.0 Appliance was turned shut down, a new 5.1 Appliance deployed, with the same IP as the old one, and then configured. Naturally the existing hosts were added to the fresh vCenter, clusters recreated and in general everything was reconfigured.
SearchserverVirtualization published an article today called «Experts weigh in on CTO Herrod’s departure, future of VMware» where I have been quoted in regard toSteve Herrod’s departure from VMware. While the quote itself is correct, I feel that there is a need to further expand on what I said, in the context it was given in. So here it is, my entire response: My reaction to Steve Herrods departure is probably on par with just about everyone else's, one of surprise.
In order to be able to deploy vCenter Operations Manager, the ESXi host it is deployed to needs to be managed by a vCenter. At first glance, that seems like a fair and pretty straight forward requirement, right? But, is it? While I can see the need for a vCenter in the environment that vCenter Operations Manager is supposed to monitor, I don´t understand why the host you want to deploy the vApp on has to be managed by a vCenter instance as well?
vOPS 6.3 Environment Explorer Yesterday fellow vExpert Mattias Sundling gave me a little pre-release briefing of the new Dell/VKernel vOPS Server Explorer 6.3 release. While I don´t normally do press release posts like these, I´m willing to make an exception in this case. Not only is vOPS Server Explorer 6.3 available in a free version, with the familiar tools from previous versions, the new release also comes armed with a couple of new interesting tools in the suite:
Christopher Kusek, who runs pkguild.com, has just announced that he is running a contest where you can win a VMware Workstation 9 license. Seeing that announcement, and the fact that Christopher was nice enough to mention both me and vNinja.net in it, I have decided to also give away a license that has been lingering unused in my possession way to long. Instead of running my own contest, my license has been added to the existing contest so head on over there to read all the details.
One of the smaller improvements in vSphere 5 was the introduction of the «Virtual machine disks consolidation is needed» configuration alert if vSphere determines that there are orphaned snapshots for a given VM. Previous versions does not show this warning message, and datastore usage could potentially skyrocket for no apparent reason if something continues to create snapshots that are not properly cleaned up when they are no longer in use.
A little while ago VMware announced Project Nee, something I was, and still am, pretty excited about. This afternoon I finally got access to the Hands-on Labs Online Beta part of Project Nee, and I have to say, this looks incredibly promising and useful. At the moment, the available labs are:Cloud Infrastructure: HOL-INF-02 - Explore vSphere 5.1 Distributed Switch (vDS) New Features This lab explores the new features of the vSphere Distributed Switch (vDS).
VMware vSphere Health Check is a service provided by VMware Professional Services, either by their own consultants or by a consultant from a VMware Certified Solution Provider. I´m lucky enough to be employed by a Premier VMware Solution Provider who offers this service to our customers, and I´ve completed a fair number of these health checks in the last couple of months. You might ask what the value of the Health Check is, and for the end customer it´s pretty clear cut.
The new vCenter Operations Manager 5.6 is now generally available, and one of many improvements from v5.5 is the new licensing scheme. The new foundation edition, is the new entry-level edition which from now on is included in every licensed vSphere edition free of charge. That´s right, you can now run vCenter Operations Manager 5.6 Foundation without purchasing any additional licenses. vCenter Operations Manager now comes in the following flavors:
One of my clients has recently been having issues with their storage solution, and wanted to export the events from vCenter that show storage performance degradation, to aid in troubleshooting with the vendor. For some reason, and I have yet to confirm that this is a bug with the vCenter 5.0 appliance or the vCenter Desktop Client, when an event export is done, the storage related events are not exported with the rest of the events.