{"id":371,"date":"2012-10-03T06:29:00","date_gmt":"2012-10-03T06:29:00","guid":{"rendered":"http:\/\/atumvirtwordpress.azurewebsites.net\/?p=371"},"modified":"2012-10-03T06:29:00","modified_gmt":"2012-10-03T06:29:00","slug":"vmware-misses-the-mark-second-year-in-a-row","status":"publish","type":"post","link":"https:\/\/avtempwp.azurewebsites.net\/2012\/10\/vmware-misses-the-mark-second-year-in-a-row\/","title":{"rendered":"VMware Misses the Mark Second Year in a Row"},"content":{"rendered":"
“Hey, Joe, remember when VMware introduced vRam and we were all totally stoked and excited beyond belief?!”
“Yeah, man that was totally awesome! \u00a0Wait…what?”
“I know…!”
“No, Tad, vRam was terribad. \u00a0So terribad that customers revolted and in vSphere 5.1 they actually removed it entirely.”
“Oh…”<\/p><\/blockquote>\nVMware has received strong recognition among Fortune 500 Companies for good reason – they’ve had a good product for years and they’ve been truly innovative. \u00a0That being said, \u00a0they haven’t been without their faults. \u00a0For some reason, July, August, and September seem to be VMware’s “lets screw with customers” months, possibly because VMworld is around that time. \u00a0Let’s take a look back.<\/div>\n<\/div>\nAfter years<\/u>\u00a0of evangelizing for VMware to get a foot in the door, we finally did, when only a few weeks afterwards we were met with the dastardly August 12 timebomb<\/a>. \u00a0Yes, our perfectly licensed, completely legal copy of ESXi 3.5 all of the sudden exploded in our faces. \u00a0VMware shrugged this off and rode their good name to a recovery, explaining that they had learned their lesson.<\/div>\n<\/div>\nFast forward to June 2011, when it was announced that they’d be changing licensing from socket+core-based licensing to socket-based+vRAM licensing. \u00a0The net result? \u00a0User protest<\/a>. \u00a0And for good reason. Instead of buying two DL380 G6 or G7 servers with 144GB of RAM and each needing two processor licenses, we would have needed three per box. \u00a0It doesn’t take a rocket scientist to recognize the price increase with that one. \u00a0All the while VMware maintained for almost a full month that these were ‘fringe’ cases and that we should just accept it and LIKE it, because after all, they’re VMware, right? \u00a0Microsoft even put out a (now removed) video that introduced “Tad, of VM Limited” to capitalize in a brilliant\u00a0marketing\u00a0campaign. \u00a0Weeks later VMware caved <\/a>and doubled the (egregiously low) limits.<\/div>\n<\/div>\nSurely they’d have learned their lesson? \u00a0Well, without much fanfare it seems VMware has decided to introduce the vSphere Web Client, first with vSphere 5.0 in 2011. \u00a0Yes, in a stunning turn of events, they developed a completely new client to free us from our dependence on Windows forever, to stick a fork in the eye of the evil Microsoft. \u00a0Except. It. Didn’t. \u00a0That is right – what do all “enterprise” web apps have? \u00a0Plugins. \u00a0And lots of them. \u00a0You know that little used feature of the vSphere client called ‘remote console’ – the thing that lets you access your server when VNC\/Remote Desktop isn’t available? \u00a0Plugin. \u00a0Please view in IE, thanks.<\/div>\n