Release Notes for Cisco AnyConnect Secure Mobility Client, Release 4.10

Incompatibility Warning: If you are an Identity Services Engine (ISE) customer running 2.0 (or later), you must read this before proceeding!

The ISE RADIUS has supported TLS 1.2 since release 2.0; however, there is a defect in the ISE implementation of EAP-FAST using TLS 1.2, tracked by CSCvm03681. The defect has been fixed in the 2.4p5 release of ISE. The fix will be made available in future hot patches for supported releases of ISE.

If Network Access Manager 4.7 (and later) is used to authenticate using EAP-FAST with any ISE releases that support TLS 1.2 prior to the above releases, the authentication will fail, and the endpoint will not have access to the network.

ISE 2.6 (and later) with AnyConnect 4.7MR1 (and later) supports IPv6 non-redirection flows (using stage 2 discovery) on wired and VPN flows.

AnyConnect temporal agent flows are working on IPv6 networks based on network topology. ISE supports multiple ways of IPv6 configuration on a network interface (for example, eth0/eth1).

IPv6 networks with regards to ISE posture flows have the following limitations: [IPv6] ISE posture discovery is in infinite loop due to specific type of network adapters (for example, Microsoft Teredo virtual adapter) (CSCvo36890).

ISE 2.0 is the minimum release capable of deploying AnyConnect software to an endpoint and posturing that endpoint using the new ISE Posture module in AnyConnect 4.0 and later.

If you are installing or updating the AnyConnect ISE Posture module, the package and modules configured on ASA must be the same as the ones configured on ISE. VPN is always upgraded when other modules are upgraded, and a VPN module upgrade is not allowed from ISE when the tunnel is active.

To deploy AnyConnect from an ISE headend and use the ISE Posture module, a Cisco ISE Premier License is required on the ISE Administration node. For detailed ISE license information, see the Cisco ISE Licenses chapter of the Cisco Identity Services Engine Admin Guide .

AnyConnect is not supported on Windows RT. There are no APIs provided in the operating system to implement this functionality. Cisco has an open request with Microsoft on this topic. Those 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:

WinPcap service “Remote Packet Capture Protocol v.0 (experimental)” distributed with Wireshark does not support Windows

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.

If you are using Network Access Manager on a system that supports standby, Cisco recommends that the default Windows 8.x association timer value (5 seconds) is used. If you find the Scanlist in Windows appears shorter than expected, increase the association timer so that the driver can complete a network scan and populate the scanlist.

Verify that the driver on the client system is supported by your Windows version. Drivers that are not supported may have intermittent connection problems.

For Network Access Manager, machine authentication using machine password will not work on Windows 8 or 10 / Server 2012 unless a registry fix described in Microsoft 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.

Machine authentication using machine certificate (rather than machine password) does not require a change and is the more secure option. Because machine password was accessible in an unencrypted format, Microsoft changed the OS so that a special key was required. Network Access Manager cannot know the password established between the operating system and active directory server and can only obtain it by setting the key above. This change permits Local Security Authority (LSA) to provide clients like Cisco Network Access Manager with the machine password.

Machine authentication allows a client desktop to be authenticated to the network before the user logs in. During this time the administrator can perform scheduled administrative tasks for this client machine. Machine authentication is also required for the EAP Chaining feature where a RADIUS server can authenticate both the User and Machine for a particular client. This will result in identifying company assets and applying appropriate access policies. For example, if this is a personal asset (PC/laptop/tablet), and corporate credentials are used, the endpoint will fail Machine authentication, but succeed User authentication, and the proper network access restrictions are applied to the user's network connection.

On Windows 8, 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.

Because of the introduction of access control in macOS 10.15, you may see additional popups when Secure Firewall Posture (formerly HostScan) or ISE posture are performing a scan on the endpoint. You are required to accept which files and folders can be accessed and scanned.

For the latest end-user license agreement, see Cisco End User License Agreement, AnyConnect Secure Mobility Client .

For our open source licensing acknowledgments, see Open Source Software Used in AnyConnect Secure Mobility Client .

To deploy AnyConnect from an ISE headend and use the ISE Posture module, a Cisco ISE Premier License is required on the ISE Administration node. For detailed ISE license information, see the Cisco ISE Licenses chapter of the Cisco Identity Services Engine .

To deploy AnyConnect from a Secure Firewall ASA headend and use the VPN and HostScan modules, an Advantage or Premier license is required. Trial licenses are available. See the AnyConnect Ordering Guide .

