Get-PowerShell | Enabling WinRM with Powershell

Andy Schneider is a Systems Engineer at Avanade, a company that was started in 2000 to merge leading enterprise technology solutions with cutting-edge business consulting capabilities. Andy is a member of the IT Infrastructure Hosting team for Avanade's IT Services. He focuses on virtualization using Hyper-V and has done a lot of work with NetApp storage devices. Andy uses PowerShell on a daily basis to manage Hyper-V, Microsoft Clusters, and NetApp storage devices. When Andy is not writing PowerShell code, you can find him spending time with his beautiful wife and two daughters or working out at Kirkland Crossfit. You can find Andy's personal PowerShell blog at http://get-powershell.com and follow him on twitter at @andys146.

<< Searching Event Logs with Powershell | WS-Man, Powershell, and MRTG >>

Enabling WinRM with Powershell

March 31, 2008 at 3:03 PM — Andy Schneider

a2f64f5e-8615-4b1f-8224-b8090de93d4b|0|.0

Posted in:

Tags:

NetApp PowerShell Toolkit has a PowerShell ProviderI was at the PowerShell Deep Dive the first half of this week. During a break, I had the chance to m...The How and Why of Learning to Use PowerShell (Part 1 of more than 1)Two years ago, I spent a great deal of time evangelizing PowerShell within my company and publicly a...Single Threaded Apartment in PowerShell V1I’ve been working on a Winform that I use in a PowerShell script and I needed to display HTML in the...

Comments (3) -

Kartik Maguwala says:

July 3, 2008 at 12:07 PM

Hello,
When try to execute
$r = New-Runspace internalComputername -cred domain\user
in Powershell gives me error
The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol.

I want to know what it means and how to solve?

I have also installed powershell 2.0 and WinRM to client machine to which i am trying to connect.