<?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: ESX 3.5 Update 2 and VirtualCenter 2.5 Update 1 configuration note</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/virtualization-pro/esx-35-update-2-and-virtualcenter-25-update-1-configuration-note/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/virtualization-pro/esx-35-update-2-and-virtualcenter-25-update-1-configuration-note/</link>
	<description>A SearchVMware.com blog</description>
	<pubDate>Sat, 28 Nov 2009 19:33:53 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Rick Vanover</title>
		<link>http://itknowledgeexchange.techtarget.com/virtualization-pro/esx-35-update-2-and-virtualcenter-25-update-1-configuration-note/#comment-77</link>
		<dc:creator>Rick Vanover</dc:creator>
		<pubDate>Wed, 03 Sep 2008 02:03:58 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/virtualization-pro/esx-35-update-2-and-virtualcenter-25-update-1-configuration-note/#comment-77</guid>
		<description>[B]Shokk[/B]  - That is exactly where I was. Glad I saved you the 'emergency upgrade'

Cheers.</description>
		<content:encoded><![CDATA[<p><b>Shokk</b>  - That is exactly where I was. Glad I saved you the &#8216;emergency upgrade&#8217;</p>
<p>Cheers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shokk</title>
		<link>http://itknowledgeexchange.techtarget.com/virtualization-pro/esx-35-update-2-and-virtualcenter-25-update-1-configuration-note/#comment-76</link>
		<dc:creator>Shokk</dc:creator>
		<pubDate>Wed, 03 Sep 2008 02:02:32 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/virtualization-pro/esx-35-update-2-and-virtualcenter-25-update-1-configuration-note/#comment-76</guid>
		<description>Wow, sorry for your pain, but thank you for saving my skin.  Was going to make that mistake as past  of an upcoming change control, where we have VC 2.5 U1.</description>
		<content:encoded><![CDATA[<p>Wow, sorry for your pain, but thank you for saving my skin.  Was going to make that mistake as past  of an upcoming change control, where we have VC 2.5 U1.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick Vanover</title>
		<link>http://itknowledgeexchange.techtarget.com/virtualization-pro/esx-35-update-2-and-virtualcenter-25-update-1-configuration-note/#comment-75</link>
		<dc:creator>Rick Vanover</dc:creator>
		<pubDate>Wed, 03 Sep 2008 00:50:05 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/virtualization-pro/esx-35-update-2-and-virtualcenter-25-update-1-configuration-note/#comment-75</guid>
		<description>Beb4vm: VMware says a lot of things, but most importantly in this post is that release notes did not explicitly say such that VirtualCenter will break in this configuration - rather than simply "not compatible"</description>
		<content:encoded><![CDATA[<p>Beb4vm: VMware says a lot of things, but most importantly in this post is that release notes did not explicitly say such that VirtualCenter will break in this configuration - rather than simply &#8220;not compatible&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Beb4vm</title>
		<link>http://itknowledgeexchange.techtarget.com/virtualization-pro/esx-35-update-2-and-virtualcenter-25-update-1-configuration-note/#comment-74</link>
		<dc:creator>Beb4vm</dc:creator>
		<pubDate>Tue, 02 Sep 2008 22:27:02 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/virtualization-pro/esx-35-update-2-and-virtualcenter-25-update-1-configuration-note/#comment-74</guid>
		<description>I find this article interesting because of the fact that the author brought the problem on himself.  VMware has ALWAYS stated that any implementation, upgrade, or install should always be staged with the Virtual Center version equal or higher than the host version.  The FIRST thing the author should have done was upgrade Virtual Center to Update 2.</description>
		<content:encoded><![CDATA[<p>I find this article interesting because of the fact that the author brought the problem on himself.  VMware has ALWAYS stated that any implementation, upgrade, or install should always be staged with the Virtual Center version equal or higher than the host version.  The FIRST thing the author should have done was upgrade Virtual Center to Update 2.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->