Forum Discussion

Linear_z's avatar
Linear_z
Copper Contributor
May 29, 2020

ICM fails on call back to local PC

Hi there.   I've an odd issue with Powershell.  I discovered that I cannot ICM from the domain controller to a remote workstation - and I also cannot ICM from the actual workstation PC console back...
ICM
Invoke-Command
powershell
Linear_z's avatar
Linear_z
Copper Contributor
May 31, 2020

Linear_z 

 

From what I can deduce, it was GPO. 

 

The SBS2k8 had a policy object "Allow automatic configuration of listeners" which is not present in WS2019 and caused this to occur once the old server came offline and the forest functional level was elevated:

 

PS C:\WINDOWS\system32> winrm enumerate winrm/config/listener
Listener [Source="GPO"]
Address = *
Transport = HTTP
Port = 5985
Hostname
Enabled = true
URLPrefix = wsman
CertificateThumbprint
ListeningOn = null

 

So when the IP filter for the client listeners was set back to " * " and GPO refreshed, Invoke-Command works from the DC as expected. 👍 

 

On a side note: the clients produce a new error now when ICM'ing to themselves - which I had tried initially as a test measure since the DC would actually do that successfully.  This really is immaterial though because there is no reason to ever do this, but now it says: "The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available." 

 

Maybe a puzzle to work on when there's nothing else to do - but for now it's of no concern.  🤷‍:male_sign:

Resources