This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Client Authentication Agent Not Works in PCs With Non Admin Users

Hi,

I am using Sophos XG 125 Firewall and tried to install the CAA in my user's computers. Initially, it is found to be working in all the PCs. The issue is observed after restarting the PCs on which the users are login in with non administrator accounts. In such PCs, the CAA will not work once the PC is restarted. I have to reinstall it again to use it. But after another restart, it will again stop working. I have already raised one support case with the Sophos team and got an interesting reply that "Its your domain issue that your domain does not allows the app to start automatically after restart". This is a completely wrong statement as I found a lot of other users also querying about the same thing in the Sophos community and even in other blogs as well. But there was no proper solution found yet for this issue. While installing the CAA in a user pc with non admin rights, it will ask to enter the administrator username and password. The app will get installed only after entering these details. The same way we are installing all the applications in the PC and all of them works well after restarting except CAA. So, its a simple logic that the issue is not at the customer side but with the CAA application only. Hope this time we will get a solution for this long pending issue reported by multiple users.

 

Thanks

Smithesh



This thread was automatically locked due to age.
Parents Reply Children
  • Finally, Sophos provided me with a so-called solution and it is very simple. Make the restricted user an administrator at the time of installation. Then perform the installation process so that the installation files will go to the concerned user folder only. Once the CAA is installed, change the user back to the restricted user. Then the CAA will work even after the restart. Even though this solution doesn't make any sense I am forced to follow it as Sophos have no other options available with them for this issue.