AnyConnect setup guides
Use these step‑by‑step instructions to configure Secure Client VPN on each platform. Each guide includes verification steps and rollback notes so you can recover quickly if something goes wrong.
Windows 10/11
- Install Secure Client VPN with the VPN module.
- Open the app and in the “VPN” field enter the gateway FQDN (e.g., vpn.company.com).
- Click Connect. If prompted, choose your group/tunnel. Complete primary auth and MFA.
- Verify: open ipconfig to confirm a new adapter and VPN IP; run route print to see injected routes; resolve an internal DNS name.
If the connection page opens in a browser (SAML), keep the browser window focused until the client reports “Connected”.
macOS 12 or later
- Install the .pkg. On first run, approve extensions in System Settings if required.
- Enter the VPN gateway FQDN and connect. Use your corporate identity provider to authenticate.
- Verify with ifconfig that a utun/tap interface appears; check the DNS search domains in Network settings.
Linux (Ubuntu)
- Install the AnyConnect packages for your distro.
- Launch the GUI or use CLI: /opt//secureclient/bin/vpn connect vpn.company.com.
- Authenticate and verify: ip a shows the tunnel interface; resolvectl status lists VPN DNS.
iOS / Android
- Install “ Secure Client VPN” from the app store.
- Add a connection, enter the gateway FQDN, save and connect.
- Approve MFA and verify access to internal apps.
Managing profiles and groups
Profiles define connection entries, backup servers, and restrictions like UI lock‑down and Always‑On. Importing a .xml profile saves time and prevents typos. Group selection maps to tunnel‑group and group‑policy on the headend; use descriptive group names so users can switch without tickets.
Verification and rollback
After changes, validate routing (full vs split), DNS suffix order, and reachability to core services such as identity, file shares, and intranet portals. If a change breaks connectivity, revert the profile and roll back the client upgrade for the impacted cohort while you triage logs.
Operational checklists
Before rollout
Back up current profiles, export headend config, and schedule a maintenance window. Notify users and publish a one‑page quick start.
After upgrade
Sample users from each business unit, test latency‑sensitive apps, and monitor session failure rate for 72 hours.
Periodic hygiene
Rotate certificates well before expiry, audit group membership, and prune unused ACLs and split‑tunnel entries.
Quick links: Guides · Download · Troubleshooting