Silent install of EAA Client

Perform a silent install of the EAA Client on machines using software deployment solutions like KACE, JAMF, and Microsoft System Center Configuration Manager (SCCM).

The Enterprise Application Access (EAA) administrator might want to install EAA Client in the background on many machines using software deployment solutions like KACE, JAMF, and SCCM. It is done by executing the installation in command line mode with some specific arguments.
Note: Command line installation for every software differs considerably. You can use this as a reference and update as required to suit your environment.

To perform a silent install you need to download the relevant files based on whether you want to deploy on 32 bit (Windows platform) or a 64 bit (Windows or Mac platform) machines.

If an existing version of the EAA Client is already installed (either a greater or lower version), the silent install first removes the existing installation before installing the new version, regardless of whether you are upgrading or downgrading from your current version.

Silent install of EAA Client in Windows systems

  1. Download the latest EAA Client packages for Windows from Akamai download links:
    https://eaaclientdownloads.akamai-access.com/eaaclientdistro/EAAClient-x64.exe
    https://eaaclientdownloads.akamai-access.com/eaaclientdistro/EAAClient-i386.exe
  2. Enter the command to start the silent installation with the IdP portal URL:
    <EAA Client package directory>\EAAClient-x64.exe" --mode unattended --unattendedmodeui none --url <idp_portal_url> --autostart no
    For example, to do a silent install for EAA Client for Windows 64 bit machine with an IdP_portal_URL of https://myidpportal.mycompany.com:
    ".\EAAClient-x64.exe" --mode unattended
            --unattendedmodeui none --url https://myidpportal.mycompany.com --autostart no
    Note: The --url option is optional. Use this option when you want EAA Client to authenticate with a pre-configured IdP in the URL location.
    Note: The default value for --autostart is yes. This enables EAA Client to start immediately after successful installation. When doing silent install with SYSTEM user, it is recommended to use the no option. This prevents deployment solutions without administrative privileges to automatically start the EAA Client. Instead, it allows the end users to manually start the EAA Client on their machines.
  3. The installation starts and runs in the background. Nothing is visible on the screen. It takes a few minutes, and is longer if there is an existing client. After the installation is finished, the IdP.ini file in the EAA Client installation folder of the machine is updated with IdP_portal_URL giving in the --url parameter of the silent installation command. When EAA Client starts, EAA Client status is in Not Configured state. The EAA Client automatically opens the browser tab and launches the IdP_portal_URL. After users authenticate, the configuration process automatically finishes. A web page opens to confirm successful configuration. Then, if you open the EAA Client, the EAA Client status will be in Authenticated state.

What you should see

The installation should finish in the background.

Silent install of EAA Client in Mac systems

  1. Download the latest EAA Client packages for MacOS from Akamai download links:
    https://eaaclientdownloads.akamai-access.com/eaaclientdistro/EAAClient.app.zip
  2. Unzip the EAAClient*.zip file with the command:

    tar -xvf EAAClient.app.zip

    A new Contents folder is created in the path the tar command was invoked from.

  3. Enter this command to start silent installation with the IdP portal URL:
    sudo ./Contents/MacOS/installbuilder.sh --mode unattended
              --unattendedmodeui none --url <idp_portal_url> --autostart no
    For example, if the IdP_portal_URL of https://myidpportal.mycompany.com:
    sudo ./Contents/MacOS/installbuilder.sh
              -mode unattended --unattendedmodeui none --url
            https://myidpportal.mycompany.com --autostart no
    Note: The --url option is optional. Use this option when you want EAA Client to authenticate with a pre-configured IdP in the URL location.
    Note: The default value for --autostart is yes. This enables EAA Client to start immediately after successful installation. When doing silent install with SYSTEM user, it is recommended to use the no option. This prevents deployment solutions without administrative privileges to automatically start the EAA Client. Instead, it allows the end users to manually start the EAA Client on their machines.
  4. The installation starts and runs in the background. Nothing is visible on the screen. It takes a few minutes, and is longer if there is an existing client. After the installation is finished, the IdP.ini file in the EAA Client installation folder of the machine is updated with IdP_portal_URL giving in the --url parameter of the silent installation command. When EAA Client starts, EAA Client status is in Not Configured state. The EAA Client automatically opens the browser tab and launches the IdP_portal_URL. After the users authenticate, the configuration process automatically finishes. The EAA Client automatically configures in the background. A web page opens to confirm successful configuration. Then, if you open the EAA Client, the EAA Client status will be in Authenticated state.

What you should see

The installation should finish in the background.