Vista - Powershell 2.0 Installation Experience

11-06-2007

- first it complains, that winrm is required: it does this by showing me a
dialog with an url that cannot be followes by clicking on it neither can I
use cut and paste to put the url into my browser
(silverlight update does the same stupid thing)

- after googeling I find the download page, select the german version of the
page: no download for xp-x86, just for server-x86 + server/xp-amd64

really nice .....

now my question:
why is this **dependency** on winrm necessary, even when I don't plan to
use this functionality?

http://msdn2.microsoft.com/en-us/library/aa384372.aspx says:

Windows Server 2003 R2: WinRM is not installed by default, but is available
as the Hardware Management feature through the Add/Remove System Components
feature in the Control Panel under Management and Monitoring Tools. Complete
installation and information about configuring WinRM using the Winrm
command-line tool is available online in the Hardware Management
Introduction which describes the WinRM and the IPMI features in Windows
Server 2003 R2.

so just because of powershell 2.0 I need to add an additional service: is
that correct?

Harald

11-06-2007

Harald Ums (2179630) wrote:

Quote:

> - first it complains, that winrm is required: it does this by showing me
> a dialog with an url that cannot be followes by clicking on it neither
> can I use cut and paste to put the url into my browser
> (silverlight update does the same stupid thing)

You might have been able to pick the window, then do a Ctrl-C. Then you
would have had to paste in Notepad or similar to extract the URL for IE.

Quote:

> - after googeling I find the download page, select the german version of
> the page: no download for xp-x86, just for server-x86 + server/xp-amd64
>
> really nice .....

OK, likely an oversight where "server-x86" is really for all.

Quote:

> now my question:
> why is this **dependency** on winrm necessary, even when I don't plan
> to use this functionality?

This is a *CTP*. Anything can and might happen/change, but your
feedback is important.

Marco

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

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

Blog:
http://marcoshaw.blogspot.com

11-06-2007

All said and written in the CTP pre-release notes on the Windows PowerShell
team blog:

"The PowerShell CTP includes Remoting features. This uses the latest (V1.1)
version of WS-Management
(also known as WINRM) and will not function property without this installed."

Here's the URL:
http://blogs.msdn.com/powershell/arc...uirements.aspx

-----
Shay Levi
$cript Fanatic
http://scriptolog.blogspot.com

Quote:

> - first it complains, that winrm is required: it does this by showing
> me a
> dialog with an url that cannot be followes by clicking on it neither
> can I
> use cut and paste to put the url into my browser
> (silverlight update does the same stupid thing)
> - after googeling I find the download page, select the german version
> of the page: no download for xp-x86, just for server-x86 +
> server/xp-amd64
>
> really nice .....
>
> now my question:
> why is this **dependency** on winrm necessary, even when I don't
> plan to
> use this functionality?
> http://msdn2.microsoft.com/en-us/library/aa384372.aspx says:
>
> Windows Server 2003 R2: WinRM is not installed by default, but is
> available as the Hardware Management feature through the Add/Remove
> System Components feature in the Control Panel under Management and
> Monitoring Tools. Complete installation and information about
> configuring WinRM using the Winrm command-line tool is available
> online in the Hardware Management Introduction which describes the
> WinRM and the IPMI features in Windows Server 2003 R2.
>
> so just because of powershell 2.0 I need to add an additional service:
> is that correct?
>
> Harald
>

11-06-2007

I've installed it on a clean XP virtual machine. Installation was easy -
just make sure WinRM is there. Longest part was installing .NET 3 to try the
editor.

Also installed PowerShell Community Extensions (PSCX), PowerGUI and PowerGUI
editor, Powergadgets and Powerpad.

Apart from needing to alter one type file on PSCX as detailed on Keith Hills
blog everything else installed and appears to run just great.

A home written application that uses PowerShell Runspace also works just fine.

As far as I can tell so far it all looks very good
--
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

"Shay Levi" wrote:

Quote:

