<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Critical ESX 3.5 Update 2 bug gives many users a nasty surprise</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/virtualization-pro/critical-esx-35-update-2-bug-gives-many-users-a-nasty-surprise/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/virtualization-pro/critical-esx-35-update-2-bug-gives-many-users-a-nasty-surprise/</link>
	<description>A SearchVMware.com blog</description>
	<pubDate>Mon, 09 Nov 2009 19:08:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Esiebert7625</title>
		<link>http://itknowledgeexchange.techtarget.com/virtualization-pro/critical-esx-35-update-2-bug-gives-many-users-a-nasty-surprise/#comment-72</link>
		<dc:creator>Esiebert7625</dc:creator>
		<pubDate>Tue, 12 Aug 2008 18:52:36 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/virtualization-pro/critical-esx-35-update-2-bug-gives-many-users-a-nasty-surprise/#comment-72</guid>
		<description>I would say the same holds true for any big company, Microsoft however is to dominate a player to have anything really effect them all that much. VMware can't afford to be making major mistakes like this, of course they will deliver a correction but the damage is already done and their reputation is tarnished. This effected a lot of customers in a bad way, hopefully they learn from the mistakes they made with this and change in a way that is beneficial for future releases of the product.</description>
		<content:encoded><![CDATA[<p>I would say the same holds true for any big company, Microsoft however is to dominate a player to have anything really effect them all that much. VMware can&#8217;t afford to be making major mistakes like this, of course they will deliver a correction but the damage is already done and their reputation is tarnished. This effected a lot of customers in a bad way, hopefully they learn from the mistakes they made with this and change in a way that is beneficial for future releases of the product.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick Vanover</title>
		<link>http://itknowledgeexchange.techtarget.com/virtualization-pro/critical-esx-35-update-2-bug-gives-many-users-a-nasty-surprise/#comment-71</link>
		<dc:creator>Rick Vanover</dc:creator>
		<pubDate>Tue, 12 Aug 2008 17:58:50 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/virtualization-pro/critical-esx-35-update-2-bug-gives-many-users-a-nasty-surprise/#comment-71</guid>
		<description>This is unfortunate, but VMware will deliver a correction. I want to play the devil's advocate here, what if this were Microsoft?</description>
		<content:encoded><![CDATA[<p>This is unfortunate, but VMware will deliver a correction. I want to play the devil&#8217;s advocate here, what if this were Microsoft?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->