<?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: ESXi 4, Moving VMs to new Storage</title>
	<atom:link href="http://blog.tech4him.com/2010/03/esxi-4-moving-vms-to-new-storage/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tech4him.com/2010/03/esxi-4-moving-vms-to-new-storage/</link>
	<description>A Christian technology chaos wrangler and his thoughts</description>
	<lastBuildDate>Wed, 25 Jan 2012 10:13:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Tom</title>
		<link>http://blog.tech4him.com/2010/03/esxi-4-moving-vms-to-new-storage/comment-page-1/#comment-135</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Fri, 23 Apr 2010 20:00:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tech4him.com/?p=948#comment-135</guid>
		<description>Tim, glad you raised that point. Since we originally investigated what we did in the article, we too found out that the latest VMWare Converter has the Synchronize changed data after conversion option. This is definitely the way to go!

One thing that caused us a little headache is that the newly created vm (destination of the conversion) ends up with a new virtual NIC and as such, the Windows guest O/S sees it as new hardware. Therefore, its a default NIC with DHCP and the works. We had to reconfigure the guest O/S NIC to be the same as the previous. Any hints on how to avoid that are welcome.

Thanks again for sharing Tim.</description>
		<content:encoded><![CDATA[<p>Tim, glad you raised that point. Since we originally investigated what we did in the article, we too found out that the latest VMWare Converter has the Synchronize changed data after conversion option. This is definitely the way to go!</p>
<p>One thing that caused us a little headache is that the newly created vm (destination of the conversion) ends up with a new virtual NIC and as such, the Windows guest O/S sees it as new hardware. Therefore, its a default NIC with DHCP and the works. We had to reconfigure the guest O/S NIC to be the same as the previous. Any hints on how to avoid that are welcome.</p>
<p>Thanks again for sharing Tim.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Bullock</title>
		<link>http://blog.tech4him.com/2010/03/esxi-4-moving-vms-to-new-storage/comment-page-1/#comment-134</link>
		<dc:creator>Tim Bullock</dc:creator>
		<pubDate>Tue, 20 Apr 2010 18:16:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tech4him.com/?p=948#comment-134</guid>
		<description>Um, why do all of that when you can just install the free vmware converter on the VM and run the convert?  Your original VM can be up and running while you convert and power up the new VM without the NIC turned on.  Once up, tools updated and IP added(if using static), kill the NIC on the original VM and turn on the NIC on the new VM.

Done.</description>
		<content:encoded><![CDATA[<p>Um, why do all of that when you can just install the free vmware converter on the VM and run the convert?  Your original VM can be up and running while you convert and power up the new VM without the NIC turned on.  Once up, tools updated and IP added(if using static), kill the NIC on the original VM and turn on the NIC on the new VM.</p>
<p>Done.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