> All said and written in the CTP pre-release notes on the Windows PowerShell
> team blog:
>
> "The PowerShell CTP includes Remoting features. This uses the latest (V1.1)
> version of WS-Management
> (also known as WINRM) and will not function property without this installed."
>
> Here's the URL:
> http://blogs.msdn.com/powershell/arc...uirements.aspx
>
> -----
> Shay Levi
> $cript Fanatic
> http://scriptolog.blogspot.com
>
>
>

Quote:

> > - first it complains, that winrm is required: it does this by showing
> > me a
> > dialog with an url that cannot be followes by clicking on it neither
> > can I
> > use cut and paste to put the url into my browser
> > (silverlight update does the same stupid thing)
> > - after googeling I find the download page, select the german version
> > of the page: no download for xp-x86, just for server-x86 +
> > server/xp-amd64
> >
> > really nice .....
> >
> > now my question:
> > why is this **dependency** on winrm necessary, even when I don't
> > plan to
> > use this functionality?
> > http://msdn2.microsoft.com/en-us/library/aa384372.aspx says:
> >
> > Windows Server 2003 R2: WinRM is not installed by default, but is
> > available as the Hardware Management feature through the Add/Remove
> > System Components feature in the Control Panel under Management and
> > Monitoring Tools. Complete installation and information about
> > configuring WinRM using the Winrm command-line tool is available
> > online in the Hardware Management Introduction which describes the
> > WinRM and the IPMI features in Windows Server 2003 R2.
> >
> > so just because of powershell 2.0 I need to add an additional service:
> > is that correct?
> >
> > Harald
> >

>
>
>

11-07-2007

"Marco Shaw [MVP]" <marco.shaw@_NO_SPAM_gmail.com> wrote in message
news:OP$$uFLIIHA.280@xxxxxx

Quote:

> Harald Ums (2179630) wrote:

Quote:

>> - first it complains, that winrm is required: it does this by showing me
>> a dialog with an url that cannot be followes by clicking on it neither
>> can I use cut and paste to put the url into my browser
>> (silverlight update does the same stupid thing)

>

do this does not work (I tried it)

Quote:

>
> OK, likely an oversight where "server-x86" is really for all.

No it is not - I tried to install the server version before I posted

Have you tested any of your recommendations before you posted?

11-07-2007

Minor problem
quest AD will not install ( this appears to be an issue of quest installer
lookinging explicitly for Powershell 1.0)

"RichS" wrote:

Quote:

> I've installed it on a clean XP virtual machine. Installation was easy -
> just make sure WinRM is there. Longest part was installing .NET 3 to try the
> editor.
>
> Also installed PowerShell Community Extensions (PSCX), PowerGUI and PowerGUI
> editor, Powergadgets and Powerpad.
>
> Apart from needing to alter one type file on PSCX as detailed on Keith Hills
> blog everything else installed and appears to run just great.
>
> A home written application that uses PowerShell Runspace also works just fine.
>
> As far as I can tell so far it all looks very good
> --
> 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
>
>
> "Shay Levi" wrote:
>

Quote:

> > All said and written in the CTP pre-release notes on the Windows PowerShell
> > team blog:
> >
> > "The PowerShell CTP includes Remoting features. This uses the latest (V1.1)
> > version of WS-Management
> > (also known as WINRM) and will not function property without this installed."
> >
> > Here's the URL:
> > http://blogs.msdn.com/powershell/arc...uirements.aspx
> >
> > -----
> > Shay Levi
> > $cript Fanatic
> > http://scriptolog.blogspot.com
> >
> >
> >

Quote:

> > > - first it complains, that winrm is required: it does this by showing
> > > me a
> > > dialog with an url that cannot be followes by clicking on it neither
> > > can I
> > > use cut and paste to put the url into my browser
> > > (silverlight update does the same stupid thing)
> > > - after googeling I find the download page, select the german version
> > > of the page: no download for xp-x86, just for server-x86 +
> > > server/xp-amd64
> > >
> > > really nice .....
> > >
> > > now my question:
> > > why is this **dependency** on winrm necessary, even when I don't
> > > plan to
> > > use this functionality?
> > > http://msdn2.microsoft.com/en-us/library/aa384372.aspx says:
> > >
> > > Windows Server 2003 R2: WinRM is not installed by default, but is
> > > available as the Hardware Management feature through the Add/Remove
> > > System Components feature in the Control Panel under Management and
> > > Monitoring Tools. Complete installation and information about
> > > configuring WinRM using the Winrm command-line tool is available
> > > online in the Hardware Management Introduction which describes the
> > > WinRM and the IPMI features in Windows Server 2003 R2.
> > >
> > > so just because of powershell 2.0 I need to add an additional service:
> > > is that correct?
> > >
> > > Harald
> > >

