Starting from version 5.0 Cisco has renamed their product to Cisco Secure Client and also the path to the GUI. It is now named csc_ui.exe instead of vpnui.exe.
Can you please add csc_ui.exe to the function "Kill vpnui.exe before open"?
Hello,
Thank you for the information, I have opened a ticket so we can add this.
Regards,
Hubert Mireault
Hello,
To confirm with you, is it only the "Kill vpnui.exe before open" option that doesn't work for you, or the whole integration due to the different executable name? From what I can see of our code, we don't handle csc_ui.exe at all and only refer to vpnui.exe, so I'm surprised it works for you. I would have expected us to need to change more than just how this one option is handled.
Regards,
Hubert Mireault
Hi,
"Kill vpnui.exe before open" does not work since the file name no longer matches. The rest works provided that you end the gui process manually before connecting. The cli exe file is still named vpncli.exe. The paths are different but I guess it just calls taskkill /IM vpnui.exe /F or something similar.
Thank you for the clarification, I've added this information to the ticket. I asked since we don't have the environment to test Cisco Anyconnect internally, and I want to make sure we make the changes in a way that works for you.
Regards,
Hubert Mireault
Hello,
We've changed the option to be more inclusive, and we now attempt to close both vpnui.exe and the csc_ui.exe
These changes should take effect in the 2022.3 version. We hope this will fix the issue for you.
Regards,
Jafran Majeau
I'm sure it will fix the issue! Many thanks!