There is currently no built-in method in Endpoint Protector to directly report how many endpoints are waiting for a license. If the customer is deploying agents via an MDM or another centralized tool, they can use that system to determine how many devices have the agent installed, then compare that number against the total number of licenses to estimate how many endpoints are unlicensed.
Regarding high availability, Endpoint Protector is designed as a single-instance server and does not support clustering or native HA configurations. Given its client-server architecture, this is typically not a limitation in practice: policies remain enforced on endpoints even if the server is temporarily unavailable, and any events generated during downtime are stored locally and automatically forwarded once connectivity to the server is restored.
For disaster recovery, the recommended approach is to rely on infrastructure-level protection. Specifically, regular VM snapshots should be configured on the virtualization platform hosting the Endpoint Protector server. A common best practice is to schedule snapshots every 12 hours and retain them for 7–10 days, ideally in a separate location. In the event of a failure, the server can be restored quickly from these snapshots.