Get-process -computerName
Returns this error:
Get-Process : A parameter cannot be found that matches parameter name
'computerName'.
Same thing when using the -ComputerName parameter with get-service. Is this
a known issue?
Get-process -computerName
Returns this error:
Get-Process : A parameter cannot be found that matches parameter name
'computerName'.
Same thing when using the -ComputerName parameter with get-service. Is this
a known issue?
You have to use Invoke-Expression
Invoke-Expression -computername xxxxxx {Get-Process}
you need PowerShell V2 on both machines and win-rm installed and configured
on both
--
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
"XXX" wrote:
> Get-process -computerName
>
> Returns this error:
>
> Get-Process : A parameter cannot be found that matches parameter name
> 'computerName'.
>
> Same thing when using the -ComputerName parameter with get-service. Is this
> a known issue?
>
>
>
XXX wrote:Like Richard says, and just to clarify that the above is an error in the
> Get-process -computerName
>
> Returns this error:
>
> Get-Process : A parameter cannot be found that matches parameter name
> 'computerName'.
>
> Same thing when using the -ComputerName parameter with get-service. Is this
> a known issue?
>
>
help file as the -computerName parameter is not valid.
You can also check: get-command get-process|format-list
Marco
--
Microsoft MVP - Windows PowerShell
http://www.microsoft.com/mvp
PowerGadgets MVP
http://www.powergadgets.com/mvp
Blog:
http://marcoshaw.blogspot.com
Apologizes for that. On that one, the documentation reflects our desires
not our code. :-)
We have this working in the code now so the next release will have it.
jps
--
Jeffrey P. Snover[MSFT]
Partner Architect, Windows Server
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
"Marco Shaw [MVP]" <marco.shaw@_NO_SPAM_gmail.com> wrote in message
news:OMs7BsfWIHA.5348@xxxxxx
> XXX wrote:>
>> Get-process -computerName
>>
>> Returns this error:
>>
>> Get-Process : A parameter cannot be found that matches parameter name
>> 'computerName'.
>>
>> Same thing when using the -ComputerName parameter with get-service. Is
>> this a known issue?
> Like Richard says, and just to clarify that the above is an error in the
> help file as the -computerName parameter is not valid.
>
> You can also check: get-command get-process|format-list
>
> Marco
>
> --
> Microsoft MVP - Windows PowerShell
> http://www.microsoft.com/mvp
>
> PowerGadgets MVP
> http://www.powergadgets.com/mvp
>
> Blog:
> http://marcoshaw.blogspot.com
Thanks for the update Jeffrey!
I'm really looking forward to this ability. Of course I won't get near as
much exercise and it's all your fault! haha
Regards...
-Fred.
"Jeffrey Snover[MSFT]" <jsnover@xxxxxx> wrote in message
news:7503E0A4-3D8B-472B-A838-7F08E559BD2B@xxxxxx
> Apologizes for that. On that one, the documentation reflects our desires
> not our code. :-)
> We have this working in the code now so the next release will have it.
> jps
>
> --
> Jeffrey P. Snover[MSFT]
> Partner Architect, Windows Server
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Marco Shaw [MVP]" <marco.shaw@_NO_SPAM_gmail.com> wrote in message
> news:OMs7BsfWIHA.5348@xxxxxx>
>> XXX wrote:>>
>>> Get-process -computerName
>>>
>>> Returns this error:
>>>
>>> Get-Process : A parameter cannot be found that matches parameter name
>>> 'computerName'.
>>>
>>> Same thing when using the -ComputerName parameter with get-service. Is
>>> this a known issue?
>> Like Richard says, and just to clarify that the above is an error in the
>> help file as the -computerName parameter is not valid.
>>
>> You can also check: get-command get-process|format-list
>>
>> Marco
>>
>> --
>> Microsoft MVP - Windows PowerShell
>> http://www.microsoft.com/mvp
>>
>> PowerGadgets MVP
>> http://www.powergadgets.com/mvp
>>
>> Blog:
>> http://marcoshaw.blogspot.com
XXX wrote:It isn't supported in the current CTP, most of this can be retrieved via
> Get-process -computerName
>
> Returns this error:
>
> Get-Process : A parameter cannot be found that matches parameter name
> 'computerName'.
>
> Same thing when using the -ComputerName parameter with get-service. Is this
> a known issue?
>
>
other means.
One method is WMI. If RPC is an issue and that's why you don't
currently use WMI, you should be able to tunnel your WMI requests via
WinRM (so it uses HTTP or HTTPS).
I'm trying out another option also...
I'll provide examples maybe by tomorrow.
Marco
It's been a while since I was playing with V2 but isn't -computerName a
parameter for the invoke-expression cmdlet ?
So it would be something like invoke-expression -computername ServerA
"Get-Process"
Andy Schneider
http://www.get-powershell.com
"Marco Shaw [MVP]" <marco.shaw@_NO_SPAM_gmail.com> wrote in message
news:OixHHzSXIHA.1168@xxxxxx
> XXX wrote:>
>> Get-process -computerName
>>
>> Returns this error:
>>
>> Get-Process : A parameter cannot be found that matches parameter name
>> 'computerName'.
>>
>> Same thing when using the -ComputerName parameter with get-service. Is
>> this a known issue?
> It isn't supported in the current CTP, most of this can be retrieved via
> other means.
>
> One method is WMI. If RPC is an issue and that's why you don't currently
> use WMI, you should be able to tunnel your WMI requests via WinRM (so it
> uses HTTP or HTTPS).
>
> I'm trying out another option also...
>
> I'll provide examples maybe by tomorrow.
>
> Marco
| Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| PowerShell Remoting equivalent of SSH scp | Dave Clarke | PowerShell | 2 | 19 Feb 2009 |
| Widnow's Powershell Remoting | kiranasileti | PowerShell | 5 | 25 Nov 2008 |
| Windows powershell Remoting -ScriptBlcok | kiranasileti | PowerShell | 0 | 23 Oct 2008 |
| Powershell 2.0 with remoting : ok what is Remoting ? | IT Staff | PowerShell | 4 | 07 Dec 2007 |
| Powershell 2.0 and remoting | Nex6 | PowerShell | 5 | 30 Nov 2007 |