Events are not forwarded if the collector is running Windows Server

Applies to: Windows Server, version 1903Windows Server 2019, all versionsWindows Server 2016


You configure a Windows Server, version 1903-based, Windows Server 2019-based or Windows Server 2016-based computer as an event collector. You also configure a source-initiated subscription (and related Group Policy Objects) for event forwarding. However, the events are not forwarded and the event source computers log event messages that resemble the following:

Log Name: Microsoft-Windows-Forwarding/Operational
Event ID: 105
Task Category: None
The forwarder is having a problem communicating with subscription manager at address Error code is 2150859027 and Error Message is The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol. </f:Message></f:WSManFault>.


This behavior is caused by the permissions that are configured for the following URLs :

  • http://+:5985/wsman/
  • http://+:5986/wsman/

On the event collector computer, both the Windows Event Collector service (WecSvc) and the Windows Remote Management service (WinRM) use these URLs. However, the default access control lists (ACLs) for these URLs allow access for only the svchost process that runs WinRM.

In the default configuration of Windows Server 2016, a single svchost process runs both WinRM and WecSvc. Because the process has access, both services function correctly. However, if you change the configuration so that the services run on separate host processes, WecSvc no longer has access and event forwarding no longer functions.

The services function differently in Windows Server 2019. If a Windows Server 2019 computer has more than 3.5 GB of RAM, separate svchost processes run WinRM and WecSvc. Because of this change, event forwarding may not function correctly in the default configuration. For more information about the service changes, see Changes to Service Host grouping in Windows 10.


To view the URL permissions, open an elevated Command Prompt window and run the following command:

netsh http show urlacl

To fix the URL permissions, use the elevated Command Prompt window and run the following commands:

netsh http delete urlacl url=http://+:5985/wsman/ netsh http add urlacl url=http://+:5985/wsman/ sddl=D:(A;;GX;;;S-1-5-80-569256582-2953403351-2909559716-1301513147-412116970)(A;;GX;;;S-1-5-80-4059739203-877974739-1245631912-527174227-2996563517)netsh http delete urlacl url=https://+:5986/wsman/netsh http add urlacl url=https://+:5986/wsman/ sddl=D:(A;;GX;;;S-1-5-80-569256582-2953403351-2909559716-1301513147-412116970)(A;;GX;;;S-1-5-80-4059739203-877974739-1245631912-527174227-2996563517)

More information

Default URL permissions that are used by Windows Server 2019 and Windows Server 2016:

Reserved URL : http://+:5985/wsman/‎User: NT SERVICE\WinRM‎Listen: Yes‎Delegate: No‎SDDL: D:(A;;GX;;;S-1-5-80-569256582-2953403351-2909559716-1301513147-412116970)Reserved URL : https://+:5986/wsman/User: NT SERVICE\WinRMListen: YesDelegate: NoSDDL: D:(A;;GX;;;S-1-5-80-569256582-2953403351-2909559716-1301513147-412116970)

Default URL permissions that are used by Windows Server 2012 R2:

Reserved URL : http://+:5985/wsman/‎User: NT SERVICE\WinRM‎Listen: Yes‎Delegate: No‎User: NT SERVICE\Wecsvc‎Listen: Yes‎Delegate: No‎SDDL: D:(A;;GX;;;S-1-5-80-569256582-2953403351-2909559716-1301513147-412116970)(A;;GX;;;S-1-5-80-4059739203-877974739-1245631912-527174227-2996563517)Reserved URL : https://+:5986/wsman/User: NT SERVICE\WinRMListen: YesDelegate: NoUser: NT SERVICE\WecsvcListen: YesDelegate: NoSDDL: D:(A;;GX;;;S-1-5-80-569256582-2953403351-2909559716-1301513147-412116970)(A;;GX;;;S-1-5-80-4059739203-877974739-1245631912-527174227-2996563517)