- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2024 01:43 AM
Good day team!
I want to customize pre-deploy and web deploy Anyconnect installation to add company logo and other resources.
guides are
Cisco AnyConnect Secure Mobility Client Administrator Guide, Release 4.8 - Customize and Localize the AnyConnect Client and Installer [Cisco Secure Client (including AnyConnect)] - Cisco
Customize Windows Installation of Cisco Secure Client
Are these links is what I need?
and questions are, if you don't mind:
1.How customize .pkg files on ASA?
2.Local pre-deploy CORE VPN, how replace resourses in .msi files?
Thanks a lot for help and reply.
Solved! Go to Solution.
- Labels:
-
AnyConnect
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2024 06:31 AM
Hi,
Well, look out for tools that might help. Easiest way though is to leave the PKG file as is when you upload it to FTD and have your custom MSI file pre-deployed on the end systems. Since end systems will already have the client installed, the on-customized PKG file from FTD will not be pushed down.
Best,
Cristian.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2024 03:13 AM
Hi,
You'll need to use an external tool (Orca, Wise, Installshield, whatever else) to build your custom MSI package and afterwards perform mass deployment (either manual installation on each endpoint, or automatic installation using another tool that support this; today, most commonly MDM/EDM tools are being used).
Best,
Cristian.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2024 05:25 AM - edited 10-31-2024 05:25 AM
Thank you for reply!
But how customize .pkg on ASA?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2024 06:31 AM
Hi,
Well, look out for tools that might help. Easiest way though is to leave the PKG file as is when you upload it to FTD and have your custom MSI file pre-deployed on the end systems. Since end systems will already have the client installed, the on-customized PKG file from FTD will not be pushed down.
Best,
Cristian.