For an overview of the Advantage and Premier licenses and a description of which license the features use, see AnyConnect Secure Mobility Client Features, Licenses, and OSs .

Predeploy—New installations and upgrades are done either by the end user, or by using an enterprise software management system (SMS).

Web Deploy—The AnyConnect package is loaded on the headend, which is either a Secure Firewall ASA or ISE server. When the user connects to a Secure Firewall ASA or to ISE, AnyConnect is deployed to the client.

For new installations, the user connects to a headend to download AnyConnect . The client is either installed manually, or automatically (web-launch).

Cloud Update—After the Umbrella Roaming Security module is deployed, you can update any AnyConnect modules using one of the above methods, as well as Cloud Update. With Cloud Update, the software upgrades are obtained automatically from the Umbrella cloud infrastructure, and the update track is dependent upon that and not any action of the administrator. By default, automatic updates from Cloud Update are disabled.

When you deploy AnyConnect , you can include the optional modules that enable extra features, and client profiles that configure the VPN and other features. Keep in mind the following:

This issue applies to Internet Explorer versions 10 and 11, on Windows 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. http://support.microsoft.com/kb/2716529 for more information.

The solution to is to:

On Windows 8, starting Internet Explorer from the Windows start screen runs the 64-bit version. Starting from the desktop runs the 32-bit version.

Cisco only provides fixes and enhancements based on the most recent Version 4.10 release. TAC support is available to any customer with an active AnyConnect Version 4.10 term/contract running a released version of AnyConnect Version 4.10 . If you experience a problem with an out-of-date software version, you may be asked to validate whether the current maintenance release resolves your issue.

Software Center access is limited to AnyConnect Version 4.10 versions with current fixes. We recommend that you download all images for your deployment, as we cannot guarantee that the version you are looking to deploy will still be available for download at a future date.

AnyConnect supports DNS load balancing using SAML authentication for an embedded browser. Using Secure Firewall ASA, Secure Firewall Threat Defense, or other headends and an external/native browser, VPN headend DNS load balancing is not supported due to operating system limitations, which restrict the ability for Cisco Secure Client to control the necessary underlying conditions.

Those running AnyConnect on macOS 12.x may experience a loss of DNS (name resolution), requiring a reboot for restoration. The cause has been identified as a macOS bug, which has been addressed in macOS 12.3 (FB9803355).

Global DNS settings Searchlist and UseDomainNameDevolution are used by AnyConnect to build the DNS suffix search list for a VPN connection. Any overrides configured via local group policy will be ignored.

Encrypted Domain Name System (DNS) resolution impacts AnyConnect Secure Mobility Client functionality, namely network flows targeting FQDNs resolved via encrypted DNS either circumvent or are not properly handled by the following AnyConnect Secure Mobility Client features: Umbrella DNS protection, Umbrella web protection (when name-based redirect rules are used), VPN (dynamic split tunneling and Always On with name-based exceptions), Network Visibility (reporting of peer FQDN). To mitigate this impact, you should disable encrypted DNS in browser settings pertaining to AnyConnect Secure Mobility Client users.

As an additional mitigation, AnyConnect Secure Mobility Client prohibits DNS over HTTPS (DoH) name resolution for the Windows DNS client via local policy setting Configure DNS over HTTP (DoH) name resolution (under Computer Configuration > Administrative Templates > Network > DNS Client). This change is applicable to Windows 11 and later versions and is enforced while any of the following modules is active: VPN, Umbrella Roaming Security, or Network Visibility. AnyConnect Secure Mobility Client does not alter this policy setting if a conflicting setting of higher precedence (for example, domain GPO setting) is detected.

You must uninstall current existing AnyConnect (including all modules) before switching to use RPM or DEB installer. See CSCwa16755 for the workaround to a known issue.

When a root certificate authority (CA) is public trusted, it is already in the File Certificate Store. However, if the Firefox NSS store is left enabled at the same time, the OCSP check might be bypassed, as we only support OCSP check with File Cert Store. To prevent this bypass, disable Firefox NSS store by setting ExcludeFirefoxNSSCertStore to true in the local policy file.

When using Trusted Network Detection, the automatic VPN connection may not be initiated according to the TND policy, if the system route table does not contain a default route.

