<?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>Check that driver file versions match on all your cluster nodes via Powershell</title><link>http://blogs.technet.com/brad_rutkowski/archive/2008/12/03/check-that-driver-file-versions-match-on-all-your-cluster-nodes-match-via-powershell.aspx</link><description>This is more of a proof of concept, but I've used it with success internally. Take it and do with it what you want. Many thx to Brandon who did the "heavy lifting" when I got stuck! Overview: Ever run into cluster issues and wanted to see if the driver</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>file server | Digg hot tags</title><link>http://blogs.technet.com/brad_rutkowski/archive/2008/12/03/check-that-driver-file-versions-match-on-all-your-cluster-nodes-match-via-powershell.aspx#3163650</link><pubDate>Thu, 04 Dec 2008 05:07:20 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3163650</guid><dc:creator>file server | Digg hot tags</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://diggwow.info/tags/109/200812/file-server.html"&gt;http://diggwow.info/tags/109/200812/file-server.html&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Check that driver file versions match on all your cluster nodes via Powershell</title><link>http://blogs.technet.com/brad_rutkowski/archive/2008/12/03/check-that-driver-file-versions-match-on-all-your-cluster-nodes-match-via-powershell.aspx#3166422</link><pubDate>Wed, 10 Dec 2008 21:23:54 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3166422</guid><dc:creator>Hal Rottenberg [MVP]</dc:creator><description>&lt;p&gt;Nice one. &amp;nbsp;Will be covering on the next PowerScripting Podcast.&lt;/p&gt;
</description></item><item><title>re: Check that driver file versions match on all your cluster nodes via Powershell</title><link>http://blogs.technet.com/brad_rutkowski/archive/2008/12/03/check-that-driver-file-versions-match-on-all-your-cluster-nodes-match-via-powershell.aspx#3192042</link><pubDate>Tue, 27 Jan 2009 20:34:49 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3192042</guid><dc:creator>eltate</dc:creator><description>&lt;p&gt;I get this error on Exchange 2007 64bits cluster&lt;/p&gt;
&lt;p&gt;[PS] D:\Scripts&amp;gt;.\Test-MSCluster.ps1 &amp;nbsp;SCC1 | ?{!$_.IsSame}&lt;/p&gt;
&lt;p&gt;Getting Nodes via WMI&lt;/p&gt;
&lt;p&gt;Get-WmiObject : A parameter cannot be found that matches parameter name 'Authentication'.&lt;/p&gt;
&lt;p&gt;At D:\Scripts\Test-MSCluster.ps1:11 char:120&lt;/p&gt;
&lt;p&gt;+ $nodes = gwmi -q &amp;quot;Select name from MSCluster_Node&amp;quot; -namespace root\mscluster -computername $ClusterNode -Authenticati&lt;/p&gt;
&lt;p&gt;on &amp;nbsp;&amp;lt;&amp;lt;&amp;lt;&amp;lt; PacketPrivacy | %{$_.Name}&lt;/p&gt;
&lt;p&gt;Getting the drivers on:&lt;/p&gt;
&lt;p&gt;Get-ChildItem : Cannot find path '\\\admin$\system32\drivers' because it does not exist.&lt;/p&gt;
&lt;p&gt;At D:\Scripts\Test-MSCluster.ps1:18 char:35&lt;/p&gt;
&lt;p&gt;+ &amp;nbsp; &amp;nbsp; $filelistFinal = get-childitem &amp;nbsp;&amp;lt;&amp;lt;&amp;lt;&amp;lt; &amp;quot;\\$node\admin$\system32\drivers&amp;quot; *.sys | %{$_.name}&lt;/p&gt;
&lt;p&gt;Getting the file versions for the drivers on:&lt;/p&gt;
&lt;p&gt;Exception calling &amp;quot;Add&amp;quot; with &amp;quot;2&amp;quot; argument(s): &amp;quot;Key cannot be null.&lt;/p&gt;
&lt;p&gt;Parameter name: key&amp;quot;&lt;/p&gt;
&lt;p&gt;At D:\Scripts\Test-MSCluster.ps1:28 char:23&lt;/p&gt;
&lt;p&gt;+ &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; $Files.Add( &amp;lt;&amp;lt;&amp;lt;&amp;lt; $file,&amp;quot;added&amp;quot;)&lt;/p&gt;
</description></item><item><title>re: Check that driver file versions match on all your cluster nodes via Powershell</title><link>http://blogs.technet.com/brad_rutkowski/archive/2008/12/03/check-that-driver-file-versions-match-on-all-your-cluster-nodes-match-via-powershell.aspx#3193988</link><pubDate>Thu, 29 Jan 2009 00:54:06 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3193988</guid><dc:creator>Brad Rutkowski</dc:creator><description>&lt;p&gt;Hey eltate, you need to be running Powershell v2.&lt;/p&gt;
</description></item><item><title>re: Check that driver file versions match on all your cluster nodes via Powershell</title><link>http://blogs.technet.com/brad_rutkowski/archive/2008/12/03/check-that-driver-file-versions-match-on-all-your-cluster-nodes-match-via-powershell.aspx#3193991</link><pubDate>Thu, 29 Jan 2009 00:57:04 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3193991</guid><dc:creator>Brad Rutkowski</dc:creator><description>&lt;p&gt;Hey elate:&lt;/p&gt;
&lt;p&gt;The -Authentication was put into v2 to help with this issue. &amp;nbsp;You cannot use get-wmiobject in POSH v1 to connect to namespaces that require packet privacy (see my earlier post on this subject). &amp;nbsp;You'd need to use [wmisearcher] or the .NET framework and then set the authentication in there. &amp;nbsp;Sorry. &amp;nbsp;It CAN be done though, just a bit more work.&lt;/p&gt;
</description></item></channel></rss>