<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Use PowerShell to Find the Top Values Returned by WMI</title><link>http://blogs.technet.com/b/heyscriptingguy/archive/2011/10/19/use-powershell-to-find-the-top-values-returned-by-wmi.aspx</link><description>Summary: Learn how to use Windows PowerShell to slice and dice WMI data in an easy, SQL-like fashion.</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Use PowerShell to Find the Top Values Returned by WMI</title><link>http://blogs.technet.com/b/heyscriptingguy/archive/2011/10/19/use-powershell-to-find-the-top-values-returned-by-wmi.aspx#3460177</link><pubDate>Wed, 19 Oct 2011 11:20:14 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3460177</guid><dc:creator>Ed Wilson</dc:creator><description>&lt;p&gt;@Klaus Schulte you are right, and this has been a common request to the WMI team for many years. As for joining different WMI classes, WMI already exposes the ability to perform associative Queries and it has a great deal associative WMI classes. I have a technique, using Windows PowerShell, that makes this highly complex process extremely easy. I will blog about it on Hey Scripting Guy! in the very near future. &lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3460177" width="1" height="1"&gt;</description></item><item><title>re: Use PowerShell to Find the Top Values Returned by WMI</title><link>http://blogs.technet.com/b/heyscriptingguy/archive/2011/10/19/use-powershell-to-find-the-top-values-returned-by-wmi.aspx#3460164</link><pubDate>Wed, 19 Oct 2011 09:28:42 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3460164</guid><dc:creator>Klaus Schulte</dc:creator><description>&lt;p&gt;Hi Ed,&lt;/p&gt;
&lt;p&gt;WMI and Powershell are already a good team!&lt;/p&gt;
&lt;p&gt;But I think, that the way WMI data are retrieved or updated could be further impoved!&lt;/p&gt;
&lt;p&gt;WQL is a good way to retrieve information but I&amp;#39;d like to have more options with it ( more like SQL )&lt;/p&gt;
&lt;p&gt;because of the way information has to be filtered and transmitted through the network where&lt;/p&gt;
&lt;p&gt;&amp;quot;less is more&amp;quot;! Less Traffic between the data source and the consumer and more sophisticated filtering, &lt;/p&gt;
&lt;p&gt;grouping and aggregating on the source site! &lt;/p&gt;
&lt;p&gt;Another great deal would be the ability of joining WMI objects in queries that sample data from different &lt;/p&gt;
&lt;p&gt;WMI classes, so that only one query has to be issued on a set of WMI classes instead of n queries targeting &lt;/p&gt;
&lt;p&gt;n different WMI classes where we have to extract the desired properties from the union of n resultsets.&lt;/p&gt;
&lt;p&gt;If we only could do the sort ( order by ), group ( by ) and first/last-n operations on the server = source site&lt;/p&gt;
&lt;p&gt;the overall roundtrip time should significantly decrease. &lt;/p&gt;
&lt;p&gt;I would even appreciate the advent of WLinq = Microsoft Linq for WMI &lt;/p&gt;
&lt;p&gt;( as much as I would like to have PSLinq :-)&lt;/p&gt;
&lt;p&gt;Klaus.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3460164" width="1" height="1"&gt;</description></item></channel></rss>