If you are using web deploy to upgrade to AnyConnect or HostScan 4.10 from a version prior to 4.9.01095, an error could result. Since AnyConnect versions prior to 4.9.01095 did not have the capacity to parse the system CA store, the result is an upgrade failure, because the correct NSS certificate store path could not be determined in the user's profile directory. If you are upgrading to AnyConnect 4.10 from a release prior to 4.9.01095, copy the root certificate (DigiCertAssuredIDRootCA.pem) to /opt/.cisco/certificates/ca prior to upgrading AnyConnect on the endpoint.

If you are using Ubuntu 20.04 (which has kernel version 5.4), you must use AnyConnect 4.8 (or later), or Network Visibility Module installation fails.

Local and/or network proxies (such as software/security applications like Fiddler, Charles Proxy, or Third-party Antimalware/Security software that includes Web HTTP/HTTPS inspection and/or decryption capabilities) are not compatible with AnyConnect .

The Ubuntu NetworkManager Connectivity Checking functionality allows periodic testing, whether the internet can be accessed or not. Because Connectivity Checking has its own prompt, you can receive a network logon window if a network without internet connectivity is detected. To avoid such network prompts, that aren’t tied to a browser window and don't have download capability, you should disable Connectivity Checking in Ubuntu 17 and beyond. By disabling, the user will be able to download a file from the ISE portal using a browser for ISE-based AnyConnect web deployment.

Before doing a web deploy onto a Linux endpoint, you must disable access control with the xhost+ command. Xhost controls the access of a remote host running a terminal on the endpoint, which is restricted by default. Without disabling access control, AnyConnect web deployment fails.

With the fix of CSCvu65566 and its device ID computation change, certain deployments of Linux (particularly those that use LVM) experience a one-time connection attempt error immediately after updating from a headend to 4.9.01xxx or later. Linux users running AnyConnect 4.8 (and later) and connecting to a headend to perform an auto update (web-deploy) may receive this error: "The secure gateway has rejected the connection attempt. A new connection attempt to the same or another secure gateway is needed, which requires re-authentication." To successfully connect, you can manually initiate another VPN connection after AnyConnect upgrade. After an initial upgrade to 4.9.01xxx or later, you will no longer hit this issue.

The Network Access Manager made a revision to write wireless LAN profiles to disk rather than just using temporary profiles in memory. Microsoft requested this change to address an OS bug, but it resulted in a crash of the Wireless LAN Data Usage window and eventual intermittent wireless connectivity issues. To prevent these issues, we reverted the Network Access Manager to using the original temporary WLAN profiles in memory. The Network Access Manager removes most of the wireless LAN profiles on disk when upgrading to version 4.8MR2 or later. Some hard profiles cannot be removed by the OS WLAN service when directed, but any remaining interfere with the ability for the Network Access Manager to connect to wireless networks. Follow these steps if you experience problems connecting to a wireless network after an upgrade from 4.7MR4 to 4.8MR2:

This removes leftover profiles from previous versions ( AnyConnect 4.7MR4 to 4.8MR2). Alternatively, you can look for profiles with AC appended to the name and delete them from the native supplicant.

macOS 11 fixed an issue seen in AnyConnect version 4.8.03036 (and later) related to the nslookup command, namely nslookup not sending DNS queries through the VPN tunnel with split-include tunneling configuration. The issue initiated in AnyConnect 4.8.03036 when that version included a fix for defect CSCvo18938. The Apple-suggested changes for that defect ended up revealing another OS issue, causing the nslookup problematic behavior.

As a workaround for macOS 10.x, you can pass the VPN DNS server as a parameter to nslookup: nslookup [name] [ip_dnsServer_vpn] .

(CSCvu71024) AnyConnect authentication may fail if the Secure Firewall ASA headend or SAML provider uses certificates signed by the AddTrust root (or one of the intermediaries), because they expired in May 2020. The expired certificate causes AnyConnect to fail and presents as a server certificate validation error, until operating systems make the required updates to accommodate the May 2020 expiration.

Windows DNS Client optimizations present in Windows 8 and above may result in failure to resolve certain domain names when split DNS is enabled. The workaround is to disable such optimizations by updating the following registry keys:

Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters

Value:DisableParallelAandAAAA

Data: 1

Key: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\DNSClient

Value: DisableSmartNameResolution

Data: 1

The macOS 10.15 operating system does not support 32-bit binaries. Additionally, Apple verifies that all software installed on 10.15 has been cryptographically notarized via digital signature. From AnyConnect 4.8 and later, operation on macOS 10.15 is supported with no 32-bit code.

Make note of these limitations:

