AnyConnect DropDown caching issue after profile replacement

[amir.glibic]

Hi,

we currently face an issue again regarding AnyConnect and the profile handling.

We have an old, manual connection profile (Profile A) that will be replaced by a new Always-On, SSO (machine-certificate) profile (Profile B).

As soon as we replace the profile in the profile folder and reboot the client, AnyConnect starts and causes an error.

The error is caused, because despite that Profile A is not present any more, it appears as the default in the drop-down menu.

So AC tries to do an automatic connection (Always-On), but fails because the wrong profile (A) is "selected".

A user then needs to switch the drop-down list to profile B manually. The connection is then established properly and profile A disappears from the list.

To me it seems to be some kind of caching issue of the dropdown list itself. The old profile in the folder is definitely deleted. We have faced this already several times, each time we need to replace VPN profiles for users via SCCM (departments are renamed, settings are changed, etc.).

Is there any trick to resolve this issue? 

Thanks & BR

[Mohammed al Baqari]

Hi, what is the path you deleted the profile from?

**** please remember to rate useful posts

[Marvin Rhoads · Accepted solution]

The connection profiles are stored in C:\ProgramData\Cisco\Cisco AnyConnect Secure Mobility Client\Profile.

However there are also:

1. a preferences_global.xml file in the parent directory.

2. a user preferences file in C:\Users\username\AppData\Local\Cisco\Cisco AnyConnect VPN Client\preferences.xml

Have you taken care to remove those when putting in the new profile?

[amir.glibic]

Thanks, after removing these files everything works fine after replacing the profile - no errors at all

[Marvin Rhoads]

You're welcome. Those files are a bit tricky to completely enumerate the first time around. Only because I've done it several times do I recall where they all reside.

Thanks for rating.