07-16-2015 07:17 AM - edited 02-21-2020 08:20 PM
Does anyone know of a way that I can put an updated AnyConnect package on the ASA and prevent it from deploying to certain Connection Profiles or Group Policies? I want to deploy AnyConnect 4 by putting it on the ASA and letting it roll out to the clients but I would like to deploy it to some specific groups first before it goes out to everyone. Thanks!
07-16-2015 07:55 AM
I don't believe you can do that with the ASA as the package deployment point. When a remote access client connects, it will detect that there is a newer package on the ASA and attempt to download and install it.
If you pre-deploy (using the msi files or an enterprise endpoint software deployment tool), a client with a newer AnyConnect can access an ASA with only the older packages installed on it.
07-16-2015 09:07 AM
Marvin, thanks for the response. I was pretty sure that was the response I would get. I have been working with the ASA and AnyConnect for over 5 years now and I never found a way to accomplish this. Posting out here was a long shot but it was worth a try. Thanks again!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide