Cisco Cisco AnyConnect Secure Mobility Client v3.x Release Notes
Release Notes for Cisco AnyConnect Secure Mobility Client, Release 3.1
Web-based installation May Fail on 64-bit Windows
6
Upgrading 3.1 MR11 AnyConnect Clients/Incompatibility Issues
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.
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.
Refer to CSCuv12386 for further information.
Upgrading 3.1 MR10 AnyConnect Clients/Incompatibility Update
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.
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:
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:
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.
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.
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.
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.
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.
Explorer\Main\TabProcGrowth is set to 0, Active X has problems during AnyConnect web deployment.
for more information.