<?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: Technical Reasons Not To Upgrade to vSphere Immediately: Product Compatibility</title>
	<atom:link href="http://vmetc.com/2009/06/18/technical-reasons-not-to-upgrade-to-vsphere-immediately-product-compatibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://vmetc.com/2009/06/18/technical-reasons-not-to-upgrade-to-vsphere-immediately-product-compatibility/</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: Dracolith</title>
		<link>http://vmetc.com/2009/06/18/technical-reasons-not-to-upgrade-to-vsphere-immediately-product-compatibility/comment-page-1/#comment-3791</link>
		<dc:creator>Dracolith</dc:creator>
		<pubDate>Thu, 25 Jun 2009 00:39:41 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=4093#comment-3791</guid>
		<description>New technical reason: In ESX3i,  free version, foundation, and standard you can hot-add virtual disks and increase their size no  license requirement.&lt;br&gt;&lt;br&gt;In vSphere  ESXi4 it doesn&#039;t work.  You need an advanced license  for all hot add operations, even just adding a VMDK. &lt;br&gt;&lt;br&gt;Tried it in the free version, verified it doesn&#039;t work.   The VMware comparison chart for vSphere features lists it as an &quot;Advanced&quot; feature.</description>
		<content:encoded><![CDATA[<p>New technical reason: In ESX3i,  free version, foundation, and standard you can hot-add virtual disks and increase their size no  license requirement.</p>
<p>In vSphere  ESXi4 it doesn&#39;t work.  You need an advanced license  for all hot add operations, even just adding a VMDK. </p>
<p>Tried it in the free version, verified it doesn&#39;t work.   The VMware comparison chart for vSphere features lists it as an &#8220;Advanced&#8221; feature.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dracolith</title>
		<link>http://vmetc.com/2009/06/18/technical-reasons-not-to-upgrade-to-vsphere-immediately-product-compatibility/comment-page-1/#comment-2688</link>
		<dc:creator>Dracolith</dc:creator>
		<pubDate>Wed, 24 Jun 2009 18:39:41 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=4093#comment-2688</guid>
		<description>New technical reason: In ESXi,  free version you can hot-add virtual disks and increase their size no  license requirement.&lt;br&gt;&lt;br&gt;In vSphere it doesn&#039;t work.  You need an advanced license.</description>
		<content:encoded><![CDATA[<p>New technical reason: In ESXi,  free version you can hot-add virtual disks and increase their size no  license requirement.</p>
<p>In vSphere it doesn&#39;t work.  You need an advanced license.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rbrambley</title>
		<link>http://vmetc.com/2009/06/18/technical-reasons-not-to-upgrade-to-vsphere-immediately-product-compatibility/comment-page-1/#comment-2680</link>
		<dc:creator>rbrambley</dc:creator>
		<pubDate>Tue, 23 Jun 2009 01:10:43 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=4093#comment-2680</guid>
		<description>Carlo, Dracolith,&lt;br&gt;&lt;br&gt;Thanks for adding a few other, equally important reasons.</description>
		<content:encoded><![CDATA[<p>Carlo, Dracolith,</p>
<p>Thanks for adding a few other, equally important reasons.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dracolith</title>
		<link>http://vmetc.com/2009/06/18/technical-reasons-not-to-upgrade-to-vsphere-immediately-product-compatibility/comment-page-1/#comment-2673</link>
		<dc:creator>Dracolith</dc:creator>
		<pubDate>Fri, 19 Jun 2009 00:34:27 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=4093#comment-2673</guid>
		<description>I think the biggest technical reason of all is ESX 4 has basically a rewritten kernel,&lt;br&gt;it&#039;s a major change, and many enterprises will want to thoroughly test it under&lt;br&gt;conditions similar to the production load,  to ensure it&#039;s actually stable, and won&#039;t&lt;br&gt;present unknown issues.&lt;br&gt;&lt;br&gt;Of course there are non-technical reasons also,  like  the VMware admins aren&#039;t familiar with or trained on how to manage the new version yet,  people need to adapt to and understand the differences, some organizations will want their admins trained on it before making a plan to move their production servers to the new version.</description>
		<content:encoded><![CDATA[<p>I think the biggest technical reason of all is ESX 4 has basically a rewritten kernel,<br />it&#39;s a major change, and many enterprises will want to thoroughly test it under<br />conditions similar to the production load,  to ensure it&#39;s actually stable, and won&#39;t<br />present unknown issues.</p>
<p>Of course there are non-technical reasons also,  like  the VMware admins aren&#39;t familiar with or trained on how to manage the new version yet,  people need to adapt to and understand the differences, some organizations will want their admins trained on it before making a plan to move their production servers to the new version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ccostan</title>
		<link>http://vmetc.com/2009/06/18/technical-reasons-not-to-upgrade-to-vsphere-immediately-product-compatibility/comment-page-1/#comment-2671</link>
		<dc:creator>ccostan</dc:creator>
		<pubDate>Thu, 18 Jun 2009 13:27:54 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=4093#comment-2671</guid>
		<description>Rich, &lt;br&gt;&lt;br&gt;Another technical reason that I have been running into is Ranger Pro. :( Clients that have become very heavily invested in using VizionCore&#039;s RangerPro for their virtual backup strategy are now stuck in the lurch with RangerDPP still only in BETA and the old RangerPro not compatible with vSphere.&lt;br&gt;&lt;br&gt;This has also made them begin to start looking at Veeam as an alternative which already has vSphere support.&lt;br&gt;&lt;br&gt;CARLO.</description>
		<content:encoded><![CDATA[<p>Rich, </p>
<p>Another technical reason that I have been running into is Ranger Pro. <img src='http://vmetc.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' />  Clients that have become very heavily invested in using VizionCore&#39;s RangerPro for their virtual backup strategy are now stuck in the lurch with RangerDPP still only in BETA and the old RangerPro not compatible with vSphere.</p>
<p>This has also made them begin to start looking at Veeam as an alternative which already has vSphere support.</p>
<p>CARLO.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

