Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Suggested Answer
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 39 subscribers
  • Views 1016 views
  • Users 0 members are here
Options
Suggested

Sophos Connect updates

Gib GoDesk

Hello, everyone.

I would like to hear from you about your experience. Thank you in advance.

Sophos version: 19.5.4

I have two questions.

First (1) - Our company is going through a name (identity) transition. We are no longer called XYZ but ABC.

Our provisioning files for RA IPSec connections with MFA are pointing to the XYZ domain. With this name change, we now need to update the domain to ABC.

Can I change the imported files for all users or will I need to generate a new provisioning file with the ABC domain and import it again?

Second (2) - With the new Sophos 20 MR1 update, the old Sophos Connect no longer works. I need to update it.

How are you doing this update? What would be the best practice?

Is it possible to send an update directly to the client? A command like: scvpn /autoupdate

Or signal the server side for the client to perform an update.

I ask to know what tools I have, what I can do better, or ideas to better adapt to my environment.

It would be interesting if someone wrote an article about this, like the recommended readings.

Thank you to everyone who read this far.



Edited TAGs
[edited by: emmosophos at 11:29 PM (GMT -7) on 7 Jun 2024]
Parents
  • 0

    Generally speaking: Sophos Connect still should work after update to V20.0 MR1. This needs more debugging to find the root cause. 

    About the first issue: Your Provisioning file has a DNS to the wrong domain? You could change the DNS or simply reuse the DNS as it is only a pointer to the Firewall. 

    __________________________________________________________________________________________________________________

  • 0 in reply to LuCar Toni

    Thanks for your time, Toni.

    Ok, I'll do a test to see if there will be an impact if I update to 20 MR1. Updating the SCVPN wouldn't be easy but you already reassured me about it.

    Regarding the first case, it is not an error in the domain. The company is changing its name.

    We will have to change the DNS name, but the provisioning points to the company's old domain name and I wanted to know if there was a way to update the configurations without the need for a new deployment.

    It also has the connection display name which is currently VPN_ABC. It would be interesting to add the new name VPN_XYZ.

Reply
  • 0 in reply to LuCar Toni

    Thanks for your time, Toni.

    Ok, I'll do a test to see if there will be an impact if I update to 20 MR1. Updating the SCVPN wouldn't be easy but you already reassured me about it.

    Regarding the first case, it is not an error in the domain. The company is changing its name.

    We will have to change the DNS name, but the provisioning points to the company's old domain name and I wanted to know if there was a way to update the configurations without the need for a new deployment.

    It also has the connection display name which is currently VPN_ABC. It would be interesting to add the new name VPN_XYZ.

Children
No Data
Unfiltered HTML