What is a one sentence summary of your feature request?
Enhanced Client Upgrade Failure Diagnostics and Remote Log Collection
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
Implement enhancements to improve the client upgrade troubleshooting process in Netwrix Endpoint Protector:
-
Remote Diagnostic Log Collection for Failed Client Upgrades by adding a “Collect Diagnostic Logs” capability within the Client Upgrade Jobs section that allows administrators to remotely retrieve logs from endpoints that fail to upgrade, either individually or in bulk. The collected logs should be centrally stored (similar to existing EPP client logs), made available for download, enabling faster and more consistent analysis.
-
Enhance the Client Upgrade Job details with specific failure codes or stage indicators that clearly identify where the upgrade process failed. Example indicators could be:
- “0” – Failed to download the client installer from the console
- “1” – Failed to install the new client
- Additional codes for other installation, validation, or communication failures
These indicators would enable administrators to immediately understand the root cause without manually accessing each endpoint.
From an operational perspective, even though the recommended approach is to begin upgrades with a small group of clients, these improvements would still enable administrators to handle unexpected upgrade failures more efficiently, reduce the time spent repeatedly accessing individual endpoints, and minimize disruption during broader client upgrade cycles.
How do you currently solve the challenges you have by not having this feature?
At present, administrators must manually connect to each endpoint, either physically or through remote access, to retrieve the client upgrade log. However, in many cases our customers face situations where the log contains no information at all, providing no value for troubleshooting. This manual approach is time-consuming and operationally challenging, especially when endpoints are located across multiple sites.