> >
> >
> >

11-07-2007

FYI
workaround for this if you use Quest ad stuff
change

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine]
PowerShellVersion

from 2.0 to 1.0
"voodooking" wrote:

Quote:

> Minor problem
> quest AD will not install ( this appears to be an issue of quest installer
> lookinging explicitly for Powershell 1.0)
>
> "RichS" wrote:
>

Quote:

> > I've installed it on a clean XP virtual machine. Installation was easy -
> > just make sure WinRM is there. Longest part was installing .NET 3 to try the
> > editor.
> >
> > Also installed PowerShell Community Extensions (PSCX), PowerGUI and PowerGUI
> > editor, Powergadgets and Powerpad.
> >
> > Apart from needing to alter one type file on PSCX as detailed on Keith Hills
> > blog everything else installed and appears to run just great.
> >
> > A home written application that uses PowerShell Runspace also works just fine.
> >
> > As far as I can tell so far it all looks very good
> > --
> > 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
> >
> >
> > "Shay Levi" wrote:
> >

Quote:

> > > All said and written in the CTP pre-release notes on the Windows PowerShell
> > > team blog:
> > >
> > > "The PowerShell CTP includes Remoting features. This uses the latest (V1.1)
> > > version of WS-Management
> > > (also known as WINRM) and will not function property without this installed."
> > >
> > > Here's the URL:
> > > http://blogs.msdn.com/powershell/arc...uirements.aspx
> > >
> > > -----
> > > Shay Levi
> > > $cript Fanatic
> > > http://scriptolog.blogspot.com
> > >
> > >
> > >
> > > > - first it complains, that winrm is required: it does this by showing
> > > > me a
> > > > dialog with an url that cannot be followes by clicking on it neither
> > > > can I
> > > > use cut and paste to put the url into my browser
> > > > (silverlight update does the same stupid thing)
> > > > - after googeling I find the download page, select the german version
> > > > of the page: no download for xp-x86, just for server-x86 +
> > > > server/xp-amd64
> > > >
> > > > really nice .....
> > > >
> > > > now my question:
> > > > why is this **dependency** on winrm necessary, even when I don't
> > > > plan to
> > > > use this functionality?
> > > > http://msdn2.microsoft.com/en-us/library/aa384372.aspx says:
> > > >
> > > > Windows Server 2003 R2: WinRM is not installed by default, but is
> > > > available as the Hardware Management feature through the Add/Remove
> > > > System Components feature in the Control Panel under Management and
> > > > Monitoring Tools. Complete installation and information about
> > > > configuring WinRM using the Winrm command-line tool is available
> > > > online in the Hardware Management Introduction which describes the
> > > > WinRM and the IPMI features in Windows Server 2003 R2.
> > > >
> > > > so just because of powershell 2.0 I need to add an additional service:
> > > > is that correct?
> > > >
> > > > Harald
> > > >
> > >
> > >
> > >

11-07-2007

Granted the current bits require WinRM, but what if you have no plans to
ever use the remoting feature as was offered by the original poster? I can
see his point about being forced to install an unecessary service. Perhaps
later releases can make remoting an optional component. I expect most
admins will take advantage of remoting, but maybe we should leave that up to
them and not make decisions for them.

--
Jeffery Hicks
Microsoft PowerShell MVP
http://www.scriptinganswers.com
http://blog.sapien.com

Now Available: WSH and VBScript Core: TFM
Coming Soon: Windows PowerShell: TFM 2nd Ed.
"Shay Levi" <no@xxxxxx> wrote in message
news:8766a944cb658c9eed99afc6914@xxxxxx