HostScan packages earlier than 4.8.x will not function with macOS Catalina (10.15). End users who attempt to connect from macOS Catalina to Secure Firewall ASA headends running HostScan packages earlier than 4.8.x will not be able to successfully complete VPN connections, receiving a posture assessment failed message.

AnyConnect 4.10.x clients on macOS Big Sur (11.x) must use HostScan 4.9.04045 or later.

To enable successful VPN connections for HostScan users, all DAP and HostScan policies must be HostScan 4.8.00175 (or later) compatible. Refer to AnyConnect HostScan Migration 4.3.x to 4.6.x and Later for additional information related to policy migration from HostScan 4.3.x to 4.8.x.

As a workaround to restore VPN connectivity, administrators of systems with HostScan packages on their Secure Firewall ASA headends may disable HostScan . If disabled, all HostScan posture functionality, and DAP policies that depend on endpoint information, will be unavailable.

The associated field notice can be found here: https://www.cisco.com/c/en/us/support/docs/field-notices/704/fn70445.html .

macOS 10.15 (and later) requires that applications obtain user permissions for access to Desktop, Documents, Downloads, and Network Volume folders. To grant this access, you may see popups during an initial launch of HostScan , System Scan (when ISE posture is enabled on the network), or DART (when ISE posture or AnyConnect is installed). ISE posture and HostScan use OPSWAT for posture assessment on endpoints, and the posture checks access these folders based on the product and policies configured.

At these popups, you must click OK to have access to these folders and to continue with the posture flow. If you click Don't Allow , the endpoint may not remain compliant, and the posture assessment and remediation may fail without access to these folders.

To Remedy a Don't Allow Selection

signtool.exe verify /v /all/debug/pa<file to verify> 

The Firefox certificate store on macOS is stored with permissions that allow any user to alter the contents of the store, which allows unauthorized users or processes to add an illegitimate CA into the trusted root store. AnyConnect no longer utilizes the Firefox store for either server validation or client certificates.

If necessary, instruct your users how to export your AnyConnect certificates from their Firefox certificate stores, and how to import them into the macOS keychain. The following steps are an example of what you may want to tell your AnyConnect users.

Your AnyConnect Certificate(s) will most likely be located under the Authorities category. Verify with your Certificate Administrator, as they may be located under a different category (Your Certificates or Servers).

In the Format pull down menu, select X.509 Certificate (DER) . Add the .der extension to the certificate name, if required.

If more than one AnyConnect Certificate and/or a Private Key is used/required, repeat the above process for each Certificate).

In the Destination Keychain:, select the desired Keychain. The login Keychain that is used for this example may not be the one used at your company. Ask your Certificate Administrator to which Keychain your certificate(s) should be imported.

In the Destination Keychain:, select the desired Keychain. The login Keychain that is used for this example may not be the one used at your company. Ask your Certificate Administrator to which keychain your certificate(s) should be imported.

(CSCue04930) HostScan does not function when the SSLv3 options SSLv3 only or Negotiate SSL V3 are chosen in ASDM (Configuration > Remote Access VPN > Advanced > SSL Settings > The SSL version for the security appliance to negotiate as a server). A warning message displays in ASDM to alert the administrator.

There is an issue with Weblaunch with Safari. 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.

Automatic upgrades of AnyConnect software via WebLaunch will work with limited user accounts as long as there are no changes required for the ActiveX control.

Occasionally, the control will change due to either a security fix or the addition of new functionality.

Should the control require an upgrade when invoked from a limited user account, the administrator must deploy the control using the AnyConnect pre-installer, SMS, GPO or other administrative deployment methodology.

Java 7 can cause problems with AnyConnect and HostScan . A description of the issues and workarounds is provided in the Troubleshooting Technote Java 7 Issues with AnyConnect, CSD/HostScan, and WebVPN - Troubleshooting Guide , which is in Cisco documentation under Security > Cisco HostScan .

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 AnyConnect 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.

Network connectivity provided by Bluetooth or USB tethered mobile phones or mobile data devices are not specifically qualified by Cisco and should be verified with AnyConnect before deployment.

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.

AnyConnect 3.0 or later used with Secure Firewall ASA 8.4(1) or later supports UTF-8 characters in passwords sent using RADIUS/MSCHAP and LDAP protocols.

When Auto Update is disabled for a client running AnyConnect , the Secure Firewall ASA must have the same version of AnyConnect 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 Secure Firewall ASA, or upgrade the client to the new version by enabling Auto Update.

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.

The Intel wireless network interface card driver, version 12.4.4.5, 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.

