Skip to content

How to Configure Windows Event Forwarding to a Collector Print

  • 0

Applies to: Windows Server 2019, 2022 and 2025.

Windows Event Forwarding sends selected events from source computers to a central collector using WinRM and subscriptions.

Monitoring should collect enough evidence to diagnose trends without overwhelming storage or exposing sensitive logs. Visit managed Windows VPS hosting.

Prerequisites

  • Choose collector and retention.
  • Define source groups.
  • Configure WinRM.
  • Select targeted events.

Procedure

Step 1: Initialize collector

Run on WEC server.

wecutil qc

Step 2: Configure source policy

Set Subscription Manager under Event Forwarding in Group Policy.

Step 3: Create subscription

Choose Source computer initiated and authorize the AD group.

Step 4: Define query

Start with targeted security and system event IDs.

Step 5: Refresh clients

Apply policy and test transport.

gpupdate /force
Test-WSMan collector.corp.example

Step 6: Monitor log

Inspect ForwardedEvents.

Verification

Check subscription status and received events.

wecutil gr 'Server Security Events'
Get-WinEvent -LogName ForwardedEvents -MaxEvents 50

Rollback

Disable the subscription and unlink the source GPO while preserving collected evidence.

Operational notes

Protect collector permissions so sources cannot alter centralized evidence.

Make a subscription deliver usable evidence

Separate the collector setup, source authorization and event query. In a source-initiated design, the source computers learn the collector endpoint from policy and the collector’s subscription authorizes which computer accounts may participate. A working Test-WSMan response verifies part of the transport, not permission to read every requested event channel.

Start with one pilot source and a narrowly selected event set. Use the Event Viewer subscription interface to configure the query and destination log, then generate a harmless event that should match. Inspect both the subscription runtime status and the source forwarding operational log when no event arrives. Security-log collection may require additional channel access; grant only the permissions needed by the supported design.

Size the ForwardedEvents log and onward collection around event volume and retention. A collector can be receiving data correctly while overwriting it too quickly for an investigation. Monitor source health, collection delay and available disk space, not just whether the collector service is running.

Restrict access to centralized logs, because usernames, hostnames and application details can be sensitive. Validate timestamps and the originating computer field in the received event. Keep received evidence when disabling a broken subscription; deleting the log is not a transport repair.

Official references

For a hosted environment with setup and onboarding, explore our managed Windows VPS plans.


Was this answer helpful?

« Back