Quote:

> All said and written in the CTP pre-release notes on the Windows
> PowerShell team blog:
>
> "The PowerShell CTP includes Remoting features. This uses the latest
> (V1.1) version of WS-Management (also known as WINRM) and will not
> function property without this installed."
>
> Here's the URL:
> http://blogs.msdn.com/powershell/arc...uirements.aspx
>
> -----
> Shay Levi
> $cript Fanatic
> http://scriptolog.blogspot.com
>
>
>

Quote:

>> - first it complains, that winrm is required: it does this by showing
>> me a
>> dialog with an url that cannot be followes by clicking on it neither
>> can I
>> use cut and paste to put the url into my browser
>> (silverlight update does the same stupid thing)
>> - after googeling I find the download page, select the german version
>> of the page: no download for xp-x86, just for server-x86 +
>> server/xp-amd64
>>
>> really nice .....
>>
>> now my question:
>> why is this **dependency** on winrm necessary, even when I don't
>> plan to
>> use this functionality?
>> http://msdn2.microsoft.com/en-us/library/aa384372.aspx says:
>>
>> Windows Server 2003 R2: WinRM is not installed by default, but is
>> available as the Hardware Management feature through the Add/Remove
>> System Components feature in the Control Panel under Management and
>> Monitoring Tools. Complete installation and information about
>> configuring WinRM using the Winrm command-line tool is available
>> online in the Hardware Management Introduction which describes the
>> WinRM and the IPMI features in Windows Server 2003 R2.
>>
>> so just because of powershell 2.0 I need to add an additional service:
>> is that correct?
>>
>> Harald
>>

>
>

12-06-2007

Quote:

> Have you tested any of your recommendations before you posted?

I'm sorry, if I made a few mistakes. I was not able to reproduce any of
your problems, but was still trying to help.

Marco

11-06-2007	#1 (permalink)
Harald Ums \(2179630\) n/a posts	Powershell 2.0 Installation Experience - first it complains, that winrm is required: it does this by showing me a dialog with an url that cannot be followes by clicking on it neither can I use cut and paste to put the url into my browser (silverlight update does the same stupid thing) - after googeling I find the download page, select the german version of the page: no download for xp-x86, just for server-x86 + server/xp-amd64 really nice ..... now my question: why is this dependency on winrm necessary, even when I don't plan to use this functionality? http://msdn2.microsoft.com/en-us/library/aa384372.aspx says: Windows Server 2003 R2: WinRM is not installed by default, but is available as the Hardware Management feature through the Add/Remove System Components feature in the Control Panel under Management and Monitoring Tools. Complete installation and information about configuring WinRM using the Winrm command-line tool is available online in the Hardware Management Introduction which describes the WinRM and the IPMI features in Windows Server 2003 R2. so just because of powershell 2.0 I need to add an additional service: is that correct? Harald
My System Specs

11-06-2007	#2 (permalink)
Marco Shaw [MVP] n/a posts	Re: Powershell 2.0 Installation Experience Harald Ums (2179630) wrote: Quote: > - first it complains, that winrm is required: it does this by showing me > a dialog with an url that cannot be followes by clicking on it neither > can I use cut and paste to put the url into my browser > (silverlight update does the same stupid thing) You might have been able to pick the window, then do a Ctrl-C. Then you would have had to paste in Notepad or similar to extract the URL for IE. Quote: > - after googeling I find the download page, select the german version of > the page: no download for xp-x86, just for server-x86 + server/xp-amd64 > > really nice ..... OK, likely an oversight where "server-x86" is really for all. Quote: > now my question: > why is this dependency on winrm necessary, even when I don't plan > to use this functionality? This is a CTP. Anything can and might happen/change, but your feedback is important. Marco -- Microsoft MVP - Windows PowerShell http://www.microsoft.com/mvp PowerGadgets MVP http://www.powergadgets.com/mvp Blog: http://marcoshaw.blogspot.com
My System Specs

