WSMan Enhancements in PowerShell 2.0

infoblog » WSMan Enhancements in PowerShell 2.0

infoblog » WSMan Enhancements in PowerShell 2.0 — Thu, 26 Mar 2009 04:11:45 GMT

PingBack from http://blog.a-foton.ru/index.php/2009/03/26/wsman-enhancements-in-powershell-20/

re: WSMan Enhancements in PowerShell 2.0

Aleksandar — Thu, 26 Mar 2009 18:03:34 GMT

When I run Set-WSManQuickConfig cmdlet on a freshly installed Windows 7 machine I get an error "Unable to check the status of the firewall.". PS console is elevated, the firewall service is running, and the machine is NOT CONNECTED to any network (maybe that's the problem?). If I stop the firewall service and run the cmdlet again I get:

"WinRM already is set up to receive requests on this machine.

WinRM has been updated for remote management.

Created a WinRM listener..."

New start of the firewall service causes the same error.

When I've checked firewall settings, Windows Remote Management (HTTP-In) rules weren't enabled.

Could you shed some light on this problem? Thanks.

re: WSMan Enhancements in PowerShell 2.0

Raghu Shantha [MSFT] — Thu, 26 Mar 2009 21:58:30 GMT

WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change the network connection type to either Domain or Private and try again.

http://www.vistax64.com/tutorials/124812-network-location-type-change.html

re: WSMan Enhancements in PowerShell 2.0

Raghu Shantha [MSFT] — Fri, 03 Apr 2009 03:19:40 GMT

Setting Network Location to Private using PowerShell

http://blogs.msdn.com/powershell/archive/2009/04/03/setting-network-location-to-private.aspx

re: WSMan Enhancements in PowerShell 2.0

Claria — Wed, 28 Oct 2009 23:26:54 GMT

Could u please be more clear about that problem and why on a public network we couldn't apply the Winrm command??

WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change the network connection type to either Domain or Private and try again.