help translating winrm authendication to powershell

This is a command using winrm that will access a remote system that has CIM 
support. 

winrm e cimv2/CIM_ComputerSystem -r:https://192.168.3.21:9997 -a:Digest 
-u:username -p:password - skipCNcheck -skipCACheck

It is simple to get the local system information using powershell with 
syntax such as:

get-wmiobject -class CIM_ComputerSystem

What is not so obvious and difficult to find in numerous search attempts is 
how to access a remote system that requires the parameters found in the above 
winrm example.

Is this possible? How?

In V1 PowerShell you can't pass those parameters unless you use .NET code to 
access WMI.  The get-wmiobject in the November CTP for V2 has enhancements 
that enable this
-- 
Richard Siddaway
All scripts are supplied "as is" and with no warranty 
PowerShell MVP
Blog: http://richardsiddaway.spaces.live.com/
PowerShell User Group: http://www.get-psuguk.org.uk


"mandankid" wrote:

> This is a command using winrm that will access a remote system that has CIM

> support. 
> 
> winrm e cimv2/CIM_ComputerSystem -r:https://192.168.3.21:9997 -a:Digest 
> -u:username -p:password - skipCNcheck -skipCACheck
> 
> It is simple to get the local system information using powershell with 
> syntax such as:
> 
> get-wmiobject -class CIM_ComputerSystem
> 
> What is not so obvious and difficult to find in numerous search attempts is

> how to access a remote system that requires the parameters found in the
above 
> winrm example.
> 
> Is this possible? How?

The PowerShell upgrade has been installed. The help screens and user guide 
make no mention of digest or basic. The 4 key needs are to specify https, 
digest, and presumably avoid the two certificate checks. Now that a version 
that can support these is installed, how is it done?

"RichS [MVP]" wrote:

> In V1 PowerShell you can't pass those parameters unless you use .NET code
to 
> access WMI.  The get-wmiobject in the November CTP for V2 has enhancements

> that enable this
> -- 
> Richard Siddaway
> All scripts are supplied "as is" and with no warranty 
> PowerShell MVP
> Blog: http://richardsiddaway.spaces.live.com/
> PowerShell User Group: http://www.get-psuguk.org.uk
> 
> 
> "mandankid" wrote:
> 
> > This is a command using winrm that will access a remote system that
has CIM 
> > support. 
> > 
> > winrm e cimv2/CIM_ComputerSystem -r:https://192.168.3.21:9997
-a:Digest 
> > -u:username -p:password - skipCNcheck -skipCACheck
> > 
> > It is simple to get the local system information using powershell with

> > syntax such as:
> > 
> > get-wmiobject -class CIM_ComputerSystem
> > 
> > What is not so obvious and difficult to find in numerous search
attempts is 
> > how to access a remote system that requires the parameters found in
the above 
> > winrm example.
> > 
> > Is this possible? How?