11-06-2007	#3 (permalink)
Shay Levi n/a posts	Re: Powershell 2.0 Installation Experience All said and written in the CTP pre-release notes on the Windows PowerShell team blog: "The PowerShell CTP includes Remoting features. This uses the latest (V1.1) version of WS-Management (also known as WINRM) and will not function property without this installed." Here's the URL: http://blogs.msdn.com/powershell/arc...uirements.aspx ----- Shay Levi $cript Fanatic http://scriptolog.blogspot.com Quote: > - first it complains, that winrm is required: it does this by showing > me a > dialog with an url that cannot be followes by clicking on it neither > can I > use cut and paste to put the url into my browser > (silverlight update does the same stupid thing) > - after googeling I find the download page, select the german version > of the page: no download for xp-x86, just for server-x86 + > server/xp-amd64 > > really nice ..... > > now my question: > why is this dependency on winrm necessary, even when I don't > plan to > use this functionality? > http://msdn2.microsoft.com/en-us/library/aa384372.aspx says: > > Windows Server 2003 R2: WinRM is not installed by default, but is > available as the Hardware Management feature through the Add/Remove > System Components feature in the Control Panel under Management and > Monitoring Tools. Complete installation and information about > configuring WinRM using the Winrm command-line tool is available > online in the Hardware Management Introduction which describes the > WinRM and the IPMI features in Windows Server 2003 R2. > > so just because of powershell 2.0 I need to add an additional service: > is that correct? > > Harald >
My System Specs

11-06-2007	#4 (permalink)
RichS n/a posts	Re: Powershell 2.0 Installation Experience I've installed it on a clean XP virtual machine. Installation was easy - just make sure WinRM is there. Longest part was installing .NET 3 to try the editor. Also installed PowerShell Community Extensions (PSCX), PowerGUI and PowerGUI editor, Powergadgets and Powerpad. Apart from needing to alter one type file on PSCX as detailed on Keith Hills blog everything else installed and appears to run just great. A home written application that uses PowerShell Runspace also works just fine. As far as I can tell so far it all looks very good -- 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 "Shay Levi" wrote: Quote: > All said and written in the CTP pre-release notes on the Windows PowerShell > team blog: > > "The PowerShell CTP includes Remoting features. This uses the latest (V1.1) > version of WS-Management > (also known as WINRM) and will not function property without this installed." > > Here's the URL: > http://blogs.msdn.com/powershell/arc...uirements.aspx > > ----- > Shay Levi > $cript Fanatic > http://scriptolog.blogspot.com > > > Quote: > > - first it complains, that winrm is required: it does this by showing > > me a > > dialog with an url that cannot be followes by clicking on it neither > > can I > > use cut and paste to put the url into my browser > > (silverlight update does the same stupid thing) > > - after googeling I find the download page, select the german version > > of the page: no download for xp-x86, just for server-x86 + > > server/xp-amd64 > > > > really nice ..... > > > > now my question: > > why is this dependency on winrm necessary, even when I don't > > plan to > > use this functionality? > > http://msdn2.microsoft.com/en-us/library/aa384372.aspx says: > > > > Windows Server 2003 R2: WinRM is not installed by default, but is > > available as the Hardware Management feature through the Add/Remove > > System Components feature in the Control Panel under Management and > > Monitoring Tools. Complete installation and information about > > configuring WinRM using the Winrm command-line tool is available > > online in the Hardware Management Introduction which describes the > > WinRM and the IPMI features in Windows Server 2003 R2. > > > > so just because of powershell 2.0 I need to add an additional service: > > is that correct? > > > > Harald > > > > >
My System Specs

11-07-2007	#5 (permalink)
Harald Ums n/a posts	Re: Powershell 2.0 Installation Experience "Marco Shaw [MVP]" <marco.shaw@_NO_SPAM_gmail.com> wrote in message news:OP$$uFLIIHA.280@xxxxxx Quote: > Harald Ums (2179630) wrote: Quote: >> - first it complains, that winrm is required: it does this by showing me >> a dialog with an url that cannot be followes by clicking on it neither >> can I use cut and paste to put the url into my browser >> (silverlight update does the same stupid thing) > do this does not work (I tried it) Quote: > > OK, likely an oversight where "server-x86" is really for all. No it is not - I tried to install the server version before I posted Have you tested any of your recommendations before you posted?
My System Specs

