jmachado81
asked on
How to fully Enable Remote PS on a server OS
I have enabled Remote PS but each time i reboot my system it says this error.
The WinRM service is not listening for WS-Management requests.
User Action
If you did not intentionally stop the service, use the following command to see the WinRM configuration:
winrm enumerate winrm/config/listener
#Enable Remote PS Access
Enable-PSRemoting –forceHere is my config:
PS C:\Users\Administrator> winrm e winrm/config/listener
Listener
Address = *
Transport = HTTP
Port = 5985
Hostname
Enabled = true
URLPrefix = wsman
CertificateThumbprint
ListeningOn = 127.0.0.1, 172.23.20.23, ::1
PS C:\Users\Administrator> 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 = *.domain.com
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 = false
CbtHardeningLevel = Relaxed
DefaultPorts
HTTP = 5985
HTTPS = 5986
IPv4Filter = *
IPv6Filter = *
EnableCompatibilityHttpListener = false
EnableCompatibilityHttpsListener = false
CertificateThumbprint
AllowRemoteAccess = true
Winrs
AllowRemoteShellAccess = true
IdleTimeout = 7200000
MaxConcurrentUsers = 2147483647
MaxShellRunTime = 2147483647
MaxProcessesPerShell = 2147483647
MaxMemoryPerShellMB = 2147483647
MaxShellsPerUser = 2147483647
PS C:\Users\Administrator>What powershell command do i need to execute to clear this error?
ASKER
Honestly haven't tested PS remoting but was more trying to clear the warnings in my system log. I've found this warning appears after every reboot...not just once in awhile. If this is expected behavior thats unfortunate but acceptable; however i'd really prefer to have no warning in my log or at the very least an explanation as to why it is even there.
I was hoping maybe there was a command/config missing to clear it....
The Windows Remote Management service is set to automatic and running with 1st & 2nd failures to restart service.
I was hoping maybe there was a command/config missing to clear it....
The Windows Remote Management service is set to automatic and running with 1st & 2nd failures to restart service.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
WinRM is set to MANUAL in Services.MSC off the gate. It won't be running.
It needs to be started in order to handle those incoming requests.
Enabling PS Remoting does not do that.
It needs to be started in order to handle those incoming requests.
Enabling PS Remoting does not do that.
ASKER
You are correct footech. After some additional testing it seems out of the box (for server 2022) this warning appears before any commands are executed. They also appear during the shutdown process. Since they are native before any changes to the OS and only at shutdown i'll ignore as you suggest.
Philip, The WinRM is default to automatic and is already running.
Philip, The WinRM is default to automatic and is already running.
It's normal to see this event from time to time. Typically you'll see an event shortly after that says it is listening.
What is the status and startup type of the Windows Remote Management service? Also, what are the recovery options set to?