How To Download The Local Argos Client: A Complete Enterprise Installation Guide

Downloading and executing the local Argos desktop client requires installing the Evisions Application Launcher on your local workstation via your institution's secure Multi-Application Platform Services (MAPS) web portal. Once configured, this local launcher handles the custom URL protocols necessary to execute the native, full-feature Windows client interface securely without relying on deprecated Java applets. This operational guide provides the exact deployment procedures, network requirements, and workstation configurations necessary for successful enterprise installation.

Pre-Installation System Requirements & MAPS Compatibility Checklist

Before attempting to initialize the download, verify that your workstation meets the baseline hardware and software specifications defined by Evisions. The local Argos client (often referred to as the Argos PC Client) executes as a native Windows application triggered via a custom URI handler. Users working on non-Windows operating systems must employ virtualization environments to interface with the local desktop build.

Hardware, Software, and Network Prerequisites

• Operating System: Windows 10, Windows 11, or Windows Server 2019/2022. macOS and Linux environments require a compatibility layer such as Parallels Desktop, VMware Fusion, or a configured Virtual Desktop Infrastructure (VDI) running Windows.
• Administrative Permissions: Local machine administrator rights are mandatory for the initial installation of the MSI service installer, though subsequent application updates often run within user-profile scopes.
• Target Network Access: Workstations must have unrestricted TCP port access to the primary institution MAPS server, typically communicating over port 80 for standard HTTP or, ideally, port 443 for secured SSL/TLS connections.
• Web Browser Compatibility: Google Chrome, Microsoft Edge, or Mozilla Firefox with protocol handler permissions enabled. Legacy browsers relying on ActiveX are fully deprecated.
• Deployment Duration: Approximately 5 to 10 minutes from initialization to connection validation.
• Associated Licensing Costs: No individual user licensing fee is required; access is fully provisioned under your institution’s enterprise Evisions license agreement.

Step-by-Step Evisions Application Launcher & Argos Client Deployment

The transition away from browser-based NPAPI plugins and Java runtimes means the modern local Argos client depends entirely on the Evisions Application Launcher (EAL). The launcher acts as a local bridge between your web browser and the MAPS server environment. Follow this sequential workflow to download, register, and launch the tool on your system.

Step 1: Access the Institutional MAPS Landing Page

Obtain the unique web address of your university's or enterprise's MAPS server. This URL is typically distributed by your internal Information Technology help desk or database administration team and adheres to a format such as maps.yourinstitution.edu or banner-maps.university.edu/maps. Enter this URL into your web browser's address bar. Do not attempt to use external public search engines to find this portal, as it resides on private or intranet-exposed servers.

Step 2: Download the Evisions Application Launcher Installer

Once the MAPS web page loads, look for a section or button labeled "Argos" or "Launch Argos." If this is your first time accessing the software on this physical machine, click the dedicated link text that reads "Download Evisions Application Launcher" or "Install the Launcher." The web server will automatically package and deliver an MSI installation file, typically named EVLauncherFree.msi or Evisions_Application_Launcher.msi, directly to your system's download directory.

Warning: Do not close the MAPS browser window during this process. The active browser session retains the security tokens and system identifiers required to authorize the local client handshake once the launcher installation completes.

Step 3: Execute the MSI Installation Package

Locate the downloaded installation file in your system directory. Right-click the MSI file and choose "Run as administrator" to prevent permission-related file system blocks. Step through the installation wizard by accepting the default destination directories. The default installation path is located within the AppData local directory structure of the current user, specifically C:\Users\Username\AppData\Local\Evisions\Application Launcher. Click "Finish" once the wizard reports a successful installation sequence.

Step 4: Authorize Browser Protocol Association

Return to your web browser window hosting the MAPS landing page and click the "Launch Argos" button. Your web browser will detect the installation of the new protocol handler and prompt you with a security confirmation dialogue box. This dialogue box will ask for permission to open the Evisions Application Launcher protocol handler. Check the box labeled "Always allow this site to open these types of links in the associated app" and then click the "Open" or "Allow" button.

Pro-Tip: If your browser does not trigger this pop-up window or continues to redirect you to the download page, restart your web browser completely. This force-reloads the newly registered system registry keys that associate the evlauncher:// protocol with the local executable.

Step 5: Establish the Local Client Cache and Log In

After authorizing the protocol handler, the Evisions Application Launcher will communicate with the host MAPS server to download the latest cached version of the local Argos desktop client files (.exe components). This background step ensures that your local client always remains synchronized with the exact version deployed on the institution's server infrastructure. Once the synchronization process completes, the Argos login prompt will appear on your desktop screen. Input your active database directory credentials, enterprise single sign-on (SSO) credentials, or MAPS-specific username and password to access your dashboards.