11-07-2007	#6 (permalink)
voodooking n/a posts	Re: Powershell 2.0 Installation Experience Minor problem quest AD will not install ( this appears to be an issue of quest installer lookinging explicitly for Powershell 1.0) "RichS" wrote: Quote: > I've installed it on a clean XP virtual machine. Installation was easy - > just make sure WinRM is there. Longest part was installing .NET 3 to try the > editor. > > Also installed PowerShell Community Extensions (PSCX), PowerGUI and PowerGUI > editor, Powergadgets and Powerpad. > > Apart from needing to alter one type file on PSCX as detailed on Keith Hills > blog everything else installed and appears to run just great. > > A home written application that uses PowerShell Runspace also works just fine. > > As far as I can tell so far it all looks very good > -- > 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 > > > "Shay Levi" wrote: > Quote: > > All said and written in the CTP pre-release notes on the Windows PowerShell > > team blog: > > > > "The PowerShell CTP includes Remoting features. This uses the latest (V1.1) > > version of WS-Management > > (also known as WINRM) and will not function property without this installed." > > > > Here's the URL: > > http://blogs.msdn.com/powershell/arc...uirements.aspx > > > > ----- > > Shay Levi > > $cript Fanatic > > http://scriptolog.blogspot.com > > > > > > Quote: > > > - first it complains, that winrm is required: it does this by showing > > > me a > > > dialog with an url that cannot be followes by clicking on it neither > > > can I > > > use cut and paste to put the url into my browser > > > (silverlight update does the same stupid thing) > > > - after googeling I find the download page, select the german version > > > of the page: no download for xp-x86, just for server-x86 + > > > server/xp-amd64 > > > > > > really nice ..... > > > > > > now my question: > > > why is this dependency on winrm necessary, even when I don't > > > plan to > > > use this functionality? > > > http://msdn2.microsoft.com/en-us/library/aa384372.aspx says: > > > > > > Windows Server 2003 R2: WinRM is not installed by default, but is > > > available as the Hardware Management feature through the Add/Remove > > > System Components feature in the Control Panel under Management and > > > Monitoring Tools. Complete installation and information about > > > configuring WinRM using the Winrm command-line tool is available > > > online in the Hardware Management Introduction which describes the > > > WinRM and the IPMI features in Windows Server 2003 R2. > > > > > > so just because of powershell 2.0 I need to add an additional service: > > > is that correct? > > > > > > Harald > > > > > > > > >
My System Specs

11-07-2007	#7 (permalink)
voodooking n/a posts	Re: Powershell 2.0 Installation Experience FYI workaround for this if you use Quest ad stuff change [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine] PowerShellVersion from 2.0 to 1.0 "voodooking" wrote: Quote: > Minor problem > quest AD will not install ( this appears to be an issue of quest installer > lookinging explicitly for Powershell 1.0) > > "RichS" wrote: > Quote: > > I've installed it on a clean XP virtual machine. Installation was easy - > > just make sure WinRM is there. Longest part was installing .NET 3 to try the > > editor. > > > > Also installed PowerShell Community Extensions (PSCX), PowerGUI and PowerGUI > > editor, Powergadgets and Powerpad. > > > > Apart from needing to alter one type file on PSCX as detailed on Keith Hills > > blog everything else installed and appears to run just great. > > > > A home written application that uses PowerShell Runspace also works just fine. > > > > As far as I can tell so far it all looks very good > > -- > > 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 > > > > > > "Shay Levi" wrote: > > Quote: > > > All said and written in the CTP pre-release notes on the Windows PowerShell > > > team blog: > > > > > > "The PowerShell CTP includes Remoting features. This uses the latest (V1.1) > > > version of WS-Management > > > (also known as WINRM) and will not function property without this installed." > > > > > > Here's the URL: > > > http://blogs.msdn.com/powershell/arc...uirements.aspx > > > > > > ----- > > > Shay Levi > > > $cript Fanatic > > > http://scriptolog.blogspot.com > > > > > > > > > > > > > - first it complains, that winrm is required: it does this by showing > > > > me a > > > > dialog with an url that cannot be followes by clicking on it neither > > > > can I > > > > use cut and paste to put the url into my browser > > > > (silverlight update does the same stupid thing) > > > > - after googeling I find the download page, select the german version > > > > of the page: no download for xp-x86, just for server-x86 + > > > > server/xp-amd64 > > > > > > > > really nice ..... > > > > > > > > now my question: > > > > why is this dependency on winrm necessary, even when I don't > > > > plan to > > > > use this functionality? > > > > http://msdn2.microsoft.com/en-us/library/aa384372.aspx says: > > > > > > > > Windows Server 2003 R2: WinRM is not installed by default, but is > > > > available as the Hardware Management feature through the Add/Remove > > > > System Components feature in the Control Panel under Management and > > > > Monitoring Tools. Complete installation and information about > > > > configuring WinRM using the Winrm command-line tool is available > > > > online in the Hardware Management Introduction which describes the > > > > WinRM and the IPMI features in Windows Server 2003 R2. > > > > > > > > so just because of powershell 2.0 I need to add an additional service: > > > > is that correct? > > > > > > > > Harald > > > > > > > > > > > > >
My System Specs

