Windows PowerShell (Monad) Has Arrived

Windows PowerShell (Monad) Has Arrived

Rate This
  • Comments 33

I just got out of Bob Muglia's keynote speech where he formally announced Windows PowerShell (previously known as Monad).  The key things he announced are:

  1. Monad (MSH) has a new name: Windows PowerShell
  2. Windows PowerShell will RTW (Web download) in Q4 2006
  3. RC1 of Windows PowerShell is available today
  4. Exchange 2007 and MOM will be built upon Windows PowerShell
  5. The next wave of products will be leverage the same architecture - Admin GUI layered on Windows PowerShell

Superstar Vivek Sharma demonstrated the Exchange 2007 Admin experience. First he showed their new MMC 3.0 managed code snap-in - it totally rocks! (you'll be amazed by what you can do with MMC 3.0).   He showed an example of adding a distribution list using the GUI.  At the end of this wizard, it showed the results of the operation and the Command equivalent.  This highlighted the fact that the Exchange GUI is layered on top of PowerShell meaning that there is parity between the GUI and the CLI and that the GUI helps teach the CLI.  He then opened a PowerShell window and typed the Cmdlet name using tab-completion and hit enter, this then prompted him for all the necessary information to complete the task showing you PowerShell helps guide the user to successful complete the task.  He then showned a number of features of the Exchange cmdlets highlighting the ability to safely manage a large number of objects in a single command line.  He concluded by showing a command sequence which leveraged a Exchange 2007 cmdlet piped to a Monad Cmdlet piped to a Community script to generate a graphical chart report of Exchange data.  It was a very cool demo and was very well received.

Here are the ramifications of this announcement:
Windows PowerShell is real and you can count on it shipping.  Most of you already knew that but some people just won't talk to you until you have a ship date and ship vehicle.  We have those now. Everyone can start making concrete plans for how and when you'll support, leverage and/or use Windows PowerShell. 

Windows PowerShell is ready for the big leagues.  Exchange 2007 is a major league, high volume, high stress, production application and it is using Windows PowerShell as the core for its entire admin experience.  We have worked closely with that team to ensure that Windows PowerShell V1.0 has the features and quality necessary to make that a safe bet.  Exchange has been hardcore about the functional and operation requirements of their customers.  This has driven PowerShell and resulted in an unusually robust and functional V1.0 release.  You too can expose your admin experience via Windows PowerShell and deliver your customer's an awesome admin experience. If you are an admin, you should start asking your vendors when they'll support PowerShell.

You can use RC1 of Windows PowerShell today.  RC1 is in great shape.  We changed the name of the exe to PowerShell.exe and the extension is now .PS1 .  We also did a big consistency pass on the cmdlets and their parameters make a number of changes along with those required to support the new name.  We release that this means that you'll have to relearn some commands and perhaps rework some scripts - apologizes for that but in the long turn, these changes really improve the consistency of the surface - a virtue that will pay back year and year.  There are also a number of bug fixes and a few DCRs.  The one you'll all go goo-goo over is Tab Completion.  You can now Tab-Complete command names, parameter names, filenames, and variable properties/methods.  Tab-Completion is now a user-definable function so if you don't like our implementation, you can replace it with one of your choosing.  Pick up RC1 today.  Here are the links:
- X86 Windows PowerShell latest build:
- X64 Windows PowerShell latest build: 
- Windows PowerShell documentation: 

Side Note:  The names of many of the APIs have changed to refect the new name (basically you'll have to search and replace MSH with PS).  We're sorry about the inconvience of this, we always expected the official name to be the Microsoft Shell or Management Shell so we felt confident that MSH was safe to use.  When Marketing saw what the technology actually did and the incredibly positive reaction that customers and partners, they decided that we warrented a "Marquee" name (I'm not making this up). Marquee names are given to those features that are going to be emphasized during the Marketing push.  So here is the net of all that: the downside is that you've got to change your API calls, the upside is that you are leveraging a technology that Microsoft Marketing plans to feature widely. 

We have a new blog site to befit our new name:

This is a pretty big day for the community. 


[Edit: Monad has now been renamed to Windows PowerShell. This script or discussion may require slight adjustments before it applies directly to newer builds.]

Leave a Comment
  • Please add 2 and 3 and type the answer here:
  • Post
  • OK, I said this elsewhere first when I heard the news, but I figure I ought to say it to y'all's faces. too:

    "Windows PowerShell really is a terrible, terrible name. At least by my usual standard of whether, on first hearing it, I think, "Aaagh! Save me from the marketing demons!"

    So now a great product is stuck with a name that's more generic than Gene Generic from Generica, GN.

    I weep."
  • I don't mind the new name.  I think it will allow for a more seamless co-existence with the old command shell.  What is the difference between the two?  They are both Microsoft's command shells.  One is more powerful.  It is trivial to create an alias for PS, so I also don't mind the verbosity of the new name...but I would like to see the PS alias come out of the box.

    Good job guys!  This is really coming together nicely!
  • PingBack from
    [via Scott Hanselman]
    As I mentioned previously about Microsoft Command Shell (aka Monad), it's...
    crosspost from
    [via Scott Hanselman]
    As I mentioned previously...
  • What can you say, this is a *BS* name. PowerShell, sounds some new Windows XP PowerToy tool - not as the genuine core management shell it is. This is a core windows server platform feature... not a toy.
  • Absolutely no improvement over the ugly looking command window. With the name change if someone in your group maybe can push for "tabbed" "POWER"shell?
    I am sure you guys can come up with brighter ideas than just a name change!. Are we ever moving off the ugly command window? Has anyone looked at the 'terminal' customizations in Linux?
  • MSH renamed to PowerShell. In RC1. Released Q42006.
  • > Absolutely no improvement over the ugly looking command window. With the name change if someone in your group maybe can push for "tabbed" "POWER"shell?

    We share your pain. We REALLY do.  This just feel into the "to ship is to choose" category.  We designed it so that 3rd parties could do this.  (3rd parties - do you see how many people would be interested in a great PowerShell HOST?)!

    Jeffrey Snover
  • PingBack from
  • Monad has been given a "marquee name" by the marketing folks at Microsoft. Henceforth Monad is the Windows PowerShell, and MSH becomes PS. Here's the announcement on the newly renamed Windows PowerShell blog...
  • Just another vote for a rename of the exe.
    Powershell.exe is just rediculous.
  • >> 3rd parties - do you see how many people would be interested in a great PowerShell HOST?

    There's a 3rd party open source tool that's supposed to make CMD and Monad look prettier.

    It's not a PowerShell Host as such, but it works pretty great.

  • I want to say only one - it is necessary to devise something new!!!!!!!!! it is still better

Page 2 of 3 (33 items) 123