For additional information, refer to the AnyConnect configuration guide.
Client Download
This article will show how to download and upload the newer AnyConnect 4.x VPN clients to your Cisco ASA Firewall appliance (5500 & 5500-X Series) and configure WebVPN so that the newer AnyConnect VPN client is used and distributed to the remote VPN clients. AnyConnect capability, with If you're using Microsoft cisco anyconnect vpn mac to do and can setup Download the Cisco AnyConnect SSL VPN The AnyConnect VPN client secure VPNs has driven Download the AnyConnect VPN image to the ASA VPN - Network The Cisco ASA does - AnyConnect Client Software) SSL VPN on Cisco AnyConnect client software. APPLICATION DESCRIPTION: AnyConnect for Kindle Fire HD provides reliable and easy-to-deploy encrypted network connectivity from Kindle Fire HDs and new (2012) Kindle Fires to Cisco VPN head-ends (including Cisco ASA 5500 Security Appliances)by delivering persistent corporate access for users on the go. Apr 18, 2018 For a transition period, both the AnyConnect Secure Mobility Client and ASA Software will support both methods. The AnyConnect Secure Mobility Client will automatically detect the correct behavior when talking to a head-end device. On the ASA side, the previous behavior will be disabled by default.
Unlike the ASA, the MX does not support web deploy or web launch, a feature that allows end users to access a web page on the AnyConnect server to download the AnyConnect client. With the MX, there are download links to the client software on the AnyConnect settings page on the dashboard, however, the download links are only available to the Meraki dashboard admin and not the end user. We do not recommend sharing the down link with users as the link expires after every five minutes of loading the AnyConnect settings page.
We recommend downloading the AnyConnect client directly from Cisco.com as there may be an updated version in the Cisco repository. Refer to the doc for the AnyConnect clientrelease notes. We also recommend using either Meraki Systems Manager, an equivalent MDM solution, or Active Directory to seamlessly push the AnyConnect software client to the end user's device.
AnyConnect requires a VPN client to be installed on a client device. The AnyConnect client for Windows, MacOS, and Linux are available on the Client Connection section of the AnyConnect configuration page on the dashboard and can be downloaded by a Meraki dashboard administrator. Please note, the download links on the Meraki dashboard expire after five minutes. The AnyConnect client for mobile devices can be downloaded via the respective mobile stores. You can also download other versions (must be version 4.8 or higher) of the AnyConnect client from Cisco.com if you have an existing AnyConnect license. AnyConnect web deploy is not supported on the MX at this time.
- Installing the AnyConnect client
- You only need the VPN box checked. Once the client has been installed on the device, open the AnyConnect application and specify the hostname or IP address of the MX (AnyConnect server) you need to connect to.
AnyConnect Profiles
An AnyConnect profile is a crucial piece for ensuring easy configuration of the AnyConnect client software, once installed. The MX does not support the use of custom hostnames for certificates (e.g. vpn.xyz.com). The MX only supports use of the Meraki DDNS hostname for auto-enrollment and use on the MX. With the Meraki DDNS hostname (e.g. mx450-xyuhsygsvge.dynamic-m.com) not as simply as a custom hostname, the need for AnyConnect profiles cannot be overemphasized. Profiles can be used to create hostname aliases, thereby masking the Meraki DDNS with a friendly name for the end user.
Cisco AnyConnect client features are enabled in AnyConnect profiles. These profiles can contain configuration settings like server list, backup server list, authentication time out, etc., for client VPN functionality, in addition to other optional client modules like Network Access Manager, ISE posture, customer experience feedback, and web security. It is important to note that at this time, the Meraki MX does not support other optional client modules that require AnyConnect head-end support. For more details, see AnyConnect profiles.
When a profile is created, it needs to get pushed to the end user's device. There are three ways to do this.
1. Through the AnyConnect server (MX): If profiles are configured on the dashboard, the MX will push the configured profile to the user's device after successful authentication.
2. Through an MDM solution: Systems Manager, an equivalent MDM solution, or Active Directory can be used push files to specific destinations on the end user's device. Profiles can also be pushed to the following paths:
Windows
%ProgramData%CiscoCisco AnyConnect Secure Mobility ClientProfile
Mac OS X
/opt/cisco/anyconnect/profile
Linux
/opt/cisco/anyconnect/profile
3. Manually: Profiles can also be preloaded manually to the same paths as listed above.
How to Create a Profile
Profiles can be created using the AnyConnect profile editor. The profile editor can be downloaded from the AnyConnect Settings page on dashboard or on cisco.com. Refer to this link for more details on AnyConnect profiles.
Using the profile editor: The profile editor can be downloaded from the AnyConnect Settings page on dashboard or on Cisco.com. The profile editor only runs on Windows operating systems. The screenshot below shows a configured server ton the Server List Entry option.
When configuration is complete, save the profile. It is recommended to use a unique file name to avoid profile overrides by other AnyConnect servers, then you can upload the file to the profile update section on the AnyConnect settings page.
Please note that only VPN profiles are supported on the MX at this time. This means you cannot push NVM, NAM, or Umbrella profiles via the MX.
- Select enable profiles, upload your xml file, and save your configuration
- After a user successfully authenticates, the configured profile gets pushed to the user's device automatically
- The result of the .xml can be seen below, after successful authentication to the AnyConnect server; this gives users the ease of selecting VPN servers on the AnyConnect client
The Meraki DDNS hostname is not easy to remember, therefore end users are not expected to use it directly. Profiles should be used to make connecting to the AnyConnect server easy for end users.
This post describes how to configure the Cisco ASA and AnyConnect VPN to use the Start-Before Logon (SBL) feature. This allows the user to connect to the VPN before logging onto Windows, thus allowing login scripts and Windows Group Policies to be applied.
Create/Modify the AnyConnect Profile
- Open the AnyConnect VPN Profile Editor
- Open the existing VPN Profile or create a new file
- Under VPN > Preferences (Part 1) select User Start Before Logon
- Ensure the Certificate Store is All
- If creating a new profile navigate to Server List
- Click Add to define a new server
- Define the Display Name (required)
- Define the FQDN or IP Address
- Select the Primary Protocol
- Save the AnyConnect Profile to the local computer, named appropriately e.g. RAS.xml
ASA Configuration
- Copy the AnyConnect Profile RAS.xml to the ASA, with a Profile Name of RASProfile
- Modify the Group Policy in use by the tunnel-group and reference the AnyConnect Profile previously created.
- Modify the Group Policy in use by the tunnel-group and enable SBL vpngina
- Save the ASA configuration
Cisco Anyconnect Windows Client Download
Testing/Verification
- Connect to the VPN tunnel, upon first connection the client should detect that SBL has been enabled and automatically download
- It will automatically install
- Reboot the computer
- After reboot the SBL icon should be visible at the login prompt, at the bottom right of the screen
Anyconnect Client Download
- Press the button and wait to be prompted for authentication
If connected to the VPN successfully you will notice the Disconnect button appear at the bottom right of the login screen. You should now be able to login to the computer as normal with full network connectivity, dependant on an ACL (DACL or VPN Filter) applied to the VPN session.
Troubleshooting
AnyConnect Client Downloads
Make sure the Local AnyConnect VPN Policy permits downloads of client, otherwise you will receive the following error “Automatic profile updates are disabled and the local VPN profile does not match the secure gateway VPN profile.”
If you receive this error run the AnyConnect Profile Editor – VPN Local Policy application
- Open the file C:ProgramDataCiscoCisco AnyConnect Secure Mobility ClientAnyConnectLocalPolicy.XML
- Untick the box Bypass Downloader
- Alternatively edit the same file in notepad an change to <BypassDownloader>false<BypassDownloader>
ASA Identity Certificate
You must ensure that the Windows client trusts the certificate presented to the client as part of the authentication process. If you receive a certificate error when connecting to the VPN normally, you will be unable to connect using SBL.
If you attempt to connect to the VPN using SBL with an invalid certificate on the ASA or the Windows client does not trust the certificate you will receive the following error:- “AnyConnect cannot confirm it is connected to your secure gateway“. It does NOT present the option to Connect Anyway.
This post describes how to configure a CA Trustpoint on the ASA and install the identity certificate and root certificate.
After installing the certificate on the ASA, connect to the VPN and confirm you do not receive any certificate warnings before attempting to connect using SBL.
Machine Certificate
If the tunnel-group is configured to use certificate or aaa + certificates authentication, ensure the Windows computer has a Machine Certificate. Without a machine certificate you will receive the following error: – “No valid certificates available for authentication”.
Certificate Store
If the tunnel-group is configured to use certificate or aaa + certificates authentication, the AnyConnect Profile must be configured to check All Certificate Store (as mentioned in the previous configuration section) for SBL to work.
If you connect to the SBL and the AnyConnect client does not check the Machine Store, you will receive the error “Certificate Validation Failure“.
Cisco Vpn Anyconnect Download