<?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: Add RDM Size info to VI Client using Powershell</title>
	<atom:link href="http://www.peetersonline.nl/index.php/vmware/add-rdm-size-info-to-vi-client-using-powershell/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.peetersonline.nl/index.php/vmware/add-rdm-size-info-to-vi-client-using-powershell/</link>
	<description>Using Powershell for (virtually) everything!</description>
	<lastBuildDate>Fri, 03 Feb 2012 11:41:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: David</title>
		<link>http://www.peetersonline.nl/index.php/vmware/add-rdm-size-info-to-vi-client-using-powershell/comment-page-1/#comment-10236</link>
		<dc:creator>David</dc:creator>
		<pubDate>Tue, 15 Sep 2009 07:23:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.peetersonline.nl/?p=204#comment-10236</guid>
		<description>Hi Hugo,

Nice script, helps me a lot for my disk usage reports.

I don&#039;t know if you do a script on demand ;-), but I&#039;m looking for a PS script that puts the foldername where my VM is situated as an attribute.

The reason why I need this is because I will recreate my clusters and otherwise I will lose all my foldernames where Ive&#039; put them.

The logic we use is 
Cluster =&gt; Foldername =&gt; vm 
or 
Cluster =&gt; Foldername =&gt; Subfolder =&gt; vm

Hope you know an easy way to achieve this.

Cheers,

