![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
![]() |
| |
| | #1 (permalink) |
| | 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 igest-u:username -p assword - skipCNcheck -skipCACheckIt 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? |
My System Specs![]() |
| | #2 (permalink) |
| | RE: help translating winrm authendication to powershell 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: Quote: > 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 igest> -u:username -p assword - 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? > |
My System Specs![]() |
| | #3 (permalink) |
| | RE: help translating winrm authendication to powershell 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: Quote: > 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: > Quote: > > 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 igest> > -u:username -p assword - 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? > > |
My System Specs![]() |
![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Powershell WinRM Exchange and ILM 2007 | PowerShell | |||
| WinRM and PowerShell V2 CTP3 | PowerShell | |||
| winrm in powershell vs. in cmd.exe | PowerShell | |||
| Help Translating "NamesTranlsate" from VBS to Powershell | PowerShell | |||
| WinRM from PowerShell | PowerShell | |||