PowerShell 2.0 CTP

WS-Management v1.1 is a prerequisite to installation. Is this
intentional. If so PowerShell is growing by 30-40%. It seems to me
the functions of PowerShell should simply be limited by what is
available rather than requiring various prerequisites. Dependencies
are expensive for developers, testers, support and end users.

Otherwise, both WS_M and Powershell installed smoothly. Most of
my scripts still run (haven't checked them all). No complains so far.
NICE WORK!!
Ed

Yes. It is needed for the remoting functionality as detailed in posts on the
PowerShell Team blog
--
Richard Siddaway
Please note that all scripts are supplied "as is" and with no warranty
Blog: http://richardsiddaway.spaces.live.com/
PowerShell User Group: http://www.get-psuguk.org.uk


"egb" wrote:

On Nov 6, 4:46 pm, RichS <Ri...@xxxxxx> wrote: It's also needed for the new background job functionality it appears.
Local psjobs are actually routed through wcf/winrm to be created
locally; fair enough - why bother with two interfaces when both jobs
are effectively isolated.

Regarding Start-Psjob and passing a new runspace to be used, has
anyone succesfully created a new runspace using new-runspace? I just
get "access is denied"

New-Runspace : [localhost] Access is denied.
At line:1 char:13
+ new-runspace <<<<

This is _after_ running Configure-Wsman.ps1 - I also have vmware
installed and I noticed that winrm was configured for my local i/f and
the two virtual vmware ones.

- Oisin

In message <BB993491-5CE9-445E-B940-F9C37D9E7C6F@xxxxxx>, egb
<egb@xxxxxx> writes Yes - required for remoting.
Possibly - but it's required for remoting. And I think it a pretty good
solution.
So else how would you do remoting? The WRM approach is pretty darned
elegant. At some point, I'd expect WRM to be installed by default.
Yes indeed.
<aol>!

--
Thomas Lee
doctordns@xxxxxx
MVP - Admin Frameworks and Security

"Thomas Lee" <tfl@xxxxxx> wrote in message
news:dRMPOY1ekOMHFAUE@xxxxxx I think the best situation would be that PowerShell always installs but, if
you try to do something that requires WinRM, it fails with an appropriate
error message.

Of course, once people see how cool it is, they'll be installing WinRM on
everything!

Which OS?

I tried new-runspace on XP SP2 and had no problems. If running XP,
there is an issue with winrm and IIS both running.

Marco

--
Microsoft MVP - Windows PowerShell
http://www.microsoft.com/mvp

PowerGadgets MVP
http://www.powergadgets.com/mvp

Blog:
http://marcoshaw.blogspot.com

In message <3DF53AAC-C6BE-4354-8AE3-FAA37B8F1110@xxxxxx>, John
Vottero <JVottero@xxxxxx> writes
The best situation is if WinRM is installed by the OS!
All the more reason to insist on it.

Of course, remember this is just a CTP. For CTPs, there are regurally
requirements that won't be there in the final build.

Personally, I feel that WinRM should just be installed by the PowerShell
installer if it's not already on the box. Whether you turn it on or even
configure it, is then up to you.

--
Thomas Lee
doctordns@xxxxxx
MVP - Admin Frameworks and Security

I'm afraid I can't agree. With this approach you will end up with a lot more
people calling for support. One of the major new features of V2 is remoting
so it makes more sense to require the underlying technologies to be installed.
--
Richard Siddaway
Please note that all scripts are supplied "as is" and with no warranty
Blog: http://richardsiddaway.spaces.live.com/
PowerShell User Group: http://www.get-psuguk.org.uk


"John Vottero" wrote:

Thomas Lee pisze: Now WinRM is available only for Windows XP in English version. I want to
try PowerShell V2 CTP but I can't find WinRM for Polish XP.

> Personally, I feel that WinRM should just be installed by the PowerShell
You think a service that is listening to port 80 should be installed by a
new shell?
-> http://msdn2.microsoft.com/en-us/library/aa384464.aspx

Hope you do not do that on a webserver in a DMZ