Of /why/ PowerShell is honestly a /power/ shell environment when it comes to Windows administration. However, this is also another example as to why this new server (I'm focusing on the Windows Remote Management 3.0 part obviously) isn't hardly as game changing as the author makes it.
The fun thing is is that PowerShell is full Object Oriented commandline environment (OOCLI ?). You don't deal with mere text or collections; you're dealing with objects which can all have their own unique properties, functions and methods. To make this even more interesting; it also fully supports the Windows Component Object Model (COM).
I'd say its pretty much common practice to check for software updates on a computer (be it server or client) every now and then, and when you have a few of those it can be tedious if you need to logon to all of them individually...
That is where PowerShell & COM can come in:
$WUSession = New-Object -ComObject "Microsoft.Update.Session"
$updates = $WUSession.CreateUpdateSearcher().Search("IsInstalled=0 And Type='Software'").Updates
Now "$updates" contains all the update descriptions. To get a good overview (and also if an update has already been downloaded and/or installed yet) simply process the collection of objects:
$updates | Format-List -Property Title, isDownloaded, isInstalled
Now that is what I call power at your fingertips. This beats having to logon to remote computers using remote desktop only to see if there are updates available! Imagine running this with one command across all your servers or clients... Oh wait, you can ;-)
SO, back to the article.. There is a lot of new stuff for PowerShell, sure. But what about software updates ?
No, there isn't any. Yes, it supports 'Windows Server Update Services' (Wsus) but that is /not/ the same. That is an infrastructure which can run on your server to distribute updates towards your clients. Ideal in an enterprise environment, but what about small to mid-size Windows networks which may even have chosen to perform maintenance on the clients manually ?
So more precisely... Its nice that they added Cmdlets for something as trivial as requesting information about your tcp/ip settings, but why haven't they added native support to allow people to check up more easily on Windows updates ?
It took me quite some time to 'hack' that COM class (Microsoft.Update.Session) by searching & studying MSDN but getting information about my network adapters took me no longer than 5 minutes (that starts with "Get-WMIObject -List *network*" for example).
SO pardon me for not being all that impressed yet with the current updates to PowerShell.