Hey Steph,
Thanks for your question!
It sounds like unexpected behavior to me, as long as your client is able to connect to Cato and login successfully for the first time. The SDP user downloads the configuration from the account regarding your SDP client settings, and apply to the client. So if you have Always-On as part of this configuration applied for the user, the user should remain in Always-On.
If you can confirm the client connects to Cato successfully, goes into Always-On mode, and on reboot Always-On is disabled, this is not expected.
There could be a possibility that something on your machine is blocking the connection., I would check here to make sure all prerequisites are matched:
https://support.catonetworks.com/hc/en-us/articles/4411554844817-Installing-the-Cato-Client
I've added our KB here for your review on Always-On:
https://support.catonetworks.com/hc/en-us/articles/4417643184529-Protecting-Users-with-Always-On-Security
I would suggest raising a support ticket with my team.
Please provide:
- Client logs - https://support.catonetworks.com/hc/en-us/articles/9054987541405-Collecting-Client-Logs
- Machine OS (I.E Windows/MacOS).
- Timestamp of testing if possible.
- Confirmation if this issue is easily reproduced.