Ivanti Secure Access Client va50 ko40 — historically known as Pulse Secure VPN — is an enterprise remote access client that creates an encrypted tunnel between your device and a company gateway. It supports certificate and multifactor authentication, device posture checks, split tunneling, and per‑app rules to help organizations adopt Zero Trust principles without making connectivity painful for end users. This official guide focuses on everyday tasks: how to get connected reliably, what to expect from the client on Windows, macOS, Linux, iOS, and Android, and how to troubleshoot the most common issues without admin rights.
Before installing the client, confirm the OS version your company supports and whether you need admin privileges. On managed Windows and macOS endpoints, the agent is often deployed by MDM or software distribution; otherwise you will receive an installer and server URL from IT. Close other VPN tools first, then run the installer and restart if prompted. When the app opens, add a new connection by pasting your gateway URL (sometimes ending in /dana-na/ on legacy Pulse Secure gateways). For strong security your admin may require a device certificate, FIDO2 security key, or a one‑time password from an authenticator app. Keep your system clock accurate — SSO and certificates fail if time drifts.
Click the saved connection and sign in with the identity method your employer provides. The client validates the gateway certificate, checks device posture (for example disk encryption and antivirus), then boots the VPN tunnel. If you see a consent screen, it describes what posture data is evaluated — read it once so you understand the privacy scope. To improve throughput, prefer wired or 5 GHz Wi‑Fi and pause heavy sync operations while connecting. If you need to access only specific apps, ask IT for per‑app VPN rules; this reduces bandwidth and battery drain while keeping corporate routes secured.
If the client cycles between “Connecting” and “Reconnecting,” check the gateway URL and your system time. Authentication failures after a password change usually require you to re‑enter saved credentials or approve a new MFA prompt. DNS problems present as “site can’t be reached” while the VPN looks connected — try flushing DNS or toggling flight mode for ten seconds. If your Pulse Secure‑era profile migrated, remove and recreate it to clear legacy settings. Persistent errors belong in a support ticket — include OS version, client build, gateway name, and a timestamp to help admins correlate logs.
Remote access extends your internal network to the edges, so treat the client like a company badge. Keep the OS patched, enable full‑disk encryption, and protect your login factors. Don’t share configuration files, and never bypass posture checks on a personal device. When traveling, avoid untrusted USB chargers and public PCs; use your company’s recommended authenticator only. For teams, document emergency access paths (out‑of‑band gateway, break‑glass accounts) and test them quarterly. If you suspect compromise, disconnect the VPN and contact security immediately so they can rotate credentials and review logs.
