Sophos connect client - try to understand

SCX is for IPsec. .Pro is for SSLVPN.

You could use https://community.sophos.com/sophos-xg-firewall/f/recommended-reads/128936/sophos-connect-migration-script-from-utm-sslvpn for migration.

Pro/SCX needs to be published via software deployment/GPO. 

Thanks!

but didn't answer my question.

.scx File is per User. Right (I am not able to connect with different user when using MY .scx file)?

Where can I get the .scx File for user XYZ? It seems it is not available in User Portal for Download by the user itself.

SCX is one File for all users. Authentication in IPsec will be used in Phase2 and is not included in the SCX. 

OK. Thanks for quick response.

I put 2 users in my VPN config. One can connect the other can not (same PC, same Sophos Connect config). Auth error. I am logging in to user portal with userename pw. No problem... One user is synced from AD the other one is local. this is a difference?

I can agree that there is no possibility to login for users that are synced from Microsoft AD.

Added a local user: Login fine.

Added an AD user and synced that user to Sophos: No login possible.

AD user are able to use SSL and user portal. But not Sophos connect.

Sophos XG is 330 with SFOS 18.5.1 MR 1 (actual patch level).

I can agree that there is no possibility to login for users that are synced from Microsoft AD.

Added a local user: Login fine.

Added an AD user and synced that user to Sophos: No login possible.

AD user are able to use SSL and user portal. But not Sophos connect.

Sophos XG is 330 with SFOS 18.5.1 MR 1 (actual patch level).

On Authentication - Services you find a separate part for SSLVPN and for IPSec. Is AD Server selected there?

IPsec does not support groups right now. 

very easy! thanks. solves it.