For additional information, refer to the AnyConnect configuration guide.
Download the VPN installer from MIT's download page, Cisco AnyConnect VPN Client for Windows. Cisco AnyConnect - Empower your employees to work from anywhere, on company laptops or personal mobile devices, at any time. AnyConnect simplifies secure endpoint access and provides the security necessary to help keep your organization safe and protected.
Client Download
Unlike the ASA, the MX does not support web deploy or web launch, a feature that allows end users to access a web page on the AnyConnect server to download the AnyConnect client. With the MX, there are download links to the client software on the AnyConnect settings page on the dashboard, however, the download links are only available to the Meraki dashboard admin and not the end user. We do not recommend sharing the down link with users as the link expires after every five minutes of loading the AnyConnect settings page.
We recommend downloading the AnyConnect client directly from Cisco.com as there may be an updated version in the Cisco repository. Refer to the doc for the AnyConnect clientrelease notes. We also recommend using either Meraki Systems Manager, an equivalent MDM solution, or Active Directory to seamlessly push the AnyConnect software client to the end user's device.
AnyConnect requires a VPN client to be installed on a client device. The AnyConnect client for Windows, MacOS, and Linux are available on the Client Connection section of the AnyConnect configuration page on the dashboard and can be downloaded by a Meraki dashboard administrator. Please note, the download links on the Meraki dashboard expire after five minutes. The AnyConnect client for mobile devices can be downloaded via the respective mobile stores. You can also download other versions (must be version 4.8 or higher) of the AnyConnect client from Cisco.com if you have an existing AnyConnect license. AnyConnect web deploy is not supported on the MX at this time.
- Installing the AnyConnect client
- You only need the VPN box checked. Once the client has been installed on the device, open the AnyConnect application and specify the hostname or IP address of the MX (AnyConnect server) you need to connect to.
AnyConnect Profiles
An AnyConnect profile is a crucial piece for ensuring easy configuration of the AnyConnect client software, once installed. The MX does not support the use of custom hostnames for certificates (e.g. vpn.xyz.com). The MX only supports use of the Meraki DDNS hostname for auto-enrollment and use on the MX. With the Meraki DDNS hostname (e.g. mx450-xyuhsygsvge.dynamic-m.com) not as simply as a custom hostname, the need for AnyConnect profiles cannot be overemphasized. Profiles can be used to create hostname aliases, thereby masking the Meraki DDNS with a friendly name for the end user.
Cisco AnyConnect client features are enabled in AnyConnect profiles. These profiles can contain configuration settings like server list, backup server list, authentication time out, etc., for client VPN functionality, in addition to other optional client modules like Network Access Manager, ISE posture, customer experience feedback, and web security. It is important to note that at this time, the Meraki MX does not support other optional client modules that require AnyConnect head-end support. For more details, see AnyConnect profiles.
When a profile is created, it needs to get pushed to the end user's device. There are three ways to do this.
1. Through the AnyConnect server (MX): If profiles are configured on the dashboard, the MX will push the configured profile to the user's device after successful authentication.
2. Through an MDM solution: Systems Manager, an equivalent MDM solution, or Active Directory can be used push files to specific destinations on the end user's device. Profiles can also be pushed to the following paths:
Windows
%ProgramData%CiscoCisco AnyConnect Secure Mobility ClientProfile
Mac OS X
/opt/cisco/anyconnect/profile
Cisco Anyconnect Vpn Software Download
Linux
/opt/cisco/anyconnect/profile
3. Manually: Profiles can also be preloaded manually to the same paths as listed above.
How to Create a Profile
Profiles can be created using the AnyConnect profile editor. The profile editor can be downloaded from the AnyConnect Settings page on dashboard or on cisco.com. Refer to this link for more details on AnyConnect profiles.
Using the profile editor: The profile editor can be downloaded from the AnyConnect Settings page on dashboard or on Cisco.com. The profile editor only runs on Windows operating systems. The screenshot below shows a configured server ton the Server List Entry option.
When configuration is complete, save the profile. It is recommended to use a unique file name to avoid profile overrides by other AnyConnect servers, then you can upload the file to the profile update section on the AnyConnect settings page.
Please note that only VPN profiles are supported on the MX at this time. This means you cannot push NVM, NAM, or Umbrella profiles via the MX.
- Select enable profiles, upload your xml file, and save your configuration
- After a user successfully authenticates, the configured profile gets pushed to the user's device automatically
- The result of the .xml can be seen below, after successful authentication to the AnyConnect server; this gives users the ease of selecting VPN servers on the AnyConnect client
The Meraki DDNS hostname is not easy to remember, therefore end users are not expected to use it directly. Profiles should be used to make connecting to the AnyConnect server easy for end users.
Virtual Private Network (VPN) is a remote access technology that creates a private encrypted connection over the Internet between a single host and Stanford's private network, SUNet.
Stanford's VPN allows you to connect to Stanford's network as if you were on campus, making access to restricted services possible. There are two types of VPN available:
- Default Stanford (split-tunnel) allows access to anything at stanford.edu via the VPN connection but non-Stanford traffic flows normally on an unencrypted internet connection.
- Full Traffic (non-split-tunnel) encrypts all internet traffic from your computer but may inadvertently block you from using resources on your local network, such as a networked printer at home.
Features
- When using VPN, your off-campus computer is dynamically assigned a Stanford IP address to connect back to Stanford's network.
- A Stanford IP address allows you access to Stanford's computing resources and certain campus services (e.g., departmental file and print servers).
Designed for
Faculty, staff, and students
Requirements
- An active SUNet ID
- Windows 8 SP1 and later
- Mac OS X 10.9 and later*
- iOS 10 or later
- Android OS 6.0 or later
*Note for Mac High Sierra (10.13): When you log in to the Cisco AnyConnect VPN, you may be prompted to upgrade to a new version of software. If you choose to upgrade, you'll see a System Extension Blocked alert directing you to go to System Preferences > Security & Privacy to allow the extension. The approval field is only present in the Security & Privacy preferences pane for 30 minutes after the alert. If the extension is not approved with in 30 minutes the software will not function correctly.
Data security
Get started
Select your operating system to see the VPN configuration instructions for your device:
Learn more
Many commonly used Stanford applications and services are available directly from the Internet without the use of VPN. While VPN does encrypt your data in transit, nearly all of the web-based applications you access already default to secure https communication, and are therefore already encrypted.