Applications like antivirus, antimalware, and Intrusion Prevention System (IPS) can misinterpret the behavior of AnyConnect Secure Mobility Client applications as malicious. You can configure exceptions to avoid such misinterpretation. After installing the AnyConnect modules or packages, configure your antivirus software to allow the AnyConnect Installation folder or make security exceptions for the AnyConnect applications.

The common directories to exclude are listed below, although the list may not be complete:

Antivirus applications can misinterpret the behavior of some of the applications included in the posture module and the HostScan package as malicious. Before installing the posture module or HostScan package, configure your antivirus software to allow or make security exceptions for these HostScan applications:

cscan.exe

ciscod.exe

cstub.exe

IKEv2 does not support the public-side proxy. If you need support for that feature, use SSL. Private-side proxies are supported by both IKEv2 and SSL as dictated by the configuration sent from the secure gateway. IKEv2 applies the proxy configuration sent from the gateway, and subsequent HTTP traffic is subject to that proxy configuration.

AnyConnect sometimes receives and drops packet fragments with some routers, resulting in a failure of some web traffic to pass.

To avoid this, lower the value of the MTU. We recommend 1200. The following example shows how to do this using CLI:

hostname# config t
hostname(config)# group-policy DfltGrpPolicy attributes
hostname(config-group-policy)# webvpn
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 > AnyConnect Client .

