And Monad is now Windows PowerShell…

by Bharat Suneja

Close on the heels of Exchange Server “12” getting its official product name – Exchange Server 2007, the cool new shell environment so far known as Monad got its official name. Yes, Monad (aka “MSH”) is now called Windows PowerShell.

No comments on this renaming – I neither love nor hate it. On the brighter side, I am more than glad my worst fears about this did not come true (on the same lines as Internet Information Service or IIS, and Internet Connection Firewall or ICF for Windows Firewall… ).

The exciting part is – Monad, MSH, PowerShell – whatever you want to call it, is emerging as a powerful new shell environment that should help those of us who’ve lived with Unix/Linux-envy for so long and labored to write code using all those different APIs – finally there’s something that command-line jockeys can be proud of.

The story gets better – if you plan to play with or move up to Exchange Server 2007, all the Monad skills you learn now will prove to be quite useful for managing the upcoming version of Exchange.

If you haven’t already started with Windows PowerShell, it’s time to download Release Candidate 1 and get to work (or play!).

Having said that, the GUI interfaces aren’t going away any time soon. There are tasks that just lend themselves better to point-and-click – it helps to figure out which one’s better for a particular task and what works best for you.

{ 1 comment… read it below or add one }

vivek April 28, 2006 at 11:10 pm

A very concise summary… Shell is great, GUI is great, why not have both? :)

Reply

Cancel reply

Leave a Comment

Previous post:

Next post: