How To Collect Windows Event Logs From Staff Laptops To A Central PC
Summary
This guide helps you troubleshoot and resolve: How To Collect Windows Event Logs From Staff Laptops To A Central PC. Follow the steps below to fix the issue.
Common Causes
This guide explains how to configure Windows Event Forwarding so that event logs from multiple staff laptops are automatically collected on one central PC. This allows your IT support team to review system, application, and security events across your organisation without needing to physically access each device or open remote desktop sessions.
For NDIS and disability support providers, centralised event logging supports compliance with privacy obligations and helps protect participant data. By collecting logs centrally, your organisation can monitor access to systems handling sensitive client information, investigate potential security incidents more efficiently, and maintain an auditable trail of system activity without disrupting frontline staff working across multiple locations.
Quick Fix Steps
- Configure the central collector PC to receive events.
- Configure Windows Firewall on all machines to allow Windows Remote Management.
- Configure WinRM on each source laptop.
- Configure each source laptop to forward events.
- Create an event subscription on the collector PC.
- Verify that events are arriving correctly.
Detailed Instructions
Prerequisites
- All laptops and the central PC must be joined to the same Active Directory domain or workgroup.
- The central PC must run Windows 10/11 Pro, Enterprise, or Education edition.
- Source laptops must run Windows 10/11 Pro, Enterprise, or Education edition to use Local Group Policy Editor.
- You must have local administrator rights on every machine.
- All devices must have synchronised time and be able to communicate over the network.
Step 1: Enable Windows Event Collector on the central PC
- Log on to the central PC as an administrator.
- Press
Windows key + R, typeservices.msc, and press Enter. - Locate the Windows Event Collector service in the list.
- Right-click Windows Event Collector and select Properties.
- Set Startup type to Automatic.
- Click Start if the service is not running, then click OK.
Step 2: Configure Windows Firewall on all machines
- On the central PC and each source laptop, press
Windows key + R, typewf.msc, and press Enter to open Windows Defender Firewall with Advanced Security. - In the left pane, click Inbound Rules.
- In the right pane, click New Rule.
- Select Predefined, then choose Windows Remote Management from the dropdown list.
- Click Next.
- Ensure Windows Remote Management (HTTP-In) is selected.
- Click Next, then select Allow the connection.
- Click Next, ensure all profiles (Domain, Private, and Public) are selected, then click Next.
- Enter a name such as Windows Remote Management (HTTP-In) - Event Forwarding and click Finish.
Step 3: Configure WinRM on each source laptop
- On each staff laptop that will forward logs, open Command Prompt or PowerShell as administrator.
- Run the following command to configure the WinRM service and create a listener:
winrm quickconfig - Type Y when prompted to confirm changes.
- Verify the listener is configured by entering:
winrm e winrm/config/listener - If the laptops are in a workgroup (non-domain environment), add the central PC to the TrustedHosts list on each source laptop by running:
Replacewinrm set winrm/config/client @{TrustedHosts="central-pc-name"}central-pc-namewith the hostname or IP address of your central collection PC.
Step 4: Configure source computers using Local Group Policy Editor
- On each staff laptop that will forward logs, press
Windows key + R, typegpedit.msc, and press Enter. - Navigate to Computer Configuration > Administrative Templates > Windows Components > Event Forwarding.
- Double-click Configure target subscription manager.
- Select Enabled.
- Under Options, click Show next to Server names.
- Enter the subscription target in the format:
ReplaceServer=central-pc-name;Port=5985central-pc-namewith the hostname or IP address of your central collection PC. - Click OK to close the dialog, then click OK again to apply the policy.
- Open Command Prompt as administrator and run:
gpupdate /force
Step 5: Configure WinRM on the central PC
- On the central PC, open Command Prompt or PowerShell as administrator.
- Run the following command to configure the WinRM service:
winrm quickconfig - Type Y when prompted to confirm changes.
- Verify the service is running by entering:
winrm e winrm/config/listener
Step 6: Create the event subscription
- On the central PC, press
Windows key + R, typeeventvwr.msc, and press Enter to open Event Viewer. - In the console tree, expand Windows Logs.
- Right-click Subscriptions and select Create Subscription.
- Enter a name and description for the subscription.
- Click Select Computers, then click Add Domain Computers or manually enter the hostnames of the staff laptops.
- Click Select Events to choose which logs to collect. Select System and Application logs. Only select Security if your organisation has a documented security auditing requirement.
- Choose Normal or Minimise bandwidth delivery optimisation based on your network.
- Click Advanced to configure the user account used for collection.
Subscription authentication for domain and workgroup environments
- Domain environment: Use a domain user account that has local administrator rights on each source laptop. This account is specified in the Advanced settings of the subscription.
- Workgroup environment: Use a local administrator account that exists on both the central PC and each source laptop, with the same username and password. Specify this account in the Advanced settings of the subscription.
- Click OK to create the subscription.
- When prompted, confirm that you want to activate the subscription.
Step 7: Verify event collection
- In Event Viewer on the central PC, expand Windows Logs and click Forwarded Events.
- Confirm that events from the staff laptops are appearing in the log.
- If no events appear, check the subscription status by right-clicking the subscription and selecting Runtime Status.
Troubleshooting
Subscription shows an error status
- Ensure the Windows Event Collector service is running on the central PC.
- Verify that WinRM is configured and running on both the collector and source laptops.
- Check that the source laptops can reach the central PC on port 5985 using
Test-NetConnection central-pc-name -Port 5985in PowerShell. - Run
gpupdate /forceon the source laptops and restart the Windows Event Log service.
No events appearing in Forwarded Events
- Confirm the subscription is active and not paused.
- Check that the correct event logs were selected during subscription creation.
- Review the subscription Runtime Status for specific error codes.
- Ensure the central PC and source laptops have synchronised time settings.
Access denied errors
- Verify that the account used for the subscription has administrative rights on the source laptops.
- For non-domain environments, add the central PC to the TrustedHosts list on each source laptop.
- Ensure Windows Firewall allows Windows Remote Management (HTTP-In) on all machines.
If you continue to experience issues with event forwarding, please Open a Ticket for assistance.
Still Having Issues?
💻 Open a Ticket