Troubleshooting Common Issues After EPP Server Migration
Overview
After migrating the Netwrix Endpoint Protector (EPP) Server from a legacy 5.x version to the current image-based platform (2510 with patch 2604), you may encounter a number of known, documented issues. This article summarizes the most common ones by symptom, grouped by whether they affect the EPP Server or the EPP Client, so you can quickly identify which applies to your situation.
For the full symptom, cause, and resolution details for each issue, see Migration Troubleshooting in the EPP Server Migration & Upgrade Guide.
EPP Server Issues
- High CPU usage after a mass client reinstall or reconnect — expected, temporary, and self-resolving. See High CPU Usage After Mass Client Reconnect.
- Backup restore fails or is rejected by the server — usually means the backup wasn't created on exactly version 5.9.4.2. See Backup Restore Fails or Is Rejected by the Server.
- Network/IP settings won't save on 2510 — a known bug requiring both DNS fields to be filled. See Network Settings Won't Save on 2510.
- Backup file exceeds the 200 MB import limit — See Backup File Exceeds 200 MB Import Limit.
- SIEM not receiving events after migration — See SIEM Integration Not Receiving Events.
- Audit Log Backup job stuck or needs to be reset — See Cleaning Up and Recreating an Audit Configuration.
- Predefined HIPAA dictionaries stop working after a server hostname/IP change — See Predefined HIPAA Dictionaries Stop Working After Migration.
- Recurring HTTP 500 errors resolved only by a full reboot — typically an undersized-server issue, not a one-time import failure. See Recurring HTTP 500 Errors Resolved Only by a Full Reboot.
- SSO login fails after migration when the new server uses an IP address instead of an FQDN — reviewing the SSO configuration after restore is mandatory in this case. See SSO Login Fails After Migration When the Server Uses an IP Address Instead of an FQDN.
EPP Client Issues
- Enforced Encryption (EE) clients can't connect after migration — typically caused by an IP/FQDN change. See EE Clients Can't Connect After Migration.
- Endpoints not checking in after migration — See Endpoints Not Checking In After Migration.
- Endpoints not upgrading via the EPP Server Client Upgrade tool — See Endpoints Not Upgrading via EPP Server Client Upgrade tool.
- Policies update fails on a Windows 11 EPP Client with a code signature verification error — See Policies Update Fails on Windows 11 EPP Client (Code Signature Verification Error).
tip
If your issue isn't covered here or in the full troubleshooting guide, also check the Migration FAQ for additional known issues and answers, or the EPP Server Migration & Upgrade Guide for the complete migration procedure.