Windows Error: The WS-Management client cannot process the request

This error typically occurs when you try to establish a remote connection or configure event forwarding using Windows Remote Management (WinRM) between computers that are in a Workgroup rather than a Windows Domain. By default, WinRM security policies restrict remote operations unless the computers trust each other through domain authentication. When the machines are in a Workgroup, Windows blocks the communication because it cannot verify the identity of the event source machine.

To resolve this issue, you must manually configure Windows Remote Management to trust the destination or source computer by modifying the TrustedHosts list or adjusting local security policies.

Step-by-Step Fix

Follow these steps on both the local machine (the client) and the remote machine (the event source) to resolve the error.

Step 1: Open PowerShell as Administrator

1. Press the Windows Key on your keyboard.
2. Type PowerShell into the search bar.
3. Right-click on Windows PowerShell from the search results.
4. Select Run as administrator.

Step 2: Enable and Start the WinRM Service

You need to ensure that the Windows Remote Management service is running and configured to start automatically.

1. In the elevated PowerShell window, type the following command and press Enter:

   Enable-PSRemoting -Force

2. If prompted to make changes or configure the firewall exceptions, type Y and press Enter.

Step 3: Configure the TrustedHosts Setting

Since the machines are not joined to a domain, you must explicitly tell the WS-Management client to trust the remote computer.

• Option A: Trust a specific machine (Recommended for security) Replace REMOTE COMPUTER IP OR NAME with the actual IP address or computer name of the remote event source:

  Set-Item WSMan:\localhost\Client\TrustedHosts -Value "REMOTE COMPUTER IP OR NAME" -Force

• Option B: Trust all machines (Useful for testing environments) If you are working in a safe private network and want to trust any computer, use an asterisk wildcard:

  Set-Item WSMan:\localhost\Client\TrustedHosts -Value "*" -Force

Step 4: Restart the WinRM Service

Apply the new configuration changes by restarting the WinRM service.

1. Run the following command in PowerShell:

   Restart-Service WinRM

Step 5: Verify the TrustedHosts Configuration

To ensure that your settings were saved correctly, check the current TrustedHosts list.

1. Run the following command:

   Get-Item WSMan:\localhost\Client\TrustedHosts

2. Verify that the output displays the IP address, computer name, or the wildcard character you entered in Step 3.

Step 6: Adjust Local Account Token Filter Policy (If needed)

If you are connecting using local administrator accounts rather than domain accounts, Windows User Account Control (UAC) might still block the connection. You can disable this restriction via the registry.

1. Run the following command in PowerShell to modify the registry:

   New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" -Name "LocalAccountTokenFilterPolicy" -Value 1 -PropertyType DWord -Force

2. Close the PowerShell window and restart your computer to apply the registry changes.