Somehow I missed getting the EOL notices for SSLVPN and only saw the information this past week when looking at FW 9.710-1 upgrade . I'm having my end-users, log into the present portal (9.709-3), download their .OVPN config, uninstall 2.1 and then install Connect v2 and import their profile. I assume this is "kosher" and no changes are actually needed on the UTM side?
I'm planning on upgrading the FW to the 9.710-1 on two SG units this weekend and I know that the old client will work with the new FW; however, is there a way to stop the old client from working with the new FW ( I was going to give them a week to migrate over to C v2), or even throw a warning about the use of an older client when they connect?
This thread was automatically locked due to age.