Migration of Anyconnect VPN issues

Hi, I am doing migration of Anyconnect VPN from one ASA to another ASA. I need your suggestion. The migration needs to transfer anyconnect vpn configuration and customization. After I reviewed some documents, it looks like that both configuration and customization are not only thing that need to transfer. Any one can give some suggestion what exactly else need to transfer in addition to vpn configuration and customization ? Thank you
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

btanExec ConsultantCommented:
to me it is sort of like cloning into another ASA like that the two ASA are supposed to be paired for HA in active/passive mode. If that is the case, it is definitely more than just Anyconnect files per se. This can include whole ASA configuration, its certificates and private keys into that other ASA with the same IP Address. This is summed up briefly in http://itsecworks.com/2012/11/04/migrate-cisco-asa-configuration-certificates-and-private-keys/

But let focus on the Anyconnect which is concern, and typically it means to transfer the exact AnyConnect XML profile stored in (default) disk0:/webvpn.xml

But probably the neat way is to have configure backup server for Anyconnect instead
You can configure a list of backup servers the client uses in case the user-selected server fails. If the user-selected server fails, the client attempts to connect to the optimal server’s backup at the top of the list. If that fails, the client attempts each remaining server in the Optimal Gateway Selection list, ordered by its selection results.
So t doesn't matter even matter if the client cannot find its config as it can seek backup server as per its system config deployed to it.

Note there is a caveat to all above, the AnyConnect Local Policy
AnyConnectLocalPolicy.xml is an XML file on the client containing security settings. This file is not deployed by the ASA. You must install it manually or deploy it to a user computer using an enterprise software deployment system. If you make changes to an existing local policy file on a user’s system, that system should be rebooted.

If you configure VPN client profiles on the ASA, they must be installed on the client before the client connects to an ASA with BypassDownloader set to true. Because the profile can contain an administrator defined policy, the BypassDownloader true setting is only recommended if you do not rely on the ASA to centrally manage client profiles.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
eemoonAuthor Commented:
Thank you so much for your reply. Your suggestion is excellent. Thank you
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.