Joining the Conversation
Cato Employee
Hi RPE,
Thanks for the comments and query!
So it is important to note that if you have this checked in your account (using my lab below as reference):
Your SDP clients, when connected to the Cato cloud, always perform configuration checks and pull down the account settings. So even if you make the registry change, it will be overwritten because of the configuration update/pull that the SDP client conducts.
Two things I would suggest:
I hope this helps!
Joining the ConversationHi
Your SDP clients, when connected to the Cato cloud, always perform configuration checks and pull down the account settings. So even if you make the registry change, it will be overwritten because of the configuration update/pull that the SDP client conducts.
yes, that's what I concluded from my various tests
We certainly need an RFE where the 'Connect-On-Boot' feature can be included in the Always-On policies. If you're able to open an RFE request with Support or your CX team here at Cato, that be great!
OK, I will do that, it would be great to have this option "connect at startup" in the policy to be able to handle exceptions.
A workaround I can suggest is to disable 'Connect-On-Boot' in the account settings. Your users can then enable it locally on the client as below:
We prefer users to be logged in as soon as they start their PC.
We have found another workaround for our contractors : they changed the CatoVPN service to start manually instead of automatically.
Thanks for your advices,
Regards,
