Issues removing legacy AnyConnect Portals from VPN Client via XML file

VPN
1

Hello,

The company that I work for is decommissioning an AnyConnect VPN Portal and as of result I need to remove the soon-to-be legacy portal from the AnyConnect Agent from all end-user. Initially, I thought if I take the existing XML File config and remove the legacy Portal from the Server List. then upload it back into my AnyConnect Configuration in FMC that would remove the portal name as an aviavable option for users to see, however, it still shows up… Does anyone know how I would go about removing a VPN portal from an AnyConnect Client for all users? Is there something that I am perhaps missing? Do I need to create some form of a XML negate statement?

2

Delete the xml entirely and replace with one that has the portals you want

3

Delete as in delete from my local PC or from the portal itself?

4

From the portal, if you delete it from the local pc the ftd will push it again eventually

5

I imported the new XML file into the portal and removed the old XML from FMC entirely, however, when I quit the AnyConnect client and relaunch the application I noticed that I am using the new XML config as shown under “statistics”. However, I still see the old portal listed as an option to connect to. After browsing to C:\ProgramData\Cisco\Cisco AnyConnect Secure Mobility Client\Profile I noticed that the old XML file is still listed there but if I remove this old XML file THEN the old portal is removed as an available option in my client. However, I want this portal deletion to be automatic and not need forced XML deletion from the PC itself.

6

Im not sure about this but does the new xml profile you imported has the same name as the one currently in prod?

If it doesnt try importing the new one with the same name as the previous one and see if it updates it locally in your pc

7

This looks to have fixed the issue I was having!!! I originally thought by keeping the same name it would use the same name but then add a value after it i.e File to File(1) and would still cause the same issue. But instead, AnyConnect kept the filename the same but just re-wrote over the existing configuration. Thanks again!!!