Argos Client Architecture & System Compatibility Matrix

The performance and functionality of the local Argos client differ significantly from the web-based version (Argos Web Viewer) and are highly contingent on local environment settings. The following matrix contrasts the operational metrics and resource dependencies of these interfaces to aid administrators in making optimal system decisions.

Resolving Common Argos Client Connection & Launcher Failures

Deploying enterprise database connections to localized environments introduces several points of potential failure, ranging from web browser isolation policies to network routing restrictions. Use the troubleshooting matrix below to identify, isolate, and repair common operational blocks.

The Browser Continually Demands to Install the Launcher

This loop occurs when the local browser profile fails to recognize the protocol association registered during the MSI installation, or when secure corporate group policies block custom URI registrations.

• Root Cause: Corrupted local registry entries for the evlauncher URI scheme, or third-party browser extensions actively stripping custom protocols from landing pages.
• Actionable Fix: Open your Windows Registry Editor by typing regedit in the Start menu. Verify that the hive HKEY_CLASSES_ROOT\evlauncher exists. If it is missing, run the MSI installer again with full local administrative privileges. Additionally, disable all browser ad-blockers and privacy extensions for your institution's domain, then clear your browser's cached site data before clicking the launch button.

Execution Terminates with a "MAPS Connection Timeout" Error

This error occurs when the local launcher initiates the handshake but cannot establish direct path communication with the target server IP or domain name.

• Root Cause: Active local Windows Defender Firewall rules, corporate perimeter firewall filtering, or an unestablished VPN tunnel to the institution's private intranet.
• Actionable Fix: Confirm that you are securely connected to your institution’s Virtual Private Network (VPN) if you are working from an off-campus or remote location. Open your Windows Advanced Firewall settings and construct an outbound traffic allowance rule specifically for port 443 and port 80 for the executable located at: C:\Users\YourUsername\AppData\Local\Evisions\Application Launcher\EVLauncher.exe.

Local Application Freezes or Displays a White Screen on Startup

The local client loads but crashes before displaying the primary institutional login prompt or navigation dashboard.

• Root Cause: A mismatch or corruption in the local application cached files downloaded from the MAPS environment during initialization.
• Actionable Fix: Close all active instances of the web browser and the launcher app. Navigate to your local machine directory at *C:\Users\YourUsername\AppData\Local\Evisions\Argos*. Delete the entire contents of this folder, which houses temporary cached configuration profiles. Relaunch the MAPS web page and click "Launch Argos" to trigger a clean, uncorrupted rebuild of the local application binaries.

Frequently Asked Questions

Can I run the local Argos client on a Mac?

The local Argos desktop client is a 32-bit/64-bit native Windows executable that cannot run directly on macOS. To run the full local desktop client on a Mac, you must utilize a virtualization tool such as Parallels Desktop to run a Windows virtual machine, or use the HTML5-based Argos Web Viewer if you do not require report design privileges.

What is the difference between the Argos Web Viewer and the local Argos client?

The local Argos client is a desktop design suite used by institutional DataBlock designers and report authors to write SQL queries, construct data schemas, and build user dashboards. The Argos Web Viewer is a responsive browser interface built for end-users to consume existing reports, input parameters, and extract CSV/PDF outputs without installing any software.

Why does Argos require the Evisions Application Launcher?

Modern web browsers have phased out legacy browser plugin interfaces such as NPAPI, ActiveX, and Java applets due to security concerns. The Evisions Application Launcher bridges this gap by acting as a secure local background service that launches the native desktop app directly from browser-triggered web links.

How do I update the local Argos client?

The local client updates automatically when launched. Every time you click "Launch Argos" on your institutional landing page, the launcher compares your local client files with the files stored on the MAPS server, automatically downloading any hotfixes or updates without requiring user or administrator intervention.

What administrative permissions are required to install the local Argos client?

While the local client itself runs entirely within the user's local profile sandbox, installing the Evisions Application Launcher MSI file requires temporary local administrator rights to write registry keys and register the custom URL protocol handler within the Windows operating system.

Upgrade Your Institutional Reporting Workflows

If you are looking to scale your database capabilities and maximize analytical outputs, contact your university database administrator to secure access to the advanced local Argos design suite today. Equipping your research teams with native desktop analytical permissions streamlines institutional decision-making and ensures data accuracy at every organizational tier.