Disabling Connect On Boot for external user

Question

Hi,we have activated the "Always On" policy for our users and an "on demand" rule for our external service providers.To ensure that always on is applied for our users, we have checked the "connect on boot" option, but unfortunately this option also applies to external service providers.Can our service providers override this option (registry key?) so that the CATO client doesn't launch at startup?(when I asked the CATO AI, it mentioned a key, but it doesn't seem to work).I can't see specfic configuration in user profile to override this nether.Any idea ?Thanks !Regards

bizzle90 · Answer

&nbsp;
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):&nbsp;

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:

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!
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:&nbsp;

I hope this helps!
&nbsp;

rpe · Answer

HiYour 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 testsWe 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"&nbsp; 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:&nbsp;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,&nbsp;