The vSphere 6.0 Launch and The Misinformation Effect

Have you ever wondered what happens if you give 10.000 people access to an open-beta that is supposed to be under NDA?

Firstly, the NDA is no-go from the get-go. There is no way you can claim that you actually expect 10.000 people to not talk about something they know about. VMware vSpere 6.0 was the worst kept secret ever, for a reason. It might have been planned that way all along for all I know, but if that was the case, the NDA should never have been in place to begin with.

Secondly, what happens when said product finally gets announced, and scores of people have pre-made blog content about all the new, and presumably secret, features? A lot of it is wrong, because people have been writing about features that have either been dropped or changed come release time.

So, now what do you do? Well, VMware decided to “Clarify the misinformation”. I’m sorry, but all of this reads as a text-book way of not handling things.

So, here is my own personal advice to VMware for the next round:

Do

  • Decide on a beta format. If you do an open beta, drop the NDA and have people discuss it. If you do a closed beta, that’s fine too, invite people and slap a NDA on it. No problem. You can’t really have it both ways.

  • If you solicit blog posts for publicity reasons during a launch event, do the bloggers a favor and tell them, beforehand, if something has changed or been dropped since the beta. If you don’t trust them to not leak information, what was the NDA worth to begin with?

Don’t

  • Don’t solicit blog posts, and then call it misinformation if things have changed, and you haven’t informed anyone of it. That’s just plain rude.

Come on VMware, you have been able to do things like this before, without this kind of problems. I’m sure you can do it again. As for the title for this post? Have a look at The misinformation effect.

Need the vSphere Client? VMware Has You Covered.

One of the more popular posts, currently in third place, on vNinja.net is my list of vSphere Client direct download links posted back in March 2012.

Thankfully William Lam had the same idea, and got a new Knowledgebase Article published: Download URLs for VMware vSphere Client (2089791). Please use that article as the official download link documentation from now on.

VMware Certified Professional Recertification

Perkins-Tryon High School Graduation 2010 (c) Paul Robinson

VCP5VMware has announced a Recertification Policy for it’s VMware Certified Professional program, effective as of March 10, 2014.

In short, it means that you are no longer a VCP(x) for life, but need to recertify every 2 years, unless you take a VCAP exam during the same period. If you do not upgrade your certification, your VCP status is revoked. For all the details, have a look at Recertification Policy: VMware Certified Professional.

It also means that anyone currently holding a VCP certification, needs to recertify before March 10th 2015, regardless of when the initial VCP was obtained.  Those obtaining a VCP after March 10th, will have to recertify within two years of obtaining the initial VCP.

I think this is a good move, and is on par with other technical certifications like ones offered by HP, Cisco and CompTia (A+). After all, we live in an ever evolving technical market where continuous change happens and if you are not able to keep current, the certification holds no real merit.

This change from VMware also means that as long as you recertify your VCP exam within the two year period, there will not be a course requirement to upgrade; schedule your exam and you are ready to go. Previously you would get a grace period, after a new major release of vSphere, where you could re-certify without having to attend a new class. With this change, you have two years, and that is it.

In a way, this also means that VMware will have to commit to major releases, with upgraded VCP versions, more frequently than every 2 years.

Looking at the last two vSphere releases, this seems to indicate a change in release cycles for major versions:

  • vSphere 4 was released  May 21st 2009.
  • vSphere 5 was released July 12th 2011
  • vSphere 5.5 was released September 22nd 2013.

Remember, vSphere 5.5 is covered by the VCP5 (ok, there is a VCP510 and VCP550 version) certification, so if this policy was in place in 2011 when vSphere 5 was released, there would not be any upgraded VCP certification to take within the two year validity period.

Update:What if VMware had called an old VCP certification “retired” instead of “expired”, would that cause less outrage and emotion?

Header image used under Creative Commons License (c) Paul Robinson