<?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: VIPlugins.com</title>
	<atom:link href="http://blog.scottlowe.org/2008/02/16/vipluginscom/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.scottlowe.org/2008/02/16/vipluginscom/</link>
	<description>The weblog of an IT pro specializing in virtualization, storage, and servers</description>
	<lastBuildDate>Tue, 07 Feb 2012 13:34:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: slowe</title>
		<link>http://blog.scottlowe.org/2008/02/16/vipluginscom/comment-page-1/#comment-39020</link>
		<dc:creator>slowe</dc:creator>
		<pubDate>Tue, 27 May 2008 10:28:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/02/16/vipluginscom/#comment-39020</guid>
		<description>Nick,

Visit http://akutz.wordpress.com/about/ and you will see links to the VI plugins and other software that Andrew has written. Some of the links point to SourceForge, some to direct downloads. It would appear he&#039;s in the midst of migrating all his stuff to new locations, so some of the links may not be fully operational just yet.</description>
		<content:encoded><![CDATA[<p>Nick,</p>
<p>Visit <a href="http://akutz.wordpress.com/about/" rel="nofollow">http://akutz.wordpress.com/about/</a> and you will see links to the VI plugins and other software that Andrew has written. Some of the links point to SourceForge, some to direct downloads. It would appear he&#8217;s in the midst of migrating all his stuff to new locations, so some of the links may not be fully operational just yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://blog.scottlowe.org/2008/02/16/vipluginscom/comment-page-1/#comment-39015</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Tue, 27 May 2008 08:46:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/02/16/vipluginscom/#comment-39015</guid>
		<description>Hi,

It seems that all Andrew Kutz sites now point to his latest blog but none of the vmware plugins are available.  Anyone know if there are any cached versions around.

Thanks
Nick</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>It seems that all Andrew Kutz sites now point to his latest blog but none of the vmware plugins are available.  Anyone know if there are any cached versions around.</p>
<p>Thanks<br />
Nick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thomas</title>
		<link>http://blog.scottlowe.org/2008/02/16/vipluginscom/comment-page-1/#comment-35623</link>
		<dc:creator>thomas</dc:creator>
		<pubDate>Mon, 18 Feb 2008 23:31:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/02/16/vipluginscom/#comment-35623</guid>
		<description>Andrew/Duncan,

I definitely agree, but take it a step further.  Apply the config at the cluster level (or possibly dc).  When a host is added to a cluster, it will automatically inherit the settings (or policies if you prefer) for that specific cluster.  Think group policy for ESX.    

I wrote an article a while ago covering the concept.

http://scalethemind.com/2007/11/next-step-in-evolution-of-virtualcenter/</description>
		<content:encoded><![CDATA[<p>Andrew/Duncan,</p>
<p>I definitely agree, but take it a step further.  Apply the config at the cluster level (or possibly dc).  When a host is added to a cluster, it will automatically inherit the settings (or policies if you prefer) for that specific cluster.  Think group policy for ESX.    </p>
<p>I wrote an article a while ago covering the concept.</p>
<p><a href="http://scalethemind.com/2007/11/next-step-in-evolution-of-virtualcenter/" rel="nofollow">http://scalethemind.com/2007/11/next-step-in-evolution-of-virtualcenter/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clint</title>
		<link>http://blog.scottlowe.org/2008/02/16/vipluginscom/comment-page-1/#comment-35608</link>
		<dc:creator>Clint</dc:creator>
		<pubDate>Mon, 18 Feb 2008 15:21:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/02/16/vipluginscom/#comment-35608</guid>
		<description>I would definitely like a template type plugin. We currently use Altiris to get ours similar, but there are times and certain areas that does not work. Having a template system, would allow use to pull a certain template based on area.</description>
		<content:encoded><![CDATA[<p>I would definitely like a template type plugin. We currently use Altiris to get ours similar, but there are times and certain areas that does not work. Having a template system, would allow use to pull a certain template based on area.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Kutz</title>
		<link>http://blog.scottlowe.org/2008/02/16/vipluginscom/comment-page-1/#comment-35584</link>
		<dc:creator>Andrew Kutz</dc:creator>
		<pubDate>Sun, 17 Feb 2008 19:57:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/02/16/vipluginscom/#comment-35584</guid>
		<description>Duncan,

I am working on a plugin that copies all of an ESX server&#039;s network settings to a new ESX server. But I like your idea better. So, you could configure one ESX server the way you want it and then say &quot;Export Settings&quot; and then right-click on a new ESX server, or servers, and say &quot;Import Settings&quot; and have the template apply all the settings? Capitol idea!</description>
		<content:encoded><![CDATA[<p>Duncan,</p>
<p>I am working on a plugin that copies all of an ESX server&#8217;s network settings to a new ESX server. But I like your idea better. So, you could configure one ESX server the way you want it and then say &#8220;Export Settings&#8221; and then right-click on a new ESX server, or servers, and say &#8220;Import Settings&#8221; and have the template apply all the settings? Capitol idea!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Duncan</title>
		<link>http://blog.scottlowe.org/2008/02/16/vipluginscom/comment-page-1/#comment-35574</link>
		<dc:creator>Duncan</dc:creator>
		<pubDate>Sun, 17 Feb 2008 13:28:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/02/16/vipluginscom/#comment-35574</guid>
		<description>cool stuff indeed. it&#039;s time VMware comes with these kind of plugins... They should create a ESX-template plugin, with which you could create a template of all the default settings you would do on an esx host after installation.</description>
		<content:encoded><![CDATA[<p>cool stuff indeed. it&#8217;s time VMware comes with these kind of plugins&#8230; They should create a ESX-template plugin, with which you could create a template of all the default settings you would do on an esx host after installation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

