Early Christmas Present from PowerShell Team: Community Technology Preview-3 (CTP3) of Windows PowerShell V2

Early Christmas Present from PowerShell Team: Community Technology Preview-3 (CTP3) of Windows PowerShell V2

  • Comments 24

While Santa and co. are getting busy for Christmas, the Windows PowerShell Team is pleased to release the third Community Technology Preview (CTP3) of Windows PowerShell V2!

First let us thank you for all your great feedback on CTP1 and CTP2.  This is your product so never be shy about letting us know what you want from it.  We made quite a few changes based upon your feedback.  That is the benefit of these CTPs, it allows us to change things before we release them.  That also means that if you wrote scripts that used the features we changed, they will have to be modified to run properly.  We’ll have some more changes before we release but we are getting to the end game so fewer and fewer things will change by smaller and smaller amounts going forward.

This release brings, among other things, performance improvements ... things will be faster/more efficient than before.  PowerShell remoting now allows implicit remoting where command execution appears to be local even though they are remote. We have added over 60 new cmdlets in this release ... cmdlets for adding/removing/renaming computers, cmdlets for event logs, cmdlets for WS-Man functionality and even a WS-Man provider.  The “graphical” host, Windows PowerShell ISE, now supports a graphical debugger, context sensitive F1 help and a programmable interface for you to party on.

These are just a few of the new features we have packaged in this CTP3 release. Additionally this CTP3 includes some simple updates... like new parameters to several existing cmdlets. More feature descriptions and details are in the Release Notes and in the “about” topics included with the installation.

Reminder to the brave souls who want to use these bits in a production environment ... Don’t, these bits are still CTP. This CTP is not a beta. This software is a pre-release version. It may not work the way a final version of the software does. These CTP3 bits have not gone through rigorous testing. Even with these caveats, we hope you would try them out and let us know your feedback.

Last but certainly not least, V2 builds upon Windows PowerShell 1.0 by providing backward compatibility – your 1.0 cmdlets and scripts will run on this CTP3 (with the exceptions noted in the Release Notes - mostly new keywords/cmdlets). If a working 1.0 script doesn’t run on V2 and is not in the known list of exceptions, please tell us about it!

Download Windows PowerShell V2 CTP3

Download WinRM 2.0 CTP3 (required for PowerShell remoting)

 

Hemant Mahawar [MSFT]
Program Manager
Windows PowerShell

Submitting Feedback

Please submit your feedback using the Connect Website (adding a CTP3: to the title), posting on the Windows PowerShell Discussion Group, or commenting on the Windows PowerShell Blog

Leave a Comment
  • Please add 6 and 4 and type the answer here:
  • Post
  • If anyone has this working on 2008 domain controllers please post.  Fine on Vista.  On  2008 DC PowerShell iteself is fine but WinRM gives event: Source"Windows Remote Management", EventID"10154".  Text:"The WinRM service failed to create the following SPNs: WSMAN/Orion.domain.com; WSMAN/Orion.

    Additional Data

    The error received was 8344: %%8344.

    User Action

    The SPNs can be created by an administrator using setspn.exe utility."

    Obviously, setting the SPNs manaually doesn't work:-(

    So no remoting to my DCs (this is in a lab BTW)

    One 64-bit, one 32-bit Server 2008

  • @Eric

    I totally sympathize and it takes great constraint not to jump on the table and join the rant.  I know exactly what a problem it is not to have XP support for remoting.  

    The issue is that we have to write a bunch of additional code to make things work on XP.  If we did that code now, we'd have to cut features from V2.  If we defer that code, we are able to take advantage of the fact that the downlevel release will happen after W7 to maximize the # of functions we ship in V2 and still support XP.  That's the calculus that lead to the current situation.  

    Honestly, the protocol team has been working super hard and are JUST going to get the features we need in.  If we were going to cut work - it would have been performance work and that would have been the wrong decision to make. If you compare the remoting performance between CTP2 and CTP3 (of course you'll have to ask your Vista friends about this :-) ) - I think you conclude that this was the right choice to make.

    In conclusion:

    1) Your frustration is TOTALLY understandable and justified.

    2) I have and will continue to fight vigorously to make as much as we can downlevel. (Note - there could always be technical issues that mean that the downlevel stuff is a subset of the functions.  Some argue that this is a reason to NOT ship downlevel.  I disagree.)

    3) I'm pretty confident that we made the right choices here. I know that this limits the feedback we get on the protocol (that is the big risk0 but we are getting pretty good feedback and it allowed us to maximize value to customers.

    Sorry for the headaches.  

    Best wishes and happy holidays!

    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

  • So, when can we see scriptable CLI CD/DVD writing?

  • Hi Do you think the release version will be available by mid March?

    We are considering integrating PowerShell in a consumer product.

    Thanks,

    John.

  • A comment on the backwards compatability is that you if you have powershell 2.x installed on the pc then then exchange2007 setup program won't work as it doesn't detect that powershell has been installed. This means you need to remove v2, install v1 and then install exchange. Although I suspect this is a bug in Exchange2007(sp1) it's a right pain.  I've yet to try the next (logical) step of then upgrading to powershell 2 after exchange has been installed, but for that I'm going to have to set it up in a lab environment......

  • The features discussed in this blog post depend on PowerShell CTP3 release. Details about PowerShell

  • The features discussed in this blog post depend on PowerShell CTP3 release. Details about PowerShell

  • The features discussed in this blog post depend on PowerShell CTP3 release. Details about PowerShell

  • Please, could you give the correct url to download the PowerShell v2.0 CTP3. the link for download says the file doesn t exist?

Page 2 of 2 (24 items) 12