Otdfbt

I'm just about stumped with WinRM up to this point. Whenever I try to install any feature with the Server Manager, it hangs on "Starting Installation". When I install the feature with PowerShell, it works fine, only when I open up Server Manager to configure the feature after the installation I get a "failed to open the runspace pool" error. Configuring it via PowerShell works fine. Then, when I tried to configure DirectAccess with its Quick Start wizard, it gives me a "could not connect to the destination specified in the request" error.

Running "winrm quickconfig" produces this:

WinRM service is already running on this machine.
WinRM is already set up for remote management on this computer.
Then, in Event Viewer, I get this error when I try to do anything with Server Manager/configuring DirectAccess:

WSMan operation CreateShell failed, error code 2150858770
And it dosen't give me any information except that. This is the output of winrm get winrm/config:

PS C:WindowsSystem32WindowsPowerShellv1.0> winrm get winrm/config
Config
 MaxEnvelopeSizekb = 500
 MaxTimeoutms = 60000
 MaxBatchItems = 32000
 MaxProviderRequests = 4294967295
 Client
 NetworkDelayms = 5000
 URLPrefix = wsman
 AllowUnencrypted = false
 Auth
 Basic = true
 Digest = true
 Kerberos = true
 Negotiate = true
 Certificate = true
 CredSSP = false
 DefaultPorts
 HTTP = 5985
 HTTPS = 5986
 TrustedHosts = fs.towerdevs.xyz
 Service
 RootSDDL = O:NSG:BAD:P(A;;GA;;;BA)(A;;GR;;;IU)S:P(AU;FA;GA;;;WD)(AU;SA;GXGW;;;WD)
 MaxConcurrentOperations = 4294967295
 MaxConcurrentOperationsPerUser = 1500
 EnumerationTimeoutms = 240000
 MaxConnections = 300
 MaxPacketRetrievalTimeSeconds = 120
 AllowUnencrypted = false
 Auth
 Basic = false
 Kerberos = true
 Negotiate = true
 Certificate = false
 CredSSP = true
 CbtHardeningLevel = Relaxed
 DefaultPorts
 HTTP = 5985
 HTTPS = 5986
 IPv4Filter = *
 IPv6Filter = *
 EnableCompatibilityHttpListener = false
 EnableCompatibilityHttpsListener = false
 CertificateThumbprint = 80 aa c1 69 11 9d 87 b8 d8 7a 20 b8 ff 76 d2 3ddb dc 7b 7f
 AllowRemoteAccess = true
 Winrs
 AllowRemoteShellAccess = true [Source="GPO"]
 IdleTimeout = 7200000
 MaxConcurrentUsers = 10
 MaxShellRunTime = 2147483647
 MaxProcessesPerShell = 25
 MaxMemoryPerShellMB = 1024
 MaxShellsPerUser = 30

And winrm enumerate winrm/config/listener:

PS C:WindowsSystem32WindowsPowerShellv1.0> winrm enumerate winrm/config/listener
Listener
 Address = *
 Transport = HTTP
 Port = 5985
 Hostname
 Enabled = true
 URLPrefix = wsman
 CertificateThumbprint
 ListeningOn = 127.0.0.1, 169.254.164.229, 169.254.224.69, 192.168.1.109, ::1, fe80::5efe:169.254.164.229%17, fe80::5
efe:169.254.224.69%18, fe80::d13:6e93:f4dd:e045%12, fe80::84a1:52c5:715:a4e5%15, fe80::fdb7:1050:858e:9139%14

Listener
 Address = *
 Transport = HTTPS
 Port = 5986
 Hostname = fs.towerdevs.xyz
 Enabled = true
 URLPrefix = wsman
 CertificateThumbprint = 80 aa c1 69 11 9d 87 b8 d8 7a 20 b8 ff 76 d2 3ddb dc 7b 7f
 ListeningOn = 127.0.0.1, 169.254.164.229, 169.254.224.69, 192.168.1.109, ::1, fe80::5efe:169.254.164.229%17, fe80::5
efe:169.254.224.69%18, fe80::d13:6e93:f4dd:e045%12, fe80::84a1:52c5:715:a4e5%15, fe80::fdb7:1050:858e:9139%14

The server runs these roles/features:

Roles:

AD CS (Certification Authority)

AD DS (Domain Controller)

DNS Server

File and Storages Server (File Server & Storage Services)

Hyper-V

Remote Access (DirectAccess and VPN)

Web Server (IIS)

Windows Deployment Services

Features:

.NET Framework 3.5

.NET Framework 4.5

Bitlocker and Network Unlock

Enhanced Storage

Group Policy Management

Ink & Handwriting Services

Media Foundation

qWave

CMAK

RSAT

User Interfaces and Infrastructure

Windows Internal Database

Windows PowerShell

WPAS

Wireless LAN Service

Wow64 Support

And yes, I have tried resetting the WinRM config and rebooting several times. If anyone could help, it would be much appreciated!

I solved a similar WinRM error using Hyper-V Manager console to a remote virtualization host, an access denied error resulting in 2150858770. Dig into the host server's "Windows Remote Management" event log to find the evidence. Then follow the steps in this blog to configure the server: 1,