A WinRM runspace pool

winrm

So I am having an issues installing/removing features and rolls from a Windows Server 2012 R2 Server. I consistently come up with this error no matter which service, role, or feature I installed called WinRM Runspace pool invalid. Now I know the two servers can talk to each other through Server Manager and I know they are using WinRM and WSMan but I don't understand how if they can talk to each other how their getting a Runspace pool error. So I guess to better understand the error after all of the fixes I have tried is to try and understand what a "Runspace Pool" is and how to troubleshoot it? I can't find any information from Microsoft on what it is. Can anyone explain and maybe how it affects my error I am getting?

Best Answer

Found the issue. Someone setup a different GPO that was above the one I was working on with the "Enable Windows Remote Shell" set to "Disabled". Set to "Not Configured" in my Patching GPO and can now Add/Remove Features.

Location: Computer Management\Policies\Administrative Templates\Windows Components\Windows Remote Shell

As stated in this question this setting can be very confusing. Since it says that setting it to "Not Configured" or "Disabled" it should be allowing the traffic and the use of the WinRM Pool but I guess for it to be fully accessible, then you have to have it set to "Not Configured"

Related Solutions

WinRM Failures – How to Fix Remote PowerShell Issues on Windows Server 2012 R2

Finally solved it, helped by the evidence I recently added to the question:

netsh http show iplist

IP addresses present in the IP listen list:
-------------------------------------------

127.0.0.1

On systems where this was working, that list was empty. This seemed rather counter-intuitive to me at first. Nevertheless, I gave this a go:

> netsh http delete iplisten ipaddress=127.0.0.1

Immediately after, I notice this output from netstat:

>netstat -anp tcp

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5985           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:47001          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49155          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49175          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49179          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49190          0.0.0.0:0              LISTENING
  TCP    10.115.63.107:139      0.0.0.0:0              LISTENING
  TCP    10.115.63.107:3389     10.115.13.25:64873     ESTABLISHED
  TCP    10.115.63.107:49235    192.168.40.146:445     ESTABLISHED
  TCP    10.115.63.107:49291    192.168.40.45:8014     ESTABLISHED
  TCP    169.254.34.30:139      0.0.0.0:0              LISTENING

And indeed, WinRM works like it should.

I surmise, via testing, that if no HTTP listener is configured, then all HTTP listeners will bind to the default entity: 0.0.0.0. Because a loopback address was configured as a listener address, the listener was binding to this address instead.

At some point, I must have taken some action that caused this configuration, though I'm not sure how. At any rate, it's working fine now. Thanks all.

Powershell – WinRM cannot connect

The winrm quickconfig command (or the abbreviated version winrm qc) performs the following operations: Starts the WinRM service, and sets the service startup type to auto-start. Configures a listener for the ports that send and receive WS-Management protocol messages using either HTTP or HTTPS on any IP address.

winrm quickconfig

Best Answer

Related Solutions

WinRM Failures – How to Fix Remote PowerShell Issues on Windows Server 2012 R2

Powershell – WinRM cannot connect

Related Topic