When are you upgrading to Windows Management Framework 3.0?

So, Windows Management Framework 3 has been available for a few months and is supported on Windows 7 Sp1, Windows Server 2008 R2 Sp1 and Windows Server 2008 Sp2. I’m curious: when you do plan to upgrade? If not, why?

The reason I’m asking is that while the twitter-verse on PowerShell has already made the move to version 3, I’ve noticed a lag in adoption from the less-than-zealots.  Many customers and students have told me that they haven’t really thought much about deploying the new version, and I guess I’m kind of confused by this. PowerShell v3 has immediate advantages for the working administrator – my favorite is dynamically loading modules – and I’m not sure I understand the drag to adoption.

There is a problem updating to WMF 3.0 for some products, this has been widely reported and I discussed that issue in my last blog. If you have some servers running products like SharePoint 2010, Exchange 2007 or 2010 or System Center, then you should NOT update those systems. They are not ready yet, in fact, see here for the complete list: Windows Management Framework 3.0 Compatibility Update

I’m not a rush-to-V-Next kind of guy – too many years in the enterprise has taught me well about fixing things that ain’t broke, but this is a different situation. I use PowerShell as my primary management tool and while v2 has been great, the improvements to v3 truly make it worth the update. My second favorite addition in v3 is the new CIM cmdlets that work over PowerShell Remoting. But there’s more…

  • The free ISE is improved and provides a console replacement that provides syntax highlighting (Yea, that does make a difference)
  • The Tab completion is smarter.  Ever try to add a parameter in the middle of a one-liner in v2? If you hit Tab, the entire line vanished from the screen: not anymore in v3.
  • As you banging out a one-liner, smacking the tab key for parameters, you would have to roll through the entire list. Tab completion now knows if a parameter has been used earlier in the line and doesn’t display it again.

This is not a complete features and benefits list, just some of the day-to-day management improvements that you will find valuable every time you open the shell. Opening a v2 console feels “cumbersome” after using v3.

So, help me out. Tell me what you think. Do you plan on updating to WMF 3.0 soon? If not, why?

Knowledge is PowerShell,

Jason

Jason Helmick
Director of PowerShell Technologies
Interface Technical Training

Posted in PowerShell | Posted in , , , , , , | Leave a comment

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">