PowerShell Training is now available!

Rate This
  • Comments 15

I was delighted to discover that DesktopEngineer.Com is now offering Windows PowerShell training: http://desktopengineer.com/ps310 .  This is the first (and therefore BEST :-) ) commercial training available for PowerShell (formally known as Monad).  I consider this a huge milestone for the project. 

One of my core beliefs is:

Technology is great but technology that matters is technology that creates an economic advantage.

This is the core principle of the PowerShell architecture and it influenced almost every element of the system.  There are three aspects to this principle:

  1. Developers should find it cheap and easy to code to PowerShell and the benefit PowerShell delivers to their customers should be ENORMOUS (leverage).
  2. End Users should be able to use PowerShell to increase their economic value by being able to dramatically lower costs through simple automation of complex things (productivity) and by using PowerShell to learn valuable .NET skills (marketability).
  3. Third parties should be able extend and participate in most aspects of PowerShell to deliver enough value that they can charge a lot of money and customers are happy to spend the money (commercialization).

We have seen lots of evidence of the first two aspects since the very beginning of the project.  It is great to now see the beginning of the commercialization phase of the project.  Exchange 2007 and MOM will be shipping with Powershell support. Opalis announced support for PowerShell in their product at MMS ( http://www.opalis.com/upload/pressreleases/OpalisPressRelease250406.pdf ).  The great O'Reilly book ( http://www.oreilly.com/catalog/msh/ ) has been available for a while now and there are a few more books due out this fall (http://www.manning.com/payette/  &  http://www.sapienpress.com/powershell.asp) .  I just installed the latest Alpha version of Sapien's PrimalScript IDE supporting PowerShell.  Now you can get training from DesktopEngineering.com (http://desktopengineer.com/ps310). 

The availability of commerical PowerShell training is particularly nice to see as the team is starting to get a number of requests from the field to come provide training to large customer XXX.  That is exciting but there is absolutely no way our team could scale to meet the demand of for this.  So 3 cheers for DesktopEngineering for being first into the pool!

Jeffrey Snover
Windows PowerShell Architect

Leave a Comment
  • Please add 1 and 8 and type the answer here:
  • Post
  • So why do we need it? So why do we want it? So why do we care? How will this make using your PC better? Why not create a batch of PC utilities that execute from the command line to aid the PC's life and ease of use? Not hackers will have a new toy to explore and we will all have to pay the price.

    DOS worked. . .

    CMD was OK. . .

    Why not just use perl for windows? ? ?

  • "So why do we need it?", well PowerShell is an improvement over DOS, cmd and wsh.

    Is it perfect? Certainly not!

    Every new technology has the potential to be used for good or bad. Should this stop us from making progress? Should we crawl back into the trees and fear anthing as advanced as fire? Well, I don't think so.

    I believe that PowerShell is a (huge) step in the right direction for Microsoft, and I'm certain that more steps will follow.


    I also use perl for windows - but for many tasks PowerShell is just better.

  • SAPIEN has training as well,

    see: http://www.scriptingtraining.com/classes.asp

    Taught by authors of "Windows PowerShell™: TFM®", Don Jones and Jeffery Hicks

  • New Horizons MN also has PowerShell Training!


    Get in on it now!!


  • PowerShell is still in beta, and in fact, it has changed so much since it first came out.  Why do I have to buy a book / pay for the training course when most of the commands and syntax do not work after 5, 6 months since last Oct, 2006.

  • Hi Tony;

    PowerShell 1.0 in fact released on November 14, 2006: http://blogs.msdn.com/powershell/archive/2006/11/14/windows-powershell-1-0-released.aspx.

    Any training and documentation would cover the RTM product.


  • I used MKS toolkit in the past

  • Do we finally get equivalents of grep and sed ?

    findstr is kind of limited.

  • The SANS Institute also has a PowerShell training course.  You can read more about here:


    And here:




  •  Before I begin, I don't believe this is the correct forum for such a comment, but I'm unsure of where to report bugs on Powershell.

     I have a few problems with powershell (so far; I've only had it installed for 20 min), one of which seems central to its design.  Anyway, here they are:

    1) Why is it slow to load & perform various actions?  In cmd (which isn't exactly fast compared to the DOS days either), a simple directory listing begins to display as soon as you hit enter, unless there's a lot to display.  In powershell, listing the contents of the root C drive requires about .2-.5 seconds before anything happens.  Regarding slow load time, I'm talking about opening powershell: cmd loads immediately, as did command.com, but powershell takes 2-3 seconds to load.

    2) Why was it necessary to change the name of things that have had the same name for 20+ years?  "items", "child-items", and "containers"?  I understand what they correspond to, but that'd be analagous to walking into the math department and saying you came up with a new way of doing math, and start calling functions 'functors', renaming variables to 'varying-quantity-containers', etc.  The documentation is also wordy, jumbled, and needs better punctuation.  To quote:

    "The Get-Childitem cmdlet gets the items in one or more specified locations.

    If the item is a container, it gets the items inside the container, known

    as child items. You can use the Recurse parameter to get items in all child

    containers A location can be a file system location, such as a directory,

    or a location exposed by another provider, such as a registry hive or a cer

    tificate store."

     Why cmdlet?  Why not just 'program', or 'command'; another standard term clarified with a more obscure term.  How about the line "..., known as child items".  It wouldn't be necessary to clarify what is meant if standard terms were used.

     Additionally, if 'ls', and 'dir' are going to serve as a default alias for "Get-ChildItem", why not list it as a variant?  This goes for all commands; if an alias exists, the documentation should show it.

     That's pretty much it.  I don't expect a reply, my goal is mainly to have those concerns examined.  Powershell seems very powerful, but in a day when new languages are cropping up in the professional world every week, it seems, adding more complexity rather than simplification can be maddening.

  • TRACIT (Belgium)has an excellent PowerShell training:



  • So I downloaded it and it looks like you just tried to make a clone of GNU bash. It's a pile of fail, IMO. There's this thing called "UNIX", and the future was 37 years ago.

  • I wish to extract the functionality of power shell to other application is there any way to do it

  • Be sure to have a look at the Global Knowledge course in Powershell, given by a MVP, really good quality course


  • Hey all,

    Just wanted to mention that there is a Microsoft MS-6434 Automating Windows Server 2008 Administration with Windows Powershell Class available in the world.

    SQLSoft currently offers this course on a pretty regular basis.  You can get more info here:



Page 1 of 1 (15 items)

PowerShell Training is now available!