Home › Knowledgebase › KB-1674

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.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

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.

Be cautious when selecting which event logs to forward. Forwarding Security event logs can expose sensitive authentication and access data, including login attempts and account activity. Unless your organisation has an explicit security auditing requirement, limit collection to System and Application logs only. In a disability support environment, minimising the amount of potentially sensitive data moved across the network helps reduce privacy risk.

Quick Fix Steps

  1. Configure the central collector PC to receive events.
  2. Configure Windows Firewall on all machines to allow Windows Remote Management.
  3. Configure WinRM on each source laptop.
  4. Configure each source laptop to forward events.
  5. Create an event subscription on the collector PC.
  6. Verify that events are arriving correctly.

Detailed Instructions

Prerequisites

Step 1: Enable Windows Event Collector on the central PC

  1. Log on to the central PC as an administrator.
  2. Press Windows key + R, type services.msc, and press Enter.
  3. Locate the Windows Event Collector service in the list.
  4. Right-click Windows Event Collector and select Properties.
  5. Set Startup type to Automatic.
  6. Click Start if the service is not running, then click OK.
The Windows Event Collector service must be running before you can create subscriptions.

Step 2: Configure Windows Firewall on all machines

  1. On the central PC and each source laptop, press Windows key + R, type wf.msc, and press Enter to open Windows Defender Firewall with Advanced Security.
  2. In the left pane, click Inbound Rules.
  3. In the right pane, click New Rule.
  4. Select Predefined, then choose Windows Remote Management from the dropdown list.
  5. Click Next.
  6. Ensure Windows Remote Management (HTTP-In) is selected.
  7. Click Next, then select Allow the connection.
  8. Click Next, ensure all profiles (Domain, Private, and Public) are selected, then click Next.
  9. Enter a name such as Windows Remote Management (HTTP-In) - Event Forwarding and click Finish.

Step 3: Configure WinRM on each source laptop

  1. On each staff laptop that will forward logs, open Command Prompt or PowerShell as administrator.
  2. Run the following command to configure the WinRM service and create a listener:
    winrm quickconfig
  3. Type Y when prompted to confirm changes.
  4. Verify the listener is configured by entering:
    winrm e winrm/config/listener
  5. If the laptops are in a workgroup (non-domain environment), add the central PC to the TrustedHosts list on each source laptop by running:
    winrm set winrm/config/client @{TrustedHosts="central-pc-name"}
    Replace central-pc-name with the hostname or IP address of your central collection PC.

Step 4: Configure source computers using Local Group Policy Editor

  1. On each staff laptop that will forward logs, press Windows key + R, type gpedit.msc, and press Enter.
  2. Navigate to Computer Configuration > Administrative Templates > Windows Components > Event Forwarding.
  3. Double-click Configure target subscription manager.
  4. Select Enabled.
  5. Under Options, click Show next to Server names.
  6. Enter the subscription target in the format:
    Server=central-pc-name;Port=5985
    Replace central-pc-name with the hostname or IP address of your central collection PC.
  7. Click OK to close the dialog, then click OK again to apply the policy.
  8. Open Command Prompt as administrator and run:
    gpupdate /force
If your laptops are not domain-joined, ensure the central PC is added to the TrustedHosts list on each source machine, or WinRM communication will fail.

Step 5: Configure WinRM on the central PC

  1. On the central PC, open Command Prompt or PowerShell as administrator.
  2. Run the following command to configure the WinRM service:
    winrm quickconfig
  3. Type Y when prompted to confirm changes.
  4. Verify the service is running by entering:
    winrm e winrm/config/listener

Step 6: Create the event subscription

  1. On the central PC, press Windows key + R, type eventvwr.msc, and press Enter to open Event Viewer.
  2. In the console tree, expand Windows Logs.
  3. Right-click Subscriptions and select Create Subscription.
  4. Enter a name and description for the subscription.
  5. Click Select Computers, then click Add Domain Computers or manually enter the hostnames of the staff laptops.
  6. 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.
  7. Choose Normal or Minimise bandwidth delivery optimisation based on your network.
  8. Click Advanced to configure the user account used for collection.

Subscription authentication for domain and workgroup environments

  1. Click OK to create the subscription.
  2. When prompted, confirm that you want to activate the subscription.
Use Normal delivery for reliable event forwarding over LAN. Use Minimise bandwidth if laptops connect over slower or metered connections.

Step 7: Verify event collection

  1. In Event Viewer on the central PC, expand Windows Logs and click Forwarded Events.
  2. Confirm that events from the staff laptops are appearing in the log.
  3. If no events appear, check the subscription status by right-clicking the subscription and selecting Runtime Status.

Troubleshooting

Subscription shows an error status

No events appearing in Forwarded Events

Access denied errors

If you continue to experience issues with event forwarding, please Open a Ticket for assistance.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket