4. Expand the Latest Releases folder and click the latest release, if it is not already selected.
5. Download AnyConnect Packages using one of these methods:
–To download a single package, find the package you want to download and click Download.
–To download multiple packages, click Add to cart in the package row and then click Download Cart at the top of the Download Software page.
6. Read and accept the Cisco license agreement when prompted.
7. Select a local directory in which to save the downloads and click Save.
8. See “Configuring the ASA to Download AnyConnect” in Chapter 2, Deploying the AnyConnect Secure Mobility Client in the Cisco AnyConnect Secure Mobility Client Administrator Guide, Release 3.1 to install the packages onto an ASA or to deploy AnyConnect using your enterprise software management system.
Important Security Considerations
Microsoft No Longer Supporting SHA-1—A secure gateway with a SHA-1 certificate or a certificate with SHA-1 intermediate certificates is considered valid by a Windows endpoint until January 2017. After January 2017, Windows endpoints will no longer consider a secure gateway with a SHA-1 certificate as trusted. Ensure that your secure gateway does not have a SHA-1 identity certificate and that any intermediate certificates are not SHA-1.
Files signed before January 1st, 2016 will be valid until January 1st, 2017.
Note: Due to the code signing changes, the current AnyConnect users must upgrade to AnyConnect release 3.1.13015, the future version of AnyConnect 4.2 MR, or AnyConnect 4.3+ releases in order to keep their AnyConnect functional on Windows platforms after January 1, 2017.
OpenSSL Cipher Suite Changes—Because the OpenSSL standards development team marked some cipher suites as compromised, we no longer support them beyond AnyConnect 3.1.05187. The unsupported cipher suites include DES-CBC-SHA, RC4-SHA, and RC4-MD5.
RC4 TLS cipher suites are not supported from 3.1.13015 onwards due to security policy enhancements.
We do not recommend using a self-signed certificate because of the possibility that a user could inadvertently configure a browser to trust a certificate on a rogue server and because of the inconvenience to users of having to respond to a security warning when connecting to your secure gateway.
Enable Strict Certificate Trust in the AnyConnect Local Policy
We strongly recommend you enable Strict Certificate Trust for the AnyConnect client for the following reasons:
With the increase in targeted exploits, enabling Strict Certificate Trust in the local policy helps prevent “man in the middle” attacks when users are connecting from untrusted networks such as those in coffee shops and airports.
Even if you use fully verifiable and trusted certificates, the AnyConnect client, by default, allows end users to accept unverifiable certificates. If your end users were subjected to a man-in-the-middle attack, they may be prompted to accept a malicious certificate. To remove this decision from your end users, enable Strict Certificate Trust.
The following behavioral changes have been made to server certificate verification:
SSL connections being performed via FQDN no longer make a secondary server certificate verification with the FQDN's resolved IP address for name verification if the initial verification using the FQDN fails.
IPsec and SSL connections require that if a server certificate contains Key Usage, the attributes must contain DigitalSignature AND (KeyAgreement OR KeyEncipherment). If the server certificate contains an EKU: for SSL the attributes must contain serverAuth, and for IPsec the attributes must contain serverAuth OR ikeIntermediate. Note that server certificates are not required to have a KU or an EKU to be accepted.
IPsec connections perform name verification on server certificates. The following rules are applied for the purposes of IPSec name verification:
–If a Subject Alternative Name extension is present with relevant attributes, name verification is performed solely against the Subject Alternative Name. Relevant attributes include DNS Name attributes for all certificates, and additionally include IP address attributes if the connection is being performed to an IP address.
–If a Subject Alternative Name extension is not present, or is present but contains no relevant attributes, name verification is performed against any Common Name attributes found in the Subject of the certificate.
–If a certificate uses a wildcard for the purposes of name verification, the wildcard must be in the first (left-most) subdomain only, and additionally must be the last (right-most) character in the subdomain. Any wildcard entry not in compliance is ignored for the purposes of name verification.
Increased Security in the AnyConnect Pre-deploy Package
The AnyConnect pre-deploy VPN package previously installed the VPN WebLaunch ActiveX control by default. Starting in AnyConnect 3.1, installation of the VPN ActiveX control is turned off by default. This change was made to favor the most secure configuration as the default behavior.
When pre-deploying the AnyConnect Client and Optional Modules, if you require the VPN ActiveX control to be installed with AnyConnect, you must use the NOINSTALLACTIVEX=0 option with msiexec or a transform. For example, on one line enter:
Important AnyConnect, Host Scan, and CSD Interoperability Information
We always recommend that you upgrade to the latest Host Scan engine version.
Note: AnyConnect will not establish a VPN connection when used with an incompatible version of Host Scan or CSD. Ensure that you are running the version of HostScan that is the same version as AnyConnect.
Note: If you cannot upgrade AnyConnect and Host Scan or AnyConnect and CSD at the same time, upgrade Host Scan or CSD first, then upgrade AnyConnect.
Note: Pre-login assessment and returning certificate information is not available. HostScan is not an authentication method; it simply checks to verify what exists on the device attempting to connect.
Important AnyConnect 3.1 and ASA 9.0 Interoperability Considerations
The following AnyConnect features require ASA 9.0 or later, or ASDM 7.0 or later, to be installed on your ASA for them to be effective:
IPv6 Support for AnyConnect VPN Features
Next Generation Encryption as it applies to VPN
AnyConnect integrates the following modules into the AnyConnect client package:
Network Access Manager
If you are using the ASA to deploy AnyConnect, the ASA can deploy all the optional modules. If pre-deploying using your SMS, you can deploy all modules, but you must pay special attention to the module installation sequence and other details.
AnyConnect shares its Host Scan component with Cisco Secure Desktop (CSD). The stand-alone Host Scan package for AnyConnect provides the same features as the Host Scan package that is part of CSD. The AnyConnect client can co-exist with Cisco Secure Desktop Vault, but it cannot be run or deployed from inside the Vault.
Every release of AnyConnect includes a localization MST file that administrators can upload to the ASA whenever they upload AnyConnect packages with new software. If you are using our localization MST files, make sure to update them with the latest release from CCO whenever you upload a new AnyConnect package.
Once AnyConnect 3.1.12020 has been automatically deployed to an endpoint, you cannot connect to a secure gateway configured with AnyConnect versions 4.0, 4.1, 4.1MR2, or 4.1MR4, which are incompatible. If you try to upgrade from the AnyConnect 3.1 MR12 version to any version other than AnyConnect 4.1MR8, 4.2, or 3.1 versions later than 3.1.12020, you will receive a notification that the upgrade is not allowed.
Once AnyConnect 3.1.11004 has been automatically deployed to an endpoint, you cannot connect to a secure gateway configured with AnyConnect versions 4.0, 4.1, 4.1MR2, or 4.1MR4, which are incompatible. If you try to upgrade from the AnyConnect 3.1 MR11 version to any version other than AnyConnect 4.1MR6 (or later) or 3.1 versions later than 3.1.11004, you will receive a notification that the upgrade is not allowed.
Once AnyConnect 3.1.10010 has been automatically deployed to an endpoint, you cannot connect to a secure gateway configured with AnyConnect versions 4.0, 4.1, and 4.1MR2, which are incompatible. If you try to upgrade from the AnyConnect 3.1 MR10 version to any version other than AnyConnect 4.1MR4 (or later) or 3.1 versions later than 3.1.10010, you will receive a notification that the upgrade is not allowed.
Refer to CSCuv12386 for further information.
Upgrading 3.0 AnyConnect Clients and Optional Modules
When you upgrade from AnyConnect Secure Mobility Client Release 3.0 to AnyConnect Secure Mobility Client Release 3.1, AnyConnect 3.1 performs the following operations:
Upgrades all previous versions of the core client and retains all VPN configurations.
Upgrades any Host Scan files used by AnyConnect.
Upgrading 2.5 and older AnyConnect Clients and Optional Modules
When you upgrade from any 2.5.x version of AnyConnect, the AnyConnect Secure Mobility Client Release 3.1 performs the following:
Upgrades all previous versions of the core client and retains all VPN configurations.
If you install Network Access Manager, AnyConnect retains all CSSC 5.x configuration for use with Network Access Manager, then removes CSSC 5.x.
Upgrades any Host Scan files used by AnyConnect.
Does not upgrade the Cisco IPsec VPN client (or remove it). However, the AnyConnect 3.1 client can coexist on the computer with the IPsec VPN client.
Does not upgrade and cannot coexist with Cisco’s ScanSafe AnyWhere+. You must uninstall AnyWhere+ before installing the AnyConnect Secure Mobility Client.
Note: If you are upgrading from the legacy Cisco VPN client, the MTU value on the physical adapters may have been lowered to 1300. You should restore the MTU back to the default (typically 1500) for each adapter so as to achieve optimal performance when using AnyConnect.
Web-based installation May Fail on 64-bit Windows
This issue applies to Internet Explorer versions 10 and 11, on Windows versions 7 and 8.
When the Windows registry entry HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\TabProcGrowth is set to 0, Active X has problems during AnyConnect web deployment.
AnyConnect Compatibility with Microsoft Windows 10
AnyConnect 3.1MR10 (3.1.10010) and later are compatible with Windows 10 official release. Technical Assistance Center (TAC) support will be available beginning on 7/29/2015.
For best results, we recommend a clean install of AnyConnect on Windows 10 system and not an upgrade from Windows 7/8/8.1. If you are planning to perform an upgrade from Windows 7/8/8/1 with AnyConnect pre-installed, make sure that you first upgrade AnyConnect prior to upgrading the Operating System. The Network Access Manager module must be uninstalled prior to upgrading to Windows 10. After the first upgrade is complete, it can be re-installed on the system. You may also choose to fully uninstall AnyConnect and re-install one of the supported versions after upgrading to Windows 10.
AnyConnect Support for Windows 8.x
ASDM version 7.02 or higher
Limitations to AnyConnect Support for Windows 8.x
Upgrading to Windows 8.1 requires you to uninstall AnyConnect, and reinstall it after your Windows upgrade is complete.
AnyConnect is not supported on Windows RT. There are no APIs provided in the operating system to provide this functionality. Cisco has an open request with Microsoft on this topic. Customers who want this functionality should contact Microsoft to express their interest.
Other third-party product’s incompatibility with Windows 8 prevent AnyConnect from establishing a VPN connection over wireless networks. Here are two examples of this problem:
To work around this problem, uninstall Wireshark or disable the WinPcap service, reboot your Windows 8 computer, and attempt the AnyConnect connection again.
–Outdated wireless cards or wireless card drivers that do not support Windows 8 prevent AnyConnect from establishing a VPN connection.
To work around this problem, make sure you have the latest wireless network cards or drivers that support Windows 8 installed on your Windows 8 computer.
AnyConnect is not integrated with the new UI framework, known as the Metro design language, that is deployed on Windows 8; however, AnyConnect does run on Windows 8 in desktop mode.
Verify that the driver on the client system is supported by Windows 8. Drivers that are not supported by Window 8 may have intermittent connection problems.
For Network Access Manager, machine authentication using machine password will not work on Windows 8 / Server 2012 unless a registry fix described in Microsoft KB 2743127 (http://support.microsoft.com/kb/2743127) is applied to the client desktop. This fix includes adding a DWORD value LsaAllowReturningUnencryptedSecrets to the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa registry key and setting this value to 1. This change permits Local Security Authority (LSA) to provide clients like Cisco Network Access Manager with the Machine password. It is related to the increased default security settings in Windows 8 / Server 2012. Machine authentication using Machine certificate does not require this change and will work the same as it worked with pre-Windows 8 operating systems.
Note Machine authentication allows a client desktop to be authenticated to the server before the user logs in. During this time server can perform scheduled administrative tasks for this client machine. Machine authentication is also required for the EAP Chaining feature where a server can authenticate both User and Machine for a particular client. This will result in identifying company assets and applying appropriate access policy. For example, if this is a personal asset (PC/laptop/tablet), and a company login is used, server will fail Machine authentication, but succeed User authentication and will apply proper access restrictions to this client desktop.
The Export Stats button on the Preferences > VPN > Statistics tab saves the file on the desktop. In other versions of Windows, the user is asked where to save the file.
HP Protect tools do not work with AnyConnect on Windows 8.x.
For Network Access Manager, machine authentication using machine password will not work on Windows 10 / Server 2012 unless a registry fix described in Microsoft KB 2743127 (http://support.microsoft.com/kb/2743127) is applied to the client desktop. This fix includes adding a DWORD value LsaAllowReturningUnencryptedSecrets to the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa registry key and setting this value to 1. This change permits Local Security Authority (LSA) to provide clients like Cisco Network Access Manager with the Machine password. It is related to the increased default security settings in Windows 10/ Server 2012. Machine authentication using Machine certificate does not require this change and will work the same as it worked with pre-Windows 8 operating systems.
AnyConnect 3.x Unsupported with Mac OS X El Capitan
AnyConnect 3.1.07021 is a maintenance release that resolves the 2015 OpenSSL Vulnerabilities in CSCus42746 and other the defects described in Caveats Resolved by AnyConnect 3.1.07021. Also, read the section below for issues with Microsoft’s February 10, 2015 patch.
Microsoft Permanent Fix for Windows 8.1 AnyConnect Incompatibility
Microsoft’s Patch update on February 10, 2015 introduced an OS regression which impacts Windows 8.1 users running AnyConnect. This issue will also impact some Windows 7 users if they have IE11 installed.
AnyConnect 3.1.06073 is a maintenance release that resolves the defects described in Caveats Resolved by AnyConnect 3.1.06073, and contains Host Scan Engine 3.1.06073. The versions of Antivirus, Antispyware, and Firewall products supported by Hostscan are listed on http://www.cisco.com/c/en/us/support/security/anyconnect-secure-mobility-client/products-device-support-tables-list.html.
This section identifies the management and endpoint requirements for this release. For endpoint OS support and license requirements for each feature, see AnyConnect Secure Mobility Client Features, Licenses, and OSs.
AnyConnect 3.1 installations can coexist with other VPN clients, including IPsec clients, on all supported endpoints; however, we do not support running AnyConnect while other VPN clients are running.
The following sections identify the minimum management and endpoint requirements:
You must upgrade to ASA 9.0 if you want to use the following features:
–Cisco Next Generation Encryption “Suite-B” security
–AnyConnect client deferred upgrades
You must use ASA 8.4(1) or later if you want to do the following:
–Use the ASDM to edit non-VPN client profiles (such as Network Access Manager, Web Security, or Telemetry).
–Use the services supported by a Cisco IronPort Web Security Appliance license. These services let you enforce acceptable use policies and protect endpoints from websites found to be unsafe, by granting or denying all HTTP and HTTPS requests.
–Deploy firewall rules. If you deploy always-on VPN, you might want to enable split tunneling and configure firewall rules to restrict network access to local printing and tethered mobile devices.
–Configure dynamic access policies or group policies to exempt qualified VPN users from an always-on VPN deployment.
–Configure dynamic access policies to display a message on the AnyConnect GUI when an AnyConnect session is in quarantine.
Note: The minimum flash memory recommended for all ASA 5500 models using AnyConnect 3.1 is 512MB. This will allow hosting of multiple endpoint operating systems, and logging and debugging to be enabled on the ASA.
Due to flash size limitations on the ASA 5505 (maximum of 128 MB), not all permutations of the AnyConnect package will be able to be loaded onto this model. To successfully load AnyConnect, you will need to reduce the size of your packages (i.e. fewer OSs, no host Scan, etc,) until they fit on the available flash.
Check for the available space before proceeding with the AnyConnect install or upgrade. You can use one of the following methods to do so:
Table 3 Microsoft Windows OS Support for the modules and new features in AnyConnect 3.1.
AnyConnect 3.1 Module
Windows XP SP3 x86 (32-bit)
Windows XP SP2 x64 (64-bit)
Windows Vista x86
x86 (32-bit) and x64 (64-bit)
x86 (32-bit) and x64 (64-bit)
Windows 8, 8.1, and 8.1 Update 1
x86 (32-bit) and x64 (64-bit)
Network Access Manager
Yes x86 (32-bit) only
Posture & Host Scan
Yes x86 (32-bit) only
Yes x86 (32-bit) only
Yes x86 (32-bit) only
Windows Support Notes
After April 8, 2014, Microsoft will no longer provide new security updates, non-security hotfixes, free or paid assisted support options, or online technical content updates for Windows XP (http://www.microsoft.com/en-us/windows/endofsupport.aspx). On the same date, Cisco will stop providing customer support for AnyConnect releases running on Windows XP, and we will not offer Windows XP as a supported operation system for future AnyConnect releases.
When Windows XP is configured with a secondary IP address, starting an AnyConnect connection starts the IpFilterDriver, which blocks traffic over the secondary IP. To prevent this, disable the ipFilterDriver with the following command:
sc config IpFilterDriver start= disabled
Make sure you enter the whitespace between “start=” and “disabled”.
Upgrading from Windows XP to Windows Vista or Windows 7 or later requires a clean install since the Cisco AnyConnect Virtual Adapter is not preserved during the upgrade. Manually uninstall AnyConnect, upgrade Windows, then reinstall AnyConnect manually or via WebLaunch.
Windows 2003 Server (32 bit) is supported for Network Access Manager only.
Windows 2008 is not supported; however, we do not prevent the installation of AnyConnect 3.1 on this OS.
To start AnyConnect with WebLaunch, you must use the 32-bit version of Firefox 3.0+ and enable ActiveX or install Sun JRE 1.4+.
Note: Internet Explorer 6.0 is no longer supported.
AnyConnect VPN is compatible with 3G data cards which interface with Windows 7 or later via a WWAN adapter.
On Windows XP, schannel.dll supports only 3DES and not AES encryption; therefore, an ASA on which XP clients terminate must have 3DES enabled with the ssl encryption aes128-sha1 aes256-sha1 3des-sha1 command.
Pentium class processor or greater.
100 MB hard disk space.
Microsoft Installer, version 3.1.
Table 4 Linux OS Support for the modules and new features in AnyConnect 3.1
AnyConnect Module 3.1
Red Hat Enterprise Linux 6.x (32-bit) and 6.4 (64-bit)
Ubuntu 9.x, 10.x, and 11.x (32-bit) and Ubuntu 12.04 & 12.10 (64-bit)
Suite-B (IPsec only)
Network Access Manager
Posture & Host Scan
x86 instruction set
32-bit or 64-bit processor
32 MB RAM
20 MB hard disk space
Superuser privileges are required for installation
libstdc++ users must have libstdc++.so.6(GLIBCXX_3.4) or higher, but below version 4
Java 5 (1.5) or later. The only version that works for web installation is Sun Java. You must install Sun Java and configure your browser to use that instead of the default package.
zlib - to support SSL deflate compression
xterm - only required if you're doing initial deployment of AnyConnect via Weblaunch from ASA clientless portal.
libpango 1.0 or a compatible build such as package pangox-compat-0.0.2-2.el7.x86_64.rpm or pangox-compat-0.0.2-3.fc20.x86_64.rpm
iptables 1.2.7a or later
tun module supplied with kernel 2.4.21 or 2.6
Linux Support Notes
The AnyConnect GUI is not supported on all Linux distributions. When the GUI is supported, it's appearance is the same as the AnyConnect version 2.5 GUI.
Mac OS X
Table 5 Mac OS X Support the modules and new features in AnyConnect 3.1
AnyConnect Module 3.1
Mac OS X 10.8, 10.9, & 10.10
x86 (32-bit) or x64 (64-bit)
Suite-B (IPsec only)
Network Access Manager
Posture & Host Scan
Yes x86 (32-bit) only
Max OS X Support Notes
Mac OS X 10.5 is no longer supported. AnyConnect 3.1 will not install on this platform.
Mac OS X 10.6, and 10.7 are no longer supported.
Mac OS X Requirements
AnyConnect requires 50MB of hard disk space.
To operate correctly with Mac OS X, AnyConnect requires a minimum display resolution of 1024 by 640 pixels.
Mac OS X 10.8 introduces a new feature called Gatekeeper that restricts which applications are allowed to run on the system. You can choose to permit applications downloaded from:
Mac App Store
Mac App Store and identified developers
The default setting is Mac App Store and identified developers (signed applications). AnyConnect release 3.1 is a signed application, but it is not signed using an Apple certificate. This means that you must either select the Anywhere setting or use Control-click to bypass the selected setting to install and run AnyConnect from a pre-deploy installation. Users who web deploy or who already have AnyConnect installed are not impacted. For further information see: http://www.apple.com/macosx/mountain-lion/security.html.
Note: Web launch or OS upgrades (for example 10.9 to 10.10) install as expected. Only the pre-deploy installation requires additional configuration as a result of Gatekeeper.
We support all non-beta AnyConnect software versions available on the Cisco AnyConnect VPN Software Download site; however, we provide fixes and enhancements only in maintenance or feature releases based on the most recently released version.
AnyConnect UI Fails Due to Missing Dependency libpangox
On many newer Linux distributions, the AnyConnect UI may fail to start with the error:
error while loading shared libraries: libpangox-1.0.so.0: cannot open shared object file: No such file or directory
The missing library is obsolete and is no longer available. This impacts other applications, not just AnyConnect.
Pango has released the source code of a compatible library that has been built by others and is available online. To resolve this problem, find and install either the package pangox-compat-0.0.2-2.el7.x86_64.rpm or pangox-compat-0.0.2-3.fc20.x86_64.rpm.
OS X 10.9 Safari Can Disable Weblaunch
The default security settings in the version of Safari that comes with OS X 10.9 (Mavericks) prevents AnyConnect Weblaunch from working. To configure Safari to allow Weblaunch, edit the URL of the ASA to Unsafe Mode, as described below.
Open Safari > Preferences > Security > Manage Website Settings. Click on the ASA and select run in Unsafe Mode.
Internet Explorer, Java 7, and AnyConnect 3.1.1 Interoperability
Supported versions of Internet Explorer stop working when the user attempts to connect to the ASA, when Java 7 is installed on the endpoint, when Host Scan is installed and enabled on the ASA, and when AnyConnect 3.1.1 is installed and enabled on the ASA.
This does not happen when Active X or earlier versions of Java 7 are installed. To avoid this, use a supported version of Java on the endpoint that is earlier than Java 7.
Refer to the Bug Toolkit and defect CSCuc48299 to verify.
Implicit DHCP filter applied when Tunnel All Networks Configured
To allow local DHCP traffic to flow in the clear when Tunnel All Networks is configured, AnyConnect adds a specific route to the local DHCP server when the AnyConnect client connects. To prevent data leakage on this route, AnyConnect also applies an implicit filter on the LAN adapter of the host machine, blocking all traffic for that route except DHCP traffic.
AnyConnect VPN over Tethered Devices
Cisco has qualified the AnyConnect VPN client over a bluetooth or USB tethered Apple iPhone only. Network connectivity provided by other tethered devices should be verified with the AnyConnect VPN client before deployment.
AnyConnect Smart Card Support
AnyConnect supports Smartcard provided credentials in the following environments:
Microsoft CAPI 1.0 and CAPI 2.0 on Windows 7 and Windows 8.
Keychain via Tokend on Mac OS X, 10.4 and higher
Note: AnyConnect does not support Smart cards on Linux or PKCS #11 devices.
AnyConnect Virtual Testing Environment
Cisco performs a portion of AnyConnect client testing using these virtual machine environments:
VMWare ESXi Hypervisor (vSphere) 4.0.1 and later
VMWare Fusion 2.x, 3.x, and 4.x
We do not support running AnyConnect in virtual environments; however, we expect AnyConnect to function properly in the VMWare environments we test in.
If you encounter any issues with AnyConnect in your virtual environment, report them. We will make our best effort to resolve them.
UTF-8 Character Support for AnyConnect Passwords
AnyConnect 3.0 or later used with ASA 8.4(1) or later supports UTF-8 characters in passwords sent using RADIUS/MSCHAP and LDAP protocols.
Disabling Auto Update May Prevent Connectivity Due to a Version Conflict
When Auto Update is disabled for a client running AnyConnect release 2.5.x or 3.0.2, the ASA must have the same version (2.5.x or 3.0.2) or earlier installed or the client will fail to connect to the VPN.
To avoid this problem, configure the same version or earlier AnyConnect package on the ASA, or upgrade the client to the new version by enabling Auto Update.
New Certificate Required
AnyConnect 3.0.1047 is signed with the new certificate VeriSign Class 3 Public Primary Certification Authority - G5. Upon installation, Windows XP, Windows Vista, Mac OS X, and Linux users might see a downloader error message, such as the following:
An internal certificate chaining error has occurred.
This event can occur if one or all of the following are true:
Root certificates were intentionally pruned.
Update Root Certificates is disabled.
The internet is not reachable when an upgrade occurs (for example, you have your ASA in a private network without Internet access).
AnyConnect installations and upgrades might require endpoint users to install the root CA before upgrading or installing AnyConnect. To do so, enable Update Root Certificates and verify that the Internet is reachable before the AnyConnect installation. By default, Update Root Certificates is enabled. Users can also update the root CA manually, as instructed on the VeriSign website.
Interoperability between Network Access Manager and other Connection Managers
When the Network Access Manager operates, it takes exclusive control over the network adapters and blocks attempts by other software connection managers (including the Windows native connection manager) to establish connections. Therefore, if you want AnyConnect users to use other connection managers on their endpoint computers (such as iPassConnect Mobility Manager), they must disable Network Access Manager either through the Disable Client option in the Network Access Manager GUI, or by stopping the Network Access Manager service.
Network Interface Card Drivers Incompatible with Network Access Manager
The Intel wireless network interface card driver, version 184.108.40.206, is incompatible with Network Access Manager. If this driver is installed on the same endpoint as the Network Access Manager, it can cause inconsistent network connectivity and an abrupt shutdown of the Windows operating system.
The AnyConnect client relies on the Windows Cryptographic Service Provider (CSP) of the certificate for hashing and signing of data required during the IKEv2 authentication phase of the IPsec/IKEv2 VPN connection. If the CSP does not support SHA 2 algorithms, and the ASA is configured for the pseudo-random function (PRF) SHA256, SHA384, or SHA512, and the connection profile (tunnel-group) is configured for certificate or certificate and AAA authentication, certificate authentication fails. The user receives the message Certificate Validation Failure.
This failure occurs for Windows only, for certificates that belong to CSPs that do not support SHA 2-type algorithms. Other supported OSs do not experience this problem.
To avoid this problem you can configure the PRF in the IKEv2 policy on the ASA to md5 or sha (SHA 1).
Alternatively, you can modify the certificate CSP value for native CSPs that work:
For Windows 7 or later —Microsoft Enhanced RSA and AES Cryptographic Provider
Note: Do not apply this workaround to SmartCards certificates. You cannot change the CSP names. Instead, contact the SmartCard provider for an updated CSP that supports SHA 2 algorithms.
Note: Performing the following workaround actions could corrupt the user certificate if you perform them incorrectly. Use extra caution when specifying changes to the certificate.
You can use the Microsoft Certutil.exe utility to modify the certificate CSP values. Certutil is a command-line utility for managing a Windows CA, and is available in the Microsoft Windows Server 2003 Administration Tools Pack. You can download the Tools Pack at this URL:
Provider = Microsoft Enhanced RSA and AES Cryptographic Provider
Signature test passed
1. Identify the <CN> attribute in the certificate. In the example, the CN is Carol Smith. You need this information for the next step.
2. Modify the certificate CSP using the following command. The example below uses the subject <CN> value to select the certificate to modify. You can also use other attributes.
On Windows Vista and Windows 7 or later, use this command:
certutil -csp "Microsoft Enhanced RSA and AES Cryptographic Provider" -f -repairstore -user My <CN> carol smith
On Windows XP, use this command:
certutil -csp "Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype)" -f -repairstore -user My <CN> carol smith
3. Repeat step 2 and verify the new CSP value appears for the certificate.
Configuring Antivirus Applications for Host Scan
Antivirus applications can misinterpret the behavior of some of the applications included in the posture module and the Host Scan package as malicious. Before installing the posture module or Host Scan package, configure your antivirus software to “white-list” or make security exceptions for these Host Scan applications:
hostname(config-group-webvpn)# anyconnect mtu 1200
To set the MTU using ASDM, go to Configuration > Network (Client) Access > Group Policies > Add or Edit > Advanced > SSL VPN Client.
MTU Automatically Adjusted When Using DTLS
If Dead Peer Detection (DPD) is enabled for DTLS, the client automatically determines the path MTU. If you previously reduced the MTU using the ASA, you should restore the setting to the default (1406). During tunnel establishment, the client auto-tunes the MTU using special DPD packets. If you still have a problem, use the MTU configuration on the ASA to restrict the MTU as before.
Network Access Manager and Group Policy
Windows Active Directory Wireless Group Policies manage the wireless settings and any wireless networks that are deployed to PCs in a specific Active Directory Domain. When installing the Network Access Manager, administrators must be aware that certain wireless GPOs can affect the behavior of the Network Access Manager. Administrators should test the GPO policy settings with the Network Access Manager before doing full GPO deployment. The following GPO conditions may prevent the Network Access Manager from operating as expected (CSCtk57290):
When using the Windows 7 or later Only use Group Policy profiles for allowed networks option
When deploying XP wireless GPO policy on Windows 7 or later
Full Authentication Required if Roaming between Access Points
A mobile endpoint running Windows 7 or later must do a full EAP authentication instead of leveraging the quicker PMKID reassociation when the client roams between access points on the same network. Consequently, in some cases, AnyConnect prompts the user to enter credentials for every full authentication if the active profile requires it.
User Guideline for Cisco Cloud Web Security Behavior with IPv6 Web Traffic
Unless an exception for an IPv6 address, domain name, address range, or wild card is specified, IPv6 web traffic is sent to the scanning proxy where it performs a DNS lookup to see if there is an IPv4 address for the URL the user is trying to reach. If the scanning proxy finds an IPv4 address, it uses that for the connection. If it does not find an IPv4 address, the connection is dropped.
If you want all IPv6 traffic to bypass the scanning proxies, you can add this static exception for all IPv6 traffic: /0. Doing this makes all IPv6 traffic bypass all scanning proxies. This means that IPv6 traffic is not protected by Cisco Cloud Web Security.
Preventing Other Devices in a LAN from Displaying Hostnames
After one uses AnyConnect to establish a VPN session with Windows 7 or later on a remote LAN, the network browsers on the other devices in the user’s LAN display the names of hosts on the protected remote network. However, the other devices cannot access these hosts.
To ensure the AnyConnect host prevents the hostname leak between subnets, including the name of the AnyConnect endpoint host, configure that endpoint to never become the master or backup browser.
1. Enter regedit in the Search Programs and Files text box.
2. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Browser\Parameters\
3. Double-click MaintainServerList.
The Edit String window opens.
1. Enter No.
2. Click OK.
3. Close the Registry Editor window.
An AnyConnect certificate revocation warning popup window opens after authentication if AnyConnect attempts to verify a server certificate that specifies the distribution point of an LDAP certificate revocation list (CRL) if the distribution point is only internally accessible.
If you want to avoid the display of this popup window, do one of the following:
Obtain a certificate without any private CRL requirements.
Disable server certificate revocation checking in Internet Explorer.
Note: Disabling server certificate revocation checking in Internet Explorer can have severe security ramifications for other uses of the OS.
Messages in the Localization File Can Span More than One Line
If you try to search for messages in the localization file, they can span more than one line, as shown in the example below:
"The service provider in your current location is restricting access to the "
"Secure Gateway. "
AnyConnect for Mac OS X Performance when Behind Certain Routers
When the AnyConnect client for Mac OS X attempts to create an SSL connection to a gateway running IOS, or when the AnyConnect client attempts to create an IPsec connection to an ASA from behind certain types of routers (such as the Cisco Virtual Office (CVO) router), some web traffic may pass through the connection while other traffic drops. AnyConnect may calculate the MTU incorrectly.
To work around this problem, manually set the MTU for the AnyConnect adaptor to a lower value using the following command from the Mac OS X command line:
sudo ifconfig utun0 mtu 1200 (For Mac OS X v10.6 and later)
Preventing Windows Users from Circumventing Always-on
On Windows computers, users with limited or standard privileges may sometimes have write access to their program data folders. This could allow them to delete the AnyConnect profile file and thereby circumvent the always-on feature. To prevent this, configure the computer to restrict access to the following folders (or at least the Cisco sub-folder):
For Windows 7 or later users: C:\ProgramData
Using the Windows 7 or later Wireless Hosted Network feature can make AnyConnect unstable. When using AnyConnect, we do not recommend enabling this feature or running front-end applications that enable it (such as Connectify or Virtual Router).
AnyConnect Requires That the ASA Be Configured to Accept TLSv1 Traffic
AnyConnect requires the ASA to accept TLSv1 traffic, but not SSLv3 traffic. The SSLv3 key derivation algorithm uses MD5 and SHA-1 in a way that can weaken the key derivation. TLSv1, the successor to SSLv3, resolves this and other security issues present in SSLv3.
Thus, the AnyConnect client cannot establish a connection with the following ASA settings for “ssl server-version”:
ssl server-version sslv3
ssl server-version sslv3-only
Trend Micro Conflicts with Install
If you have Trend Micro on your device, the Network Access Manager will not install because of a driver conflict. You can uninstall the Trend Micro or uncheck trend micro common firewall driver to bypass the issue. Trend Micro also conflicts with Web Security.
What Host Scan Reports
None of the supported antivirus, antispyware, and firewall products report the last scan time information. Host scan reports the following:
For antivirus and antispyware
–File system protection status (active scan)
–Data file time (last update and timestamp)
–Is firewall enabled
ActiveX Controls May Fail During Web-Deployment and Upgrade
Installation of an ActiveX control requires administrative privileges.
AnyConnect web-deployment must install an ActiveX control. If the user can't install that control, then web-deployment fails.
The AnyConnect ActiveX control will change periodically, due to a security fix or the addition of new functionality. Upgrading the ActiveX control will fail during Weblaunch for users with Standard privileges.
To avoid these problems, Administrators can deploy using the AnyConnect pre-installer, SMS, GPO or other administrative deployment methodology.
Using the Manual Install Option on Mac OS X if the Java Installer Fails
If users use WebLaunch to start AnyConnect on a Mac and the Java installer fails, a dialog box presents a Manual Install link. Users should follow this procedure when this happens:
1. Click Manual Install. A dialog box presents the option to save a.dmg file that contains an OS X installer.
2. Mount the disk image (.dmg) file by opening it and browsing to the mounted volume using Finder.
3. Open a Terminal window and use the CD command to navigate to the directory containing the file saved. Open the.dmg file and run the installer.
4. Following the installation, choose Applications > Cisco > Cisco AnyConnect Secure Mobility Client to initiate an AnyConnect session, or use Launchpad.
No Pro-Active Key Caching (PKC) or CCKM Support
Network Access Manager does not support PKC or CCKM caching. On Windows 7, fast roaming with a non-Cisco wireless card is unavailable.
Application Programming Interface for the AnyConnect Secure Mobility Client
The AnyConnect Secure Mobility Client includes an Application Programming Interface (API) for customers who want to write their own client programs.
The API package contains documentation, source files, and library files to support a C++ interface for the Cisco AnyConnect VPN Client. You can use the libraries and example programs for building on Windows, Linux and MAC platforms. The Makefiles (or project files) for the Windows platform are also included. For other platforms, it includes platform specific scripts showing how to compile the example code. Network administrators can link their application (GUI, CLI, or embedded application) with these files and libraries.
You can download the APIs from Cisco.com.
For support issues regarding the AnyConnect API, send e-mail to the following address: firstname.lastname@example.org.
Caveats describe unexpected behavior or defects in Cisco software releases.
The Release Notes for the AnyConnect Secure Mobility Client, Release 3.1 is a living document that we update as we continue to produce maintenance releases and major releases of AnyConnect. As the development of AnyConnect continues, should we find caveats that impact AnyConnect 3.1, or resolve caveats that improve AnyConnect 3.1, we will update these tables and republish this document.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.