Examples of commonly used Stanford services which do not require VPN:
- Office 365
- Zoom
- WebEx
- Axess
- Oracle Financials
- Cisco Jabber
- Slack
- Google Drive
- G Suite
University IT (UIT) recommends that you donot enable your VPN connection unless the server or application that you are trying to access requires a VPN connection. Using VPN adds unnecessary additional overhead, which may degrade the user experience while connected, especially for video conferencing, streaming services, or applications.
Many secure servers within the Stanford University network do require the use of VPN. There is no published list of these servers, but it is easy to quickly determine whether the server/system you are attempting to connect to requires VPN with this simple test: try performing daily duties without the VPN enabled. If you cannot access a service, enable the VPN and try again.
If you do require a VPN connection, UIT recommends that you use the split-tunnel profile rather than full-tunnel. The split-tunnel profile enables the Internet-bound traffic to flow directly outbound via your home ISP, without first going to the Stanford VPN, and then route to the Internet. This also ensures better performance overall. Please remember that when using the full-tunnel profile, all traffic from your system routes first through the Stanford VPN and then out to the Internet.
Stanford University Libraries (SUL) updated the method by which authorized community members access restricted journals from off-campus.
Rather than using Stanford's VPN (Virtual Private Network), SUL wants community members to use its EZProxy service: http://library.stanford.edu/using/connect-campus/ezproxy-alternative-campus-access
See also
Cisco Anyconnect 4 9 X64 Free Download
- Instructions for using Remote Desktop to work remotely
- Work Anywhere website for more resources for telecommuting and remote work
