VMware recertification policy requirement is wrong-minded and a de-valuation of products which are already purchased and paid for

[unsichtbare]

THe VMware recertification policy requirement is a prime example of VMware treating its customers badly and de-valuing products which are already purchased and paid for! The most recent example of VMware de-valuing client investment in its product was the vRAM requirement introduced with vSphere 5.1 and withdrawn shortly thereafter when VMware got its a** handed to it by many significant and widely-publicized clients.

Because there was no stated expiration at the time all of us received our VCP certifications, the correct (and polite) way to introduce a recertification requirement would be on all VCP certifications moving forward. There is, after all, limited value in a previous VCP certification, like VCP 3, when there are newer VCP certifications available. This move, plain and simple, is designed to generate revenue for VMware prior to the availability of VCP 6, and has no relation to the knowledge and competence of existing VCP holders.

At the very least, VMware ought to extend the recertification deadline past the availability of VCP 6.

I object and I hope others do too!

[scott28tt]

vRAM was new to vSphere 5.0 and was removed at the launch of vSphere 5.1 - it was removed because partners/customers needed it.

Recertification is not exclusive to VMware, it's been used by many other IT vendors for years. It was announced as a policy 1 year ago.

I recertified recently by passing the VCP550D exam, this exam was created as partners/customers needed it.

By passing it, all my VCPs are extended for 2 years, from VCP2 through to VCP5-DCV.

The recertification deadline has been pushed back from March 10th to May 8th, because partners/customers needed it.

VCP6-DCV availability and upgrade/migration paths will be announced soon.

[unsichtbare]

Thank you for reminding me that vRAM was a 5.0 issue. It was removed because VMware suffered an almost 20% loss in value based on the public announcement by major users (like PayPal) of migration to other platforms.

I have and will re-certify (no matter how much I object) and also get some form of the VCP 6.

My objection stems from VMware's retroactive de-valuation of a product I have already paid for. I don't recall any statement during the VCP 3, 4, or 5 process stating that the certification may expire at VMware's discretion. The correct and polite way to implement this policy would be to announce the recertification requirement on the new version of the VCP.

[scott28tt]

VMware's share price prior to the launch of vSphere 5.0 was around $76. The next time it fell below that price was in February 2013, 5 months after the launch of vSphere 5.1. VMware revenues grew by 22% between 2011 and 2012.

Anyway, it's clear that you don't agree with the recertification policy. It was announced 1 year ago, there was a lot of discussion about it at the time, but most people seem to have gotten used to the idea.

[unsichtbare]

On July 22, 2011 VMware shares were trading at 106.72, on August 19, 2011, they were down to 76.76. I interpret this precipitous fall to the public loss of customers due to the perceived devaluation of vRAM. Source: Google "vmware share price"

I am merely stating that while I have and will comply with the recertification policy, I find it objectionable for previously-issued (and paid for) products.

Furthermore, I feel that many one-VCP recipients will choose not to recertify, drastically trimming the ranks of those who VMware regards as VCP Certified.

While this may be good for you and I (as those who will maintain their certs no matter what), it may not be good for the industry or ultimately, VMware.

[scott28tt]

I had thought that 5.0 was announced at VMWorld at the end of August 2011, but now see it was on July 12th 2011 - thanks for the correction.

[unsichtbare]

As you know, I had forgotten that vRAM was a part of 5.0. I guess I associate all bad things from VMware with 5.1!