Manually Activating Debugging Logs on Windows

Overview

This article explains how to manually activate debugging logs on Windows for the Endpoint Protector (EPP) Client, for cases when you cannot use the Debug Logging UI option or the SupportTool.

NOTE: Collecting logs remotely from the server console — the Automatic Logging method — is the optimal approach, since it requires no action on the endpoint itself. See Remotely Activating and Collecting Client Logs from the Server Interface for the automatic procedure. If the EPP Client cannot communicate with the EPP Server at all, use the diagnostic collection script instead, since it captures a more complete diagnostic package. Use this manual terminal method only when neither of those applies. For the equivalent manual procedure on macOS, see Manually Generating Logs for Mac Endpoint Protector Agents via Terminal.

Instructions

1. Open the Command Prompt as an administrator.
2. Navigate to the log folder for your client version:
   • EPP Client 2608 and later: C:\ProgramData\Netwrix\EndpointProtector
   • EPP Client versions before 2608: the root of your C: drive
3. Create the following log files in that folder:
   • eppclient.log
   • eppsslsplit.log
4. Restart the EPP process as an admin using services.msc.
5. After completing these steps, reproduce the issue while debugging logs are active. The created files capture the log information.

IMPORTANT: Share the log files with Netwrix Support for further investigation.