Skip to main content

User Interface Performance Issues

Symptom​

The Endpoint Protector Console/User Interface is experiencing issues and other performance concerns.

Causes​

  1. Large number of logs or file shadows on the Endpoint Protector server.
  2. Backend services being affected or disrupted.
  3. Insufficient disk space on the server.
  4. Insufficient CPU cores and RAM allocated to the server, or a server that no longer meets the minimum sizing requirements.
  5. Endpoint Protector Server upgrades or audit log backups running. Performance can decrease during upgrades or backup operations.
  6. Running older Endpoint Protector Server and Client versions.
  7. Third-party antivirus, EDR, or HIPS software scanning EPP Client or Server processes and files. Security software that isn't configured with the required exclusions can compete with Endpoint Protector for CPU and RAM, and cause timeouts.

Resolutions​

  1. Large Number of Logs or File Shadows

    1. Check Appliance > Server Information for the number of logs and file shadows.
    2. Delete older or unnecessary logs or archive them using the Audit Log Backup functionality.
    3. Externalize logs using the File Shadow Repository or SIEM Integration functionality.

  2. Backend Services Being Affected

    1. Reboot the Endpoint Protector server from Appliance Operations (Appliance > Server Maintenance) or from your hosting platform (VM, AWS, Azure, GCP).
    2. If the server returns HTTP 500 errors that only clear after a full reboot and recur every few days, this is often a sizing issue rather than a one-off glitch. See Recurring HTTP 500 Errors Resolved Only by a Full Reboot.

  3. Disk Space Issues

    1. Review Server Information for disk space details.
    2. Remove unnecessary files and raise a support ticket for investigation if necessary.
    3. If hosted on your end (VM, AWS, Azure, GCP), allocate extra disk space and contact support for disk resizing.

  4. Resource Issues

    1. Compare your current CPU, RAM, and disk allocation against Server Requirements — an undersized appliance is a common root cause of both general UI slowness and recurring server errors.
    2. If hosted on your end (VM, AWS, Azure, GCP), add extra CPU cores and RAM.
    3. Contact support via a support ticket to allocate additional resources on the Endpoint Protector server.

  5. Endpoint Protector Server Upgrades or Audit Log Backups Running

    1. Expect temporary UI performance decrease during and shortly after these processes.
    2. During the first 24 hours after a migration or major upgrade, temporary CPU/RAM/disk peaks are normal while background cron jobs and database schema alignment tasks complete. See Post-Migration Stability in the Migration Best Practices for details.

  6. Running Older Endpoint Protector Server and Client Versions

    1. Always use the latest Endpoint Protector server and client versions available as a best practice. See Netwrix Endpoint Protector Server-Side Support Policy and Netwrix Endpoint Protector Agent Support Policy for supported version tracks, and the EPP Server Migration & Upgrade Guide if you're on a version older than 5.9.4.2.

  7. Third-Party Security Software Interference

    1. Configure the required file, process, and registry exclusions for your antivirus, EDR, or HIPS solution. See Security Exclusions for the complete list for Windows, macOS, and Linux.
    2. Reboot the affected endpoint after applying exclusions before escalating further.