Distinguish Online Devices from Fully Connected Clients Planned

Description:

During a recent deployment, we encountered a situation where Timus Connect was stuck on “Applying security policies” and repeatedly attempting to connect. However, the device appeared online and connected in Timus Manager, making it impossible to identify the issue centrally without inspecting the endpoint directly.

We resolved the issue by allowing outbound ports specifically to the Timus Gateway IP.

Requested Enhancement:

Please provide more granular connection status visibility in Timus Manager so administrators can distinguish between:

• A device that is online and reporting to Manager.
• A device that has successfully established its Timus tunnel.
• A device that has successfully completed security policy application.
• A device experiencing connection failures or stuck during connection establishment.

Ideally, these statuses would be visible centrally and accessible through reporting or an API, allowing MSPs to validate deployments at scale.

Business Impact:

For MSPs deploying Timus Connect across hundreds of endpoints, an online status that doesn't reflect a fully working connection can create a false sense of security. Improved visibility would help administrators identify failed deployments, troubleshoot connectivity issues faster, and verify that endpoints are functioning as expected without manually inspecting each device.

Use Case:

Deploying Timus Connect to 130+ endpoints and needing to confirm centrally that every device has successfully connected and applied its security policies.