<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://powershell.com/cs/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>Richard Siddaway's Blog : PowerShell V3</title><link>http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+V3/default.aspx</link><description>Tags: PowerShell V3</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 (Build: 30929.2835)</generator><item><title>AD MoL Chapter 10 MEAP</title><link>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/05/08/ad-mol-chapter-10-meap.aspx</link><pubDate>Wed, 08 May 2013 19:07:19 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:23353</guid><dc:creator>Richard Siddaway's Blog</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/richardsiddaway/rsscomments.aspx?PostID=23353</wfw:commentRss><comments>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/05/08/ad-mol-chapter-10-meap.aspx#comments</comments><description>Chapter 10 of AD Management in a Month of Lunches is now available. http://www.manning.com/siddaway3/ The chapter covers Fine Grained Password Policies Read More......(&lt;a href="http://powershell.com/cs/blogs/richardsiddaway/archive/2013/05/08/ad-mol-chapter-10-meap.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=23353" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/Books/default.aspx">Books</category><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/Active+Directory/default.aspx">Active Directory</category><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+V3/default.aspx">PowerShell V3</category></item><item><title>Scripting Games–new Get-ChildItem parameters</title><link>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/05/07/scripting-games-new-get-childitem-parameters.aspx</link><pubDate>Tue, 07 May 2013 21:20:39 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:23323</guid><dc:creator>Richard Siddaway's Blog</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/richardsiddaway/rsscomments.aspx?PostID=23323</wfw:commentRss><comments>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/05/07/scripting-games-new-get-childitem-parameters.aspx#comments</comments><description>One improvement that came with PowerShell v3 is the –File and –Directory parameters on Get-ChildItem If I run this Get-ChildItem -Path c:\mydata I will get a mixture of directories and files Mode&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;...(&lt;a href="http://powershell.com/cs/blogs/richardsiddaway/archive/2013/05/07/scripting-games-new-get-childitem-parameters.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=23323" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+V3/default.aspx">PowerShell V3</category><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/Scripting+Games/default.aspx">Scripting Games</category></item><item><title>WMI vs CIM speed tests–the final round</title><link>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/30/wmi-vs-cim-speed-tests-the-final-round.aspx</link><pubDate>Tue, 30 Apr 2013 18:31:07 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:23138</guid><dc:creator>Richard Siddaway's Blog</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/richardsiddaway/rsscomments.aspx?PostID=23138</wfw:commentRss><comments>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/30/wmi-vs-cim-speed-tests-the-final-round.aspx#comments</comments><description>As a final test I want to see what happened when I ran multiple commands against the remote machine. PS&amp;gt; 1..100 | foreach { Measure-Command -Expression{1..100 | foreach { Get-WmiObject -Class Win32_ComputerSystem -ComputerName W12SUS; Get-WmiObject...(&lt;a href="http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/30/wmi-vs-cim-speed-tests-the-final-round.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=23138" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+and+WMI/default.aspx">PowerShell and WMI</category><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+V3/default.aspx">PowerShell V3</category></item><item><title>CIM vs WMI cmdlets-remote execution speed</title><link>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/29/cim-vs-wmi-cmdlets-remote-execution-speed.aspx</link><pubDate>Mon, 29 Apr 2013 19:08:14 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:23120</guid><dc:creator>Richard Siddaway's Blog</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/richardsiddaway/rsscomments.aspx?PostID=23120</wfw:commentRss><comments>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/29/cim-vs-wmi-cmdlets-remote-execution-speed.aspx#comments</comments><description>Following on from my previous post we’ll look at how the two types of cmdlets compare for accessing remote machines. I used a similar format to the previous tests but was accessing a remote machine. First off was the WMI cmdlet – using DCOM to access...(&lt;a href="http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/29/cim-vs-wmi-cmdlets-remote-execution-speed.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=23120" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+and+WMI/default.aspx">PowerShell and WMI</category><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+V3/default.aspx">PowerShell V3</category></item><item><title>Creating a new disk</title><link>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/12/creating-a-new-disk.aspx</link><pubDate>Fri, 12 Apr 2013 18:43:05 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:22757</guid><dc:creator>Richard Siddaway's Blog</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/richardsiddaway/rsscomments.aspx?PostID=22757</wfw:commentRss><comments>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/12/creating-a-new-disk.aspx#comments</comments><description>I really like Windows Server Core. The concept has come of age in Windows 2012. I needed to add a new disk to a virtual machine&amp;#160; - that’s easy using the Hyper-V cmdlets. But what about formating the disk. A module new to Windows 2012 &amp;amp; Windows...(&lt;a href="http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/12/creating-a-new-disk.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=22757" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+V3/default.aspx">PowerShell V3</category><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/Windows+Server+2012/default.aspx">Windows Server 2012</category></item><item><title>Windows Server Backup</title><link>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/11/windows-server-backup.aspx</link><pubDate>Thu, 11 Apr 2013 19:50:15 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:22716</guid><dc:creator>Richard Siddaway's Blog</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/richardsiddaway/rsscomments.aspx?PostID=22716</wfw:commentRss><comments>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/11/windows-server-backup.aspx#comments</comments><description>Windows Server 2012 has a PowerShell enabled backup utility. When you enable the feature you get a module called WindowsServerBackup.&amp;#160; It has the cmldets you would expect for creating and managing backups. No surprise you may say as this was avialable...(&lt;a href="http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/11/windows-server-backup.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=22716" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+V3/default.aspx">PowerShell V3</category><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/Windows+Server+2012/default.aspx">Windows Server 2012</category></item><item><title>Running workflows</title><link>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/08/running-workflows.aspx</link><pubDate>Mon, 08 Apr 2013 18:11:21 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:22616</guid><dc:creator>Richard Siddaway's Blog</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/richardsiddaway/rsscomments.aspx?PostID=22616</wfw:commentRss><comments>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/08/running-workflows.aspx#comments</comments><description>I tripped over an interesting issue recently regarding the running of PowerShell workflows. Consider the world’s simplest workflow workflow test-w1 {&amp;quot;hello world&amp;quot;} If I run this on a 32bit Windows 8&amp;#160; PowerShell machine – it works If I run...(&lt;a href="http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/08/running-workflows.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=22616" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+V3/default.aspx">PowerShell V3</category></item><item><title>AD Management in a Month of Lunches</title><link>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/06/ad-management-in-a-month-of-lunches.aspx</link><pubDate>Sat, 06 Apr 2013 15:39:41 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:22602</guid><dc:creator>Richard Siddaway's Blog</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/richardsiddaway/rsscomments.aspx?PostID=22602</wfw:commentRss><comments>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/06/ad-management-in-a-month-of-lunches.aspx#comments</comments><description>The MEAP marches on with chapter 8 now released: Chapter 8 – creating Group Policies details from http://www.manning.com/siddaway3/ Read More......(&lt;a href="http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/06/ad-management-in-a-month-of-lunches.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=22602" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/Books/default.aspx">Books</category><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/Active+Directory/default.aspx">Active Directory</category><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+V3/default.aspx">PowerShell V3</category><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/Windows+Server+2012/default.aspx">Windows Server 2012</category></item><item><title>Putting the date in a file name</title><link>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/03/putting-the-date-in-a-file-name.aspx</link><pubDate>Wed, 03 Apr 2013 19:18:33 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:22570</guid><dc:creator>Richard Siddaway's Blog</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/richardsiddaway/rsscomments.aspx?PostID=22570</wfw:commentRss><comments>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/03/putting-the-date-in-a-file-name.aspx#comments</comments><description>I often need to create file names that include the date &amp;amp; time the file was created in the name. I’ve come up with all sorts of ways to do but this I think is the simplest. I want the date in this format:&amp;#160; year-month-day-hour-minute-second.&amp;#160;...(&lt;a href="http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/03/putting-the-date-in-a-file-name.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=22570" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+V3/default.aspx">PowerShell V3</category></item><item><title>Shutting down a remote computer</title><link>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/01/shutting-down-a-remote-computer.aspx</link><pubDate>Mon, 01 Apr 2013 11:16:35 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:22524</guid><dc:creator>Richard Siddaway's Blog</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/richardsiddaway/rsscomments.aspx?PostID=22524</wfw:commentRss><comments>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/01/shutting-down-a-remote-computer.aspx#comments</comments><description>PowerShell provides the Stop-Computer cmdlet for closing down a remote machine. I find this especially useful in my virtual test environment. I’ll have several machines running but won’t necessarily have logged onto them. Using Stop-Computer means that...(&lt;a href="http://powershell.com/cs/blogs/richardsiddaway/archive/2013/04/01/shutting-down-a-remote-computer.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=22524" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+and+WMI/default.aspx">PowerShell and WMI</category><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+V3/default.aspx">PowerShell V3</category><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/Windows+Server+2012/default.aspx">Windows Server 2012</category></item><item><title>CIM cmdlets</title><link>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/03/26/cim-cmdlets.aspx</link><pubDate>Tue, 26 Mar 2013 21:03:47 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:22420</guid><dc:creator>Richard Siddaway's Blog</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/richardsiddaway/rsscomments.aspx?PostID=22420</wfw:commentRss><comments>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/03/26/cim-cmdlets.aspx#comments</comments><description>The CIM cmdlets are found in the CIMcmdlets module. Get-Command -Module CimCmdlets&amp;#160; produces this list of names.&amp;#160; I’ve added some information on the tasks they perform Get-CimAssociatedInstance&amp;#160; is for working with WMI associated classes...(&lt;a href="http://powershell.com/cs/blogs/richardsiddaway/archive/2013/03/26/cim-cmdlets.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=22420" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+and+WMI/default.aspx">PowerShell and WMI</category><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+V3/default.aspx">PowerShell V3</category></item><item><title>WMI vs CIM</title><link>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/03/24/wmi-vs-cim.aspx</link><pubDate>Sun, 24 Mar 2013 12:03:50 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:22376</guid><dc:creator>Richard Siddaway's Blog</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/richardsiddaway/rsscomments.aspx?PostID=22376</wfw:commentRss><comments>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/03/24/wmi-vs-cim.aspx#comments</comments><description>An email debate yesterday regarding the use of the CIM cmdlets (new in PowerShell 3) vs the WMI cmdlets made me realise that other people are probably wondering the same thing, The question is really part of a the semi-philosophical debate about when...(&lt;a href="http://powershell.com/cs/blogs/richardsiddaway/archive/2013/03/24/wmi-vs-cim.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=22376" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+and+WMI/default.aspx">PowerShell and WMI</category><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+V3/default.aspx">PowerShell V3</category></item><item><title>PowerShell 3 SDK samples</title><link>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/03/21/powershell-3-sdk-samples.aspx</link><pubDate>Thu, 21 Mar 2013 19:49:44 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:22293</guid><dc:creator>Richard Siddaway's Blog</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/richardsiddaway/rsscomments.aspx?PostID=22293</wfw:commentRss><comments>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/03/21/powershell-3-sdk-samples.aspx#comments</comments><description>A sample pack for the SDK is now available -&amp;#160; see http://blogs.msdn.com/b/powershell/archive/2013/03/17/windows-powershell-3-0-sample-pack.aspx Read More......(&lt;a href="http://powershell.com/cs/blogs/richardsiddaway/archive/2013/03/21/powershell-3-sdk-samples.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=22293" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+V3/default.aspx">PowerShell V3</category></item><item><title>Network Adapters–Disable/Enable</title><link>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/03/11/network-adapters-disable-enable.aspx</link><pubDate>Mon, 11 Mar 2013 20:08:21 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:22103</guid><dc:creator>Richard Siddaway's Blog</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/richardsiddaway/rsscomments.aspx?PostID=22103</wfw:commentRss><comments>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/03/11/network-adapters-disable-enable.aspx#comments</comments><description>Last time we saw the Get-NetAdapter cmdlet from the NetAdapter module PS&amp;gt; Get-NetAdapter | ft Name, InterfaceDescription, Status -a Name&amp;#160;&amp;#160;&amp;#160;&amp;#160; InterfaceDescription&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;...(&lt;a href="http://powershell.com/cs/blogs/richardsiddaway/archive/2013/03/11/network-adapters-disable-enable.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=22103" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+and+WMI/default.aspx">PowerShell and WMI</category><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+V3/default.aspx">PowerShell V3</category><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/Windows+8/default.aspx">Windows 8</category><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/Windows+Server+2012/default.aspx">Windows Server 2012</category></item><item><title>Network adapters</title><link>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/03/04/network-adapters.aspx</link><pubDate>Mon, 04 Mar 2013 20:23:47 GMT</pubDate><guid isPermaLink="false">f421715f-7aba-45f0-8a8d-44de5318a3a7:21954</guid><dc:creator>Richard Siddaway's Blog</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://powershell.com/cs/blogs/richardsiddaway/rsscomments.aspx?PostID=21954</wfw:commentRss><comments>http://powershell.com/cs/blogs/richardsiddaway/archive/2013/03/04/network-adapters.aspx#comments</comments><description>The WMI classes Win32_NetworkAdapter and Win32_NetworkAdapterConfiguration have seen a lot of use over the years. They can be a bit fiddly to use which is why the NetAdapter module in Windows 8/2012 is a so welcome. Lets start by looking at basic information...(&lt;a href="http://powershell.com/cs/blogs/richardsiddaway/archive/2013/03/04/network-adapters.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://powershell.com/cs/aggbug.aspx?PostID=21954" width="1" height="1"&gt;</description><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+and+WMI/default.aspx">PowerShell and WMI</category><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/PowerShell+V3/default.aspx">PowerShell V3</category><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/Windows+8/default.aspx">Windows 8</category><category domain="http://powershell.com/cs/blogs/richardsiddaway/archive/tags/Windows+Server+2012/default.aspx">Windows Server 2012</category></item></channel></rss>