Примечания к выпуску для Cisco Cisco AnyConnect Secure Mobility Client v4.x
• Upgrading from Windows XP to any later Windows release 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.
or via WebLaunch.
• 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+.
• ASDM version 7.02 or higher is required when using Windows 8 or 8.1.
Windows Limitations
• 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.
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
To work around this problem, uninstall Wireshark or disable the WinPcap service, reboot your Windows 8 computer, and
attempt the AnyConnect connection again.
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.
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.
• HP Protect tools do not work with AnyConnect on Windows 8.x.
• Windows 2008 is not supported; however, we do not prevent the installation of AnyConnect on this OS. Also, Windows Server
2008 R2 requires the optional SysWow64 component
• 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.
association timer so that the driver can complete a network scan and populate the scanlist.
Windows Guidelines
• Verify that the driver on the client system is supported by Windows 7 or 8. 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. 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 or 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.
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 or 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.
11