Additionally, applications must be cryptographically notarized in order to be installed by the operating system. Cisco AnyConnect 4.8.00175 is the first version that officially supports operation on macOS Catalina and contains no 32-bit code. The Snap version of Firefox is not supported by AnyConnect on Linux. The Cisco AnyConnect Secure Mobility Client is supported on the Mac OS X El Capitan 10.11 operating system. Using the Manual Install Option on Mac OS X if the Java Installer Fails If users WebLaunch from the ASA headend to start AnyConnect on a Mac, and the Java installer fails, a dialog box presents a Manual Install link.
For additional information, refer to the AnyConnect configuration guide.
- Objective The objective of this document is to provide details about the supported operating systems (Windows, Linux, Mac) of the Cisco AnyConnect Secure Mobility Client and their requirements.
- Mar 09, 2021 Cisco AnyConnect and HostScan require updated releases for compatibility with the upcoming macOS Catalina release (10.15). Beginning with macOS Catalina release (10.15), the operating system will no longer support the executing of 32-bit binaries.
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.
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:
%ProgramData%CiscoCisco AnyConnect Secure Mobility ClientProfile
Mac OS X
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.
Topics Map > Networking > Virtual Private Networking (VPN)
This page contains links to download and installation instructions for VPN software for other operating systems.
Technology Services supports the Cisco AnyConnect VPN client on operating systems that are supported by Cisco. Support is provided for Windows 7, and 8 for x86 processors only, and Windows 10 for both x86 and ARM processors; Mac OS X 10.14, 10.15, 11; Some versions of linux; iOS (iPhone and iPad); Android; Kindle; For other mobile devices - check the App store.
However, you may be able to configure your system to connect to the Virtual Private Network (VPN) server if your system offers a compatible VPN client.
To construct your own VPN connection method, you should configure your VPN client as follows:
- VPN server: vpn.illinois.edu
- Username: Your NetID
(or, if you're a guest, your guest ID)
- Password: Your Active Directory password
(or, if you're a guest, your guest password)
- Group: 1_SplitTunnel_Default
(Note: This is the most common choice, but you may want the Tunnel All profile for Library access. See About VPN Profiles for information about the alternatives.)
- Authentication Domain Name: none
- On some Linux variants, you may need to add additional configuration information:
Refuse 40-bit encryption
Require Microsoft Point to Point Encryption [MPPE]
These guidelines are available for reference, but you will need to work out the configuration of your own system and its VPN client.
Cisco Anyconnect Supported Operating Systems Free
Travelers: If you have another Cisco VPN software client installed on your computer already, you may be able to connect to the University VPN server using a guest account and that software.
Cisco Anyconnect Updates
Campus community members can share their knowledge about their devices at Community-developed VPN configurations. (external link) (Log in with your NetID and AD password to read and contribute.)