<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: VirtualCenter 2.0.2 Web Interface does not work after upgrade</title>
	<atom:link href="http://vmetc.com/2008/10/01/virtualcenter-202-web-interface-does-not-work-after-upgrade/feed/" rel="self" type="application/rss+xml" />
	<link>http://vmetc.com/2008/10/01/virtualcenter-202-web-interface-does-not-work-after-upgrade/</link>
	<description>Go Green with Virtualization. Go UGLY Green with vmetc.com.</description>
	<lastBuildDate>Wed, 25 Jan 2012 13:41:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Eric Siebert</title>
		<link>http://vmetc.com/2008/10/01/virtualcenter-202-web-interface-does-not-work-after-upgrade/comment-page-1/#comment-1336</link>
		<dc:creator>Eric Siebert</dc:creator>
		<pubDate>Wed, 01 Oct 2008 21:51:11 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=1021#comment-1336</guid>
		<description>Yeah it bit a lot of people when they tried upgrading after 2.0.2U1 was released. It&#039;s a shame it got past their QA and even more shameful that it took them so long to resolve it. Hopefully they&#039;ve learned from the last time-bomb snafu and implement better QA testing in the future.</description>
		<content:encoded><![CDATA[<p>Yeah it bit a lot of people when they tried upgrading after 2.0.2U1 was released. It&#8217;s a shame it got past their QA and even more shameful that it took them so long to resolve it. Hopefully they&#8217;ve learned from the last time-bomb snafu and implement better QA testing in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Siebert</title>
		<link>http://vmetc.com/2008/10/01/virtualcenter-202-web-interface-does-not-work-after-upgrade/comment-page-1/#comment-5454</link>
		<dc:creator>Eric Siebert</dc:creator>
		<pubDate>Wed, 01 Oct 2008 21:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=1021#comment-5454</guid>
		<description>Yeah it bit a lot of people when they tried upgrading after 2.0.2U1 was released. It&#039;s a shame it got past their QA and even more shameful that it took them so long to resolve it. Hopefully they&#039;ve learned from the last time-bomb snafu and implement better QA testing in the future.</description>
		<content:encoded><![CDATA[<p>Yeah it bit a lot of people when they tried upgrading after 2.0.2U1 was released. It&#8217;s a shame it got past their QA and even more shameful that it took them so long to resolve it. Hopefully they&#8217;ve learned from the last time-bomb snafu and implement better QA testing in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich</title>
		<link>http://vmetc.com/2008/10/01/virtualcenter-202-web-interface-does-not-work-after-upgrade/comment-page-1/#comment-1335</link>
		<dc:creator>Rich</dc:creator>
		<pubDate>Wed, 01 Oct 2008 20:49:48 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=1021#comment-1335</guid>
		<description>Thanks Eric. I guess it just has not been common for me.</description>
		<content:encoded><![CDATA[<p>Thanks Eric. I guess it just has not been common for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rbrambley</title>
		<link>http://vmetc.com/2008/10/01/virtualcenter-202-web-interface-does-not-work-after-upgrade/comment-page-1/#comment-5455</link>
		<dc:creator>rbrambley</dc:creator>
		<pubDate>Wed, 01 Oct 2008 20:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=1021#comment-5455</guid>
		<description>Thanks Eric. I guess it just has not been common for me.</description>
		<content:encoded><![CDATA[<p>Thanks Eric. I guess it just has not been common for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Siebert</title>
		<link>http://vmetc.com/2008/10/01/virtualcenter-202-web-interface-does-not-work-after-upgrade/comment-page-1/#comment-1334</link>
		<dc:creator>Eric Siebert</dc:creator>
		<pubDate>Wed, 01 Oct 2008 18:37:05 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=1021#comment-1334</guid>
		<description>That&#039;s actually a pretty common one that was first seen right after 2.0.2 Update 1 came out about a year ago. Here&#039;s the Vmtn thread that first identified the problem.

http://communities.vmware.com/thread/110156

VMware was aware of the problem right away but it wasn&#039;t fixed until 2.0.2 Update 4.</description>
		<content:encoded><![CDATA[<p>That&#8217;s actually a pretty common one that was first seen right after 2.0.2 Update 1 came out about a year ago. Here&#8217;s the Vmtn thread that first identified the problem.</p>
<p><a href="http://communities.vmware.com/thread/110156" rel="nofollow">http://communities.vmware.com/thread/110156</a></p>
<p>VMware was aware of the problem right away but it wasn&#8217;t fixed until 2.0.2 Update 4.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Siebert</title>
		<link>http://vmetc.com/2008/10/01/virtualcenter-202-web-interface-does-not-work-after-upgrade/comment-page-1/#comment-5456</link>
		<dc:creator>Eric Siebert</dc:creator>
		<pubDate>Wed, 01 Oct 2008 18:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=1021#comment-5456</guid>
		<description>That&#039;s actually a pretty common one that was first seen right after 2.0.2 Update 1 came out about a year ago. Here&#039;s the Vmtn thread that first identified the problem.

http://communities.vmware.com/thread/110156

VMware was aware of the problem right away but it wasn&#039;t fixed until 2.0.2 Update 4.</description>
		<content:encoded><![CDATA[<p>That&#8217;s actually a pretty common one that was first seen right after 2.0.2 Update 1 came out about a year ago. Here&#8217;s the Vmtn thread that first identified the problem.</p>
<p><a href="http://communities.vmware.com/thread/110156" rel="nofollow">http://communities.vmware.com/thread/110156</a></p>
<p>VMware was aware of the problem right away but it wasn&#8217;t fixed until 2.0.2 Update 4.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

