Comments on: Is VMware’s apology enough? http://itknowledgeexchange.techtarget.com/server-virtualization/is-vmware%e2%80%99s-apology-enough/ A SearchServerVirtualization.com blog Fri, 27 Nov 2009 08:22:15 +0000 http://wordpress.org/?v=2.6.2 By: Bill http://itknowledgeexchange.techtarget.com/server-virtualization/is-vmware%e2%80%99s-apology-enough/#comment-1497 Bill Mon, 18 Aug 2008 17:22:10 +0000 http://servervirtualization.blogs.techtarget.com/2008/08/14/is-vmware%e2%80%99s-apology-enough/#comment-1497 This is one of the worst one sided articles I have ever seen. I cannot believe that the feeling is that; Okay VMWARE screwed up, we accept the apology and move one. Where is the lawsuit cries? Where is the justification and editorial criticism that needs to be made on this matter. Production Server went down , costing many companies to loose money , and have panick set in as VMWARE did nothing to acknowledge this problem in the early goings. If this was a Microsoft blunder my God, the Executive Team would be in front of Congress... If we must editorialize I/T lets be fair to it all and make blame the game even. This is a serious problem ,the Hypervisor is now more important then hardware it sits on. Having time stamps on these types of technology is so wrong on so many levels. If VMWARE want to continue to be the dominate player it was prior to be no real competition for hypervisors, it has best learn to get rid of these time bombed activation schemes. This is one of the worst one sided articles I have ever seen. I cannot believe that the feeling is that; Okay VMWARE screwed up, we accept the apology and move one. Where is the lawsuit cries? Where is the justification and editorial criticism that needs to be made on this matter.

Production Server went down , costing many companies to loose money , and have panick set in as VMWARE did nothing to acknowledge this problem in the early goings.

If this was a Microsoft blunder my God, the Executive Team would be in front of Congress…

If we must editorialize I/T lets be fair to it all and make blame the game even.

This is a serious problem ,the Hypervisor is now more important then hardware it sits on. Having time stamps on these types of technology is so wrong on so many levels.

If VMWARE want to continue to be the dominate player it was prior to be no real competition for hypervisors, it has best learn to get rid of these time bombed activation schemes.

]]> By: John Smith http://itknowledgeexchange.techtarget.com/server-virtualization/is-vmware%e2%80%99s-apology-enough/#comment-1496 John Smith Fri, 15 Aug 2008 03:37:20 +0000 http://servervirtualization.blogs.techtarget.com/2008/08/14/is-vmware%e2%80%99s-apology-enough/#comment-1496 I disagree with the comment that they were responsive, and had a patch withing 24hrs of the report. I am in Australia and we reported the problem at least 36hrs before the patch came out. We got no responce from VMware until the next day local time, and they gave no suggestions at all about work arounds, or how to patch an environment that was totally on 3.5U2 without widespread outages.... I disagree with the comment that they were responsive, and had a patch withing 24hrs of the report.

I am in Australia and we reported the problem at least 36hrs before the patch came out. We got no responce from VMware until the next day local time, and they gave no suggestions at all about work arounds, or how to patch an environment that was totally on 3.5U2 without widespread outages….

]]> By: Rich http://itknowledgeexchange.techtarget.com/server-virtualization/is-vmware%e2%80%99s-apology-enough/#comment-1495 Rich Thu, 14 Aug 2008 19:53:22 +0000 http://servervirtualization.blogs.techtarget.com/2008/08/14/is-vmware%e2%80%99s-apology-enough/#comment-1495 Eric, Sure VMware could have handled some aspects of this issue better as you point out. Hopefully, they will never have to again deal with a blunder like this and therefore never demonstrate that they have improved their public relations communications process. Improving their internal testing and Q&A process will keep customers and partners from ever needing to know. For my own similar thoughts on this issue and why it happened check out my post at http://vmetc.com/2008/08/13/my-thoughts-on-the-reactions-to-the-esx-35-update-2-bug/ Eric,

Sure VMware could have handled some aspects of this issue better as you point out. Hopefully, they will never have to again deal with a blunder like this and therefore never demonstrate that they have improved their public relations communications process. Improving their internal testing and Q&A process will keep customers and partners from ever needing to know. For my own similar thoughts on this issue and why it happened check out my post at <a href="http://vmetc.com/2008/08/13/my-thoughts-on-the-reactions-to-the-esx-35-update-2-bug/" title="http://vmetc.com/2008/08/13/my-thoughts-on-the-reactions-to-the-esx-35-update-2-bug/" target="_blank">http://vmetc.com/2008/08/13/my-thoughts-…</a>

]]>