PowerShell Hits a Million Downloads in the First Six Months
Having come up with the initial idea of Windows PowerShell and then worked on it for a (really) long time, I was very optimistic about how it would be received and widely it would be adopted. I have to admit that even I’m shocked at where we are just six months after our release mid Nov 2006 release.
Shortly before we released, Scott Ottaway (our marketing guy) expressed an opinion that we have a million downloads in our first year. I thought he was delusional or just plain ignorant about how long it takes for technologies like this to be adopted. Imagine how much crow I’m eating now that we are about to have our millionth download.
That’s right – PowerShell has had almost a MILLION DOWNLOADS IN ITS FIRST 6 MONTHS. People just can’t get their heads around this – we keep double checking the numbers – but it’s true. Note that this does NOT include the Windows Server 2008 (Server “Longhorn” Beta 3) usage.
Also, just six months ago we did not know if we would be in Windows Server 2008 (“Longhorn”) but the team worked hard and got it in Beta 3. At MS, this is like moving a mountain because of our focus on testing and quality in late stages of product development but we were able to get it in WS08 within 3 months of given the go ahead.
The first six months have been amazing but I don’t think anyone truly grasps how ubiquitous PowerShell is going to become.
We keep hearing about customers moving beyond evaluation and deploying PowerShell in production environments. The flagship deployment so far has to be MySpace.com (the #1 internet destination). They have been using PowerShell to manage ALL of their production severs for over a year now (they were so impressed by the quality and reliability [not to mention power] of PowerShell, that they deployed our beta copies in production).
There is a large and growing list of products that are shipping with PowerShell support in final or beta test form. There is an even larger list of products that are working on PowerShell support. What is so nice is that as internal teams consider whether to do anything with PowerShell, we just have them talk to the teams that have already done it to get a feel for how much work it is going to be, what benefits they get and the customer reactions. A quick conversation with those teams and the deal is closed. Happy customers are clearly our best marketing. What is interesting is the level of integration that teams are executing on, including very deep integration. Exchange 2007 and Virtual Machine Manager are the flagships in this regard. Both teams took a significant, all-or-nothing bet on PowerShell as the heart of their management capabilities and they have benefited tremendously with integrated GUI and cmd line management and the ability of IT Pros to completely automate management tasks. This product list is old by the time you hit the carriage return but here are a few:
Microsoft projects using PowerShell:
System Center Operations Manager 2007 (MOM)
Microsoft Transporter Suite for Lotus Domino
Windows Server 2008 Beta3 (Longhorn)
Systems Center Virtual Machine Manager
Data Protection Manager 2007
Windows Compute Cluster Tool Pack
UserGroups I was delightfully surprised to see the first PowerShell usergroup get established in our first 6 months. The indefatigable Richard Siddaway started and runs the very active UK PowerShell Users Group Get-PSUGUK. Innovation and Impact There is widespread recognition of the level of innovation and the impact that this has on the Windows platform. A number of people in the Unix community have been gracious enough to offer their praise for this effort and encourage their own community to respond in kind. I what I like most is the emotional connection that PowerShell makes with the user community. (Note that quite a few of the compliments were coupled with a criticism of our use of CONSOLE – Message Received!). Here are a few examples: http://jbazuzi.blogspot.com/2007/01/powershell-is-awesome.html I want to declare my love of PowerShell to the world. http://thinkersroom.com/bytes/2006/10/27/customizing-windows-powershell/ The Windows PowerShell is probably one of Microsoft’s best innovations over the last few years. Really. It is a brilliant piece of work that finally gives the command line shell real power. http://www.javalobby.org/java/forums/t84456.html?start=0 Windows Powershell is awesome next-generation shell technology..and as usual 80% of the devs here have their heads (and eyes) stuck in the sand and casually dismiss whatever it offers (since its by M$). Yes, the UI is kludgy and old, but the concept/implementation is terrific. … Powershell’s object filtering pipeline concept brings things to the table that no Unix shell cam compare with. Powershell pipes _objects_ not text. There are _consistent_ cross-command constructs for filtering on those objects, evaluating conditions on those objects, formatting those objects, et al. Yeah Windows Powershell goes beyond what is available on Linux or any other Unix. Its object oriented, for one. Bash is not. … https://channel9.msdn.com/ShowPost.aspx?PostID=309510
I honestly think that PowerShell is going to be as significant as .NET, C# and LINQ. …the thing I love about PowerShell is that it feels like coming home. http://www.peterprovost.org/archive/2007/02/24/22255.aspx Now, you know that I love Powershell. I think it is one of the coolest developer innovations out of Microsoft in years. http://www.oreillynet.com/windows/blog/2006/06/powershell_shell_scripting_don.html PowerShell, though it’s not yet RTM, is a powerful enough shell that I’ve found myself wishing that Microsoft would stop ignoring UNIX and actually port it to UNIX machines. PowerShell’s innovations are clear enough to be of great value even on a UNIX system. I said it before, I’ll say it again: This train keeps gathering steam! SNOOPY DANCE! Jeffrey Snover [MSFT] Windows Management Partner Architect Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx