What is a one sentence summary of your feature request?
Unable to save Endpoint Protector client configuration settings after few recent upgrades
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
In previous versions of Endpoint Protector, we were able to save the client configuration details within the “Client Software” field. However, since the last few upgrades and migrations, this setting no longer saves.
Every time we generate a new client installation package, we now have to manually re-enter the details (Endpoint Protector Server IP, Endpoint Protector Server Port, and Department Code).
Could you please restore this feature back to the Endpoint Protector.
How do you currently solve the challenges you have by not having this feature?
Let me know how to permanently save this configuration for future package deployments?
Upload any supporting images that you think should be considered in this idea.
I tested this on both Windows and macOS with server version 2608. The settings entered on the Client Software page are preserved correctly in the generated Client Package. The fields on that page do revert to default display values once you navigate away, but this is a display behavior only and doesn’t affect what’s packaged.
Thank you for looking into this matter. Some time ago on 5.9.x.x firmware version before it becomes 4 digits (2510.x) version releases. I was able to save and keep the server display value (FQDN) and continue to use it on client package generation process.