David</description>
		<content:encoded><![CDATA[<p>Hi Hugo,</p>
<p>Nice script, helps me a lot for my disk usage reports.</p>
<p>I don&#8217;t know if you do a script on demand ;-), but I&#8217;m looking for a PS script that puts the foldername where my VM is situated as an attribute.</p>
<p>The reason why I need this is because I will recreate my clusters and otherwise I will lose all my foldernames where Ive&#8217; put them.</p>
<p>The logic we use is<br />
Cluster =&gt; Foldername =&gt; vm<br />
or<br />
Cluster =&gt; Foldername =&gt; Subfolder =&gt; vm</p>
<p>Hope you know an easy way to achieve this.</p>
<p>Cheers,</p>
<p>David</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sylvain</title>
		<link>http://www.peetersonline.nl/index.php/vmware/add-rdm-size-info-to-vi-client-using-powershell/comment-page-1/#comment-3188</link>
		<dc:creator>Sylvain</dc:creator>
		<pubDate>Thu, 19 Mar 2009 16:59:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.peetersonline.nl/?p=204#comment-3188</guid>
		<description>Hello,
It&#039;s doesn&#039;t work for me. The return size for the RDM disk is not right... do you have this problem ?

Thanks in advance</description>
		<content:encoded><![CDATA[<p>Hello,<br />
It&#8217;s doesn&#8217;t work for me. The return size for the RDM disk is not right&#8230; do you have this problem ?</p>
<p>Thanks in advance</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.peetersonline.nl/index.php/vmware/add-rdm-size-info-to-vi-client-using-powershell/comment-page-1/#comment-3124</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Tue, 17 Mar 2009 19:25:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.peetersonline.nl/?p=204#comment-3124</guid>
		<description>[...] ссылка на пост Хуго Питерса (Hugo Peeters) о скрипте, который добавляет информацию о размере RDM в VI-клиент с помощью P.... Мне понравилось смотреть на скрипты других людей – [...]</description>
		<content:encoded><![CDATA[<p>[...] ссылка на пост Хуго Питерса (Hugo Peeters) о скрипте, который добавляет информацию о размере RDM в VI-клиент с помощью P&#8230;. Мне понравилось смотреть на скрипты других людей – [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Windows PowerShell Blog : Step up your FOREACH Game</title>
		<link>http://www.peetersonline.nl/index.php/vmware/add-rdm-size-info-to-vi-client-using-powershell/comment-page-1/#comment-1444</link>
		<dc:creator>Windows PowerShell Blog : Step up your FOREACH Game</dc:creator>
		<pubDate>Fri, 19 Dec 2008 17:15:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.peetersonline.nl/?p=204#comment-1444</guid>
		<description>[...] not ready to recommend it yet BUT the very first item on the bullet was from depping with a link to a blog post by&#160; Hugo Peeters about script that adds RDM size info to a VI client using ....&#160; I love looking at other peoples scripts - it gives me a view into how they think about the [...]</description>
		<content:encoded><![CDATA[<p>[...] not ready to recommend it yet BUT the very first item on the bullet was from depping with a link to a blog post by&#160; Hugo Peeters about script that adds RDM size info to a VI client using &#8230;.&#160; I love looking at other peoples scripts &#8211; it gives me a view into how they think about the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.peetersonline.nl/index.php/vmware/add-rdm-size-info-to-vi-client-using-powershell/comment-page-1/#comment-1443</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 19 Dec 2008 17:09:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.peetersonline.nl/?p=204#comment-1443</guid>
		<description>&lt;a href=&quot;#comment-1442&quot; rel=&quot;nofollow&quot;&gt;@Jeffrey Snover&lt;/a&gt; 
Hey Jeffrey, 
Thanks!
I do tend to use that technique when that part of the script is inside a loop, so that I don&#039;t have to Clear-Variable the extra variable. At other times, when the first line needs an additional pipe to Where-Object, I often keep them on two separate lines for readability.
I write my scripts mostly off the top of my head, so that&#039;s probably why I sometimes create to much variables. I need to look them over more often when they are done to consolidate some of the clutter into single lines.
Thanks for the tip! And I must say it&#039;s an honor to have you on my blog ;)
Hugo</description>
		<content:encoded><![CDATA[<p><a href="#comment-1442" rel="nofollow">@Jeffrey Snover</a><br />
Hey Jeffrey,<br />
Thanks!<br />
I do tend to use that technique when that part of the script is inside a loop, so that I don&#8217;t have to Clear-Variable the extra variable. At other times, when the first line needs an additional pipe to Where-Object, I often keep them on two separate lines for readability.<br />
I write my scripts mostly off the top of my head, so that&#8217;s probably why I sometimes create to much variables. I need to look them over more often when they are done to consolidate some of the clutter into single lines.<br />
Thanks for the tip! And I must say it&#8217;s an honor to have you on my blog ;)<br />
Hugo</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffrey Snover</title>
		<link>http://www.peetersonline.nl/index.php/vmware/add-rdm-size-info-to-vi-client-using-powershell/comment-page-1/#comment-1442</link>
		<dc:creator>Jeffrey Snover</dc:creator>
		<pubDate>Fri, 19 Dec 2008 16:38:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.peetersonline.nl/?p=204#comment-1442</guid>
		<description>Howdy Hugo!

That is a nice readable script.  I thought I would make one suggestion that I&#039;ve started doing more and more with my scripts.  You have the following:

$VMs = Get-VM
ForEach ($VM in $VMs)

Lately I&#039;ve been collapsing that into a single line because I think it is more readable/maintainable (and I don&#039;t have to think up a good variable name!).  It would be:

ForEach ($VM in Get-VM)

Jeffrey Snover [MSFT]
Windows Management Partner Architect
Visit the Windows PowerShell Team blog at:    http://blogs.msdn.com/PowerShell
Visit the Windows PowerShell ScriptCenter at:  http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx</description>
		<content:encoded><![CDATA[<p>Howdy Hugo!</p>
<p>That is a nice readable script.  I thought I would make one suggestion that I&#8217;ve started doing more and more with my scripts.  You have the following:</p>
<p>$VMs = Get-VM<br />
ForEach ($VM in $VMs)</p>
<p>Lately I&#8217;ve been collapsing that into a single line because I think it is more readable/maintainable (and I don&#8217;t have to think up a good variable name!).  It would be:</p>
<p>ForEach ($VM in Get-VM)</p>
<p>Jeffrey Snover [MSFT]<br />
Windows Management Partner Architect<br />
Visit the Windows <a href="http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx" target='_blank'>PowerShell</a> Team blog at:    <a href="http://blogs.msdn.com/PowerShell" rel="nofollow">http://blogs.msdn.com/PowerShell</a><br />
Visit the Windows <a href="http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx" target='_blank'>PowerShell</a> ScriptCenter at:  <a href="http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx" rel="nofollow">http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx</a>
<p style="opacity:0.5;padding:0;margin:0;display:inline;"><sub><a href="http://www.janhvizdak.com/make-donation-cross-linker-plugin-wordpress.php" onclick="window.open('http://www.janhvizdak.com/make-donation-cross-linker-plugin-wordpress.php'); return false;" target="_blank" style="cursor:help;"><b>&#187;crosslinked&#171;</b></a></sub></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Add RDM Size info to VI Client using Powershell » Yellow Bricks</title>
		<link>http://www.peetersonline.nl/index.php/vmware/add-rdm-size-info-to-vi-client-using-powershell/comment-page-1/#comment-1441</link>
		<dc:creator>Add RDM Size info to VI Client using Powershell » Yellow Bricks</dc:creator>
		<pubDate>Fri, 19 Dec 2008 16:05:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.peetersonline.nl/?p=204#comment-1441</guid>
		<description>[...] his article for the script and the complete blogpost. Don&#8217;t forget to download the updated versions of [...]</description>
		<content:encoded><![CDATA[<p>[...] his article for the script and the complete blogpost. Don&#8217;t forget to download the updated versions of [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

