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

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

Brad — Tue, 23 Dec 2008 06:16:55 GMT

Yeah!

You guys are the best!

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

Tue, 23 Dec 2008 06:29:37 GMT

PingBack from http://www.codedstyle.com/early-christmas-present-from-powershell-team-community-technology-preview-3-ctp3-of-windows-powershell-v2/

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

Glenn Sizemore — Tue, 23 Dec 2008 08:41:47 GMT

Don't worry about us early adopters. Who cares if you break my scripts... This isn't C# or VBScript it didn't take me that long to write them in the first place. Given the current release cycle, Don't worry about us. Just get it right!

By the time V2 is rolled out in production around the world (3-12 months after GA). PowerShell will have reached a critical mass. Like those who used monad before, the CTP crowd will be but a whisper...

As long as you get it right, who cares! Feel free to break EVERYTHING with beta1. If your road map says it's the right thing to do. Part of what has made POSH so successful is your unorthodox approach to solving complex problems. At this point "in powershell I trust", If you tell me that X is the best thing for everyone... I may not like it, but I'm not going back to cmd/wsh

~Glenn

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

Larry Smith — Tue, 23 Dec 2008 09:43:20 GMT

Sorry to rain on your parade guys, but I've got one major gripe even before I download the stuff.

Could whoever posted these file to download PLEASE GIVE THEM INTELLIGENT NAMES?!?

The Help file was OK, WindowsPowerShellV2_CTP3_SDK.chm. It has the fact that this is for a) PowerShell, b) is V2, and c) is for CTP3.

But the other files were generic. PowerShell_Setup_x86.msi didn't mention V2 or CTP3. And releaseNotes.rtf? Strike 3!

PowerShell V2 (CTP3) is public

Shay Levy — Tue, 23 Dec 2008 09:52:35 GMT

PowerShell V2 Community Technology Preview 3 is public with lots of goodies. Read the announcement at

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

Stuart Henderson — Tue, 23 Dec 2008 12:20:16 GMT

Oh my god...it's full of stars!

Community Technology Preview-3 (CTP3) of Windows PowerShell V2 available from Powershell Team

Scott Moss at myITforum.com — Tue, 23 Dec 2008 15:26:28 GMT

Just in time for Christmas, CTP3 of Powershell v2 was realeased last nigth and is available for download

v2 CTP3: Running PowerShell silently

get-powershellblog — Tue, 23 Dec 2008 16:22:12 GMT

Well, if you haven't heard, v2 CTP3 is out. Check it HERE . This new release provides a feature where

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

Eric Walker — Tue, 23 Dec 2008 17:22:50 GMT

Could we please for the love of all that is holy actually harmonize the releases between WinRM and PowerShell? I mean, if PowerShell has a dependency on WinRM, and PowerShell CTP3 clearly supports XP, why the HELL can't I get WinRM CTP3 to support XP?????

FIX THIS!! This is the THIRD time you've done this since becoming dependent on WinRM and EACH time you've put out an update, you lock yourselves into Vista and Server 2008 ONLY even though your product SUPPORTS XP!!!!

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

Smith Catar — Tue, 23 Dec 2008 21:33:04 GMT

Now I can Minimize and hide powershell.exe window...great!!!

But PowerShell ISE doesn't react when I click 'Windows PowerShell Help F1' menu...

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

SPowser — Wed, 24 Dec 2008 03:00:22 GMT

Eric,

Feel your pain but there are alternatives for the time being. nSofware has their Powershell Server which works in much the same way that WinRM does. If your hair is on fire, as Jeffrey would say, go with what works now.

-Shane

Configuring PowerShell for Remoting – Part 1

Windows PowerShell Blog — Wed, 24 Dec 2008 06:48:13 GMT

Configuring PowerShell for Remoting – Part 1 The features discussed in this blog post depend on PowerShell

Configuring PowerShell for Remoting – Part 1

Windows PowerShell Team Blog — Wed, 24 Dec 2008 11:17:07 GMT

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

Visual Studio Links #92

Visual Studio Hacks — Wed, 24 Dec 2008 16:08:32 GMT

My latest in a series of the weekly, or more often, summary of interesting links I come across related to Visual Studio. Greg Duncan posted a link to the CodePlex project that provides a managed interface to Esent , the embedded database that ships with

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

Eric Walker — Wed, 24 Dec 2008 17:31:17 GMT

Shane: Thanks, and I get that I went overboard in my previous post, but it's not like this hasn't been discussed AND addressed before. It's like all of Microsoft has been given the mantra "Do whatever it takes to PUSH customers off XP and to Vista."

Unfortunately for folks like myself that prefer to keep up with the latest in tools and technology, we aren't always the final arbiter in what platforms we support, and continually having to lag behind everyone else to use something that is supported on XP (but one of it's dependencies prefers to support Vista...) is creating an increasingly bad taste in my mouth.

I have Vista at home and use it to teach myself the skills I'll need to support it when the time comes, but there are LOTS of folks like myself who still support primarily 2000 and XP and have NO say in when that will change.

This is right up there with PS not working on 2k (because it does, it's strictly an installer limit in checking the O/S version)

PowerShell Team: My apologies for my previous post's unwarranted vitriol. It's the holidays and you guys/gals probably busted hump to get these bits out the door, and it IS appreciated! My point was, this has been an on-going issue since deciding on WinRM as a dependency for remoting and I've brought the point up and had it addressed before in previous CTP bits for WinRM (they release only a .mui first, and then much later an .msi)

In any case, I'll be playing around with the new features (that I can) over the holidays and thanks again for this early Christmas present (even if I'm more the Grinch than Saint Nick!)

Merry Saturnalia!

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

Chris Warwick — Wed, 24 Dec 2008 19:56:09 GMT

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

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

PowerShellTeam — Wed, 24 Dec 2008 20:48:05 GMT

@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

Command line burning of CD/DVDs yet?

Paul Borella — Sat, 27 Dec 2008 04:16:09 GMT

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

PowerShell 2.0 Release Date

John — Tue, 30 Dec 2008 11:55:20 GMT

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

We are considering integrating PowerShell in a consumer product.

Thanks,

John.

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

Andy Helsby — Wed, 07 Jan 2009 15:32:05 GMT

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......

Configuring PowerShell for Remoting – Part 2 (Fan-In)

Windows PowerShell Blog — Fri, 10 Apr 2009 10:40:09 GMT

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

Configuring PowerShell for Remoting – Part 2 (Fan-In)

PowerShell Team Blog (external) — Fri, 10 Apr 2009 12:11:46 GMT

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

Configuring PowerShell for Remoting – Part 2 (Fan-In)

Windows PowerShell Team Blog — Fri, 10 Apr 2009 12:16:41 GMT

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