If Dead Peer Detection (DPD) is enabled for DTLS, the client automatically determines the path MTU. If you previously reduced the MTU using the Secure Firewall 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 Secure Firewall ASA to restrict the MTU as before.

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 Group Policy Objects (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. GPOs pertaining to wireless networks are not supported.

To use Network Access Manager, you may need to adjust the FreeRADIUS configuration. Any ECDH related ciphers are disabled by default to prevent vulnerability. In /etc/raddb/eap.conf, change the cipher_list value.

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.

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.

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 primary or backup browser.

Enter regedit in the Search Programs and Files text box.

Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Browser\Parameters\

Double-click MaintainServerList .

The Edit String window opens.

Enter No .

Click OK .

Close the Registry Editor window.

The 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.

Caution

Disabling server certificate revocation checking in Internet Explorer can have severe security ramifications for other uses of the OS.

If you try to search for messages in the localization file, they can span more than one line, as shown in the example below:

msgid ""
"The service provider in your current location is restricting access to the "
"Secure Gateway. "
                     
When AnyConnect for macOS attempts to create an SSL connection to a gateway running IOS, or when AnyConnect attempts to create an IPsec connection to a Secure Firewall 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 macOS command line: 
                     
sudo ifconfig utun0 mtu
                     
On Windows computers, users with limited or standard privileges may
                        				sometimes have write access to their program data folders. These privileges could
                        				allow them to delete the AnyConnect profile and thereby circumvent the Always-On feature. To prevent this, configure
                        				the computer to restrict access to the C:\ProgramData folder,
                        				or at least the Cisco sub-folder. 
                     
Using the Windows 7 or later, the 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 the Secure Firewall ASA to accept TLSv1 or TLSv1.2 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.
                     
AnyConnect cannot establish a connection with the following Secure Firewall ASA settings for “ssl server-version”:
                     
ssl server-version sslv3
                     
ssl server-version sslv3-only
                     
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.
                     
You may experience long reconnects on Windows if IPv6 is enabled and
                        				auto-discovery of proxy setting is either enabled in Internet Explorer or not
                        				supported by the current network environment. As a workaround, you can disconnect
                        				any physical network adapters not used for VPN connection or disable proxy
                        				auto-discovery in IE, if proxy auto-discovery is not supported by the current
                        				network environment. 
                     
AnyConnect Secure Mobility Client includes an Application Programming Interface (API) for those 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 AnyConnect. 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: [email protected]. 
                  
The Cisco Bug Search Tool has detailed information about the following open and resolved caveats in this release. A Cisco account is required to access
                     the Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
The Cisco Bug Search Tool has detailed information about the following open and resolved caveats in this release. A Cisco account is required to access
                     the Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
The Cisco Bug Search Tool has detailed information about the following open and resolved caveats in this release. A Cisco account is required to access
                     the Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
The Cisco Bug Search Tool has detailed information about the following open and resolved caveats in this release. A Cisco account is required to access
                     the Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
The Cisco Bug Search Tool has detailed information about the following open and resolved caveats in this release. A Cisco account is required to access
                     the Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
The Cisco Bug Search Tool has detailed information about the following open and resolved caveats in this release. A Cisco account is required to access
                     the Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
The Cisco Bug Search Tool has detailed information about the following open and resolved caveats in this release. A Cisco account is required to access
                     the Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
The Cisco Bug Search Tool has detailed information about the following open and resolved caveats in this release. A Cisco account is required to access
                     the Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
The Cisco Bug Search Tool has detailed information about the following open and resolved caveats in this release. A Cisco account is required to access
                     the Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
The Cisco Bug Search Tool has detailed information about the following
                     open and resolved caveats in this release. A Cisco account is required to access the
                     Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
The Cisco Bug Search Tool has detailed information about the following
                     open and resolved caveats in this release. A Cisco account is required to access the
                     Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
The Cisco Bug Search Tool has detailed information about the
                     following open and resolved caveats in this release. A Cisco account is required to
                     access the Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
The Cisco Bug Search Tool has detailed information about the following
                     open and resolved caveats in this release. A Cisco account is required to access the
                     Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
The Cisco Bug Search Tool has detailed information about the following
                     open and resolved caveats in this release. A Cisco account is required to access the
                     Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
The Cisco Bug Search Tool has detailed information about the following
                     open and resolved caveats in this release. A Cisco account is required to access the
                     Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
The Cisco Bug Seach Tool has detailed information about the following
                     open and resolved caveats in this release. A Cisco account is required to access the
                     Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
Caveats describe unexpected behavior or defects in Cisco software releases.
                  
The Cisco Bug Search Tool has detailed information about the following open and resolved caveats in this release. A Cisco account is required to access
                     the Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
Caveats describe unexpected behavior or defects in Cisco software releases.
                  
The Cisco Bug Search Tool has detailed information about the following open and resolved caveats in this release. A Cisco account is required to access
                     the Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
Caveats describe unexpected behavior or defects in Cisco software releases.
                  
The Cisco Bug Search Tool has detailed information about the following open and resolved caveats in this release. A Cisco account is required to access
                     the Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
Caveats describe unexpected behavior or defects in Cisco software releases.
                  
The Cisco Bug Search Tool has detailed information about the following open and resolved caveats in this release. A Cisco account is required to access
                     the Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
Caveats describe unexpected behavior or defects in Cisco software releases.
                  
The Cisco Bug Search Tool has detailed information about the following open and resolved caveats in this release. A Cisco account is required to access
                     the Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
Caveats describe unexpected behavior or defects in Cisco software releases.
                  
The Cisco Bug Search Tool has detailed information about the following open and resolved caveats in this release. A Cisco account is required to access
                     the Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
Caveats describe unexpected behavior or defects in Cisco software releases.
                  
The Cisco Bug Search Tool has detailed information about the following
                     open and resolved caveats in this release. A Cisco account is required to access the
                     Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
Caveats describe unexpected behavior or defects in Cisco software releases.
                  
The Cisco Bug Search Tool has detailed information about the following
                     open and resolved caveats in this release. A Cisco account is required to access the
                     Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
Caveats describe unexpected behavior or defects in Cisco software releases.
                  
The Cisco Bug Search Tool has detailed information about the following
                     open and resolved caveats in this release. A Cisco account is required to access the
                     Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
Caveats describe unexpected behavior or defects in Cisco software releases.
                  
The Cisco Bug Search Tool has detailed information about the following
                     open and resolved caveats in this release. A Cisco account is required to access the
                     Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
Caveats describe unexpected behavior or defects in Cisco software releases.
                  
The Cisco Bug Search Tool has detailed information about the following
                     open and resolved caveats in this release. A Cisco account is required to access the
                     Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
Caveats describe unexpected behavior or defects in Cisco software releases.
                  
The Cisco Bug Search Tool has detailed information about the following
                     open and resolved caveats in this release. A Cisco account is required to access the
                     Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
Caveats describe unexpected behavior or defects in Cisco software releases.
                  
The Cisco Bug Search Tool has detailed information about the following
                     open and resolved caveats in this release. A Cisco account is required to access the
                     Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
Caveats describe unexpected behavior or defects in Cisco software releases.
                  
The Cisco Bug Search Tool has detailed information about the following
                     open and resolved caveats in this release. A Cisco account is required to access the
                     Bug Search Tool. If you do not have one, register at https://Cisco.com.
                  
Caveats describe unexpected behavior or defects in Cisco software releases.
                  
The Cisco Bug Search Tool has detailed information about the following
                     open and resolved caveats in this release. A Cisco account is required to access the
                     Bug Search Tool. If you do not have one, register at https://Cisco.com.