11-07-2007	#8 (permalink)
Jeffery Hicks [MVP] n/a posts	Re: Powershell 2.0 Installation Experience Granted the current bits require WinRM, but what if you have no plans to ever use the remoting feature as was offered by the original poster? I can see his point about being forced to install an unecessary service. Perhaps later releases can make remoting an optional component. I expect most admins will take advantage of remoting, but maybe we should leave that up to them and not make decisions for them. -- Jeffery Hicks Microsoft PowerShell MVP http://www.scriptinganswers.com http://blog.sapien.com Now Available: WSH and VBScript Core: TFM Coming Soon: Windows PowerShell: TFM 2nd Ed. "Shay Levi" <no@xxxxxx> wrote in message news:8766a944cb658c9eed99afc6914@xxxxxx Quote: > All said and written in the CTP pre-release notes on the Windows > PowerShell team blog: > > "The PowerShell CTP includes Remoting features. This uses the latest > (V1.1) version of WS-Management (also known as WINRM) and will not > function property without this installed." > > Here's the URL: > http://blogs.msdn.com/powershell/arc...uirements.aspx > > ----- > Shay Levi > $cript Fanatic > http://scriptolog.blogspot.com > > > Quote: >> - first it complains, that winrm is required: it does this by showing >> me a >> dialog with an url that cannot be followes by clicking on it neither >> can I >> use cut and paste to put the url into my browser >> (silverlight update does the same stupid thing) >> - after googeling I find the download page, select the german version >> of the page: no download for xp-x86, just for server-x86 + >> server/xp-amd64 >> >> really nice ..... >> >> now my question: >> why is this dependency on winrm necessary, even when I don't >> plan to >> use this functionality? >> http://msdn2.microsoft.com/en-us/library/aa384372.aspx says: >> >> Windows Server 2003 R2: WinRM is not installed by default, but is >> available as the Hardware Management feature through the Add/Remove >> System Components feature in the Control Panel under Management and >> Monitoring Tools. Complete installation and information about >> configuring WinRM using the Winrm command-line tool is available >> online in the Hardware Management Introduction which describes the >> WinRM and the IPMI features in Windows Server 2003 R2. >> >> so just because of powershell 2.0 I need to add an additional service: >> is that correct? >> >> Harald >> > >
My System Specs

12-06-2007	#9 (permalink)
Marco Shaw [MVP] n/a posts	Re: Powershell 2.0 Installation Experience Quote: > Have you tested any of your recommendations before you posted? I'm sorry, if I made a few mistakes. I was not able to reproduce any of your problems, but was still trying to help. Marco
My System Specs

Similar Threads
Thread	Forum
Sample Vista SP2 Installation Experience	Windows Updates
Scripted Installation with PowerShell	PowerShell
powershell installation required?	PowerShell
Unattended installation switch for PowerShell?	PowerShell
My installation experience with Vista RC1 x86	Vista General