### Install IBM Aspera Connect Per-User (Windows Command Prompt)

Source: https://www.ibm.com/docs/en/aspera-connect/4_topic=connect-silent-installation

This command installs IBM Aspera Connect for the current user. It requires administrator privileges to run the MSI installer and specifies the installation path and quiet mode. Ensure the correct path to the MSI installer is provided.

```batch
C:\Windows\System32\msiexec.exe /i C:\path\to\IBMAsperaConnect-ML-version.msi WIX_APP_FOLDER=WixPerUserFolder ALLUSERS=0 REBOOT=REALLYSUPPRESS /qn
```

--------------------------------

### Install IBM Aspera Connect (Windows Command Prompt)

Source: https://www.ibm.com/docs/en/aspera-connect/4.2_topic=connect-silent-installation

This command installs IBM Aspera Connect for the current user. It suppresses reboot prompts and installs to a per-user folder. Ensure you have the correct MSI file path.

```batch
C:\Windows\System32\msiexec.exe /i C:\path\to\ibm-aspera-connect-version_win64.msi WIX_APP_FOLDER=WixPerUserFolder ALLUSERS=0 REBOOT=REALLYSUPPRESS /qn
```

--------------------------------

### Manually Execute IBM Aspera Connect (Shell)

Source: https://www.ibm.com/docs/en/aspera-connect/3.10_topic=suc-installation

This command is used to manually start the IBM Aspera Connect application from the terminal. It assumes the default installation path. Ensure you have the necessary execute permissions.

```bash
$ ~/.aspera/connect/bin/asperaconnect
```

--------------------------------

### Silent System-wide Installation of IBM Aspera Connect (Windows)

Source: https://www.ibm.com/docs/en/aspera-connect/4_topic=connect-silent-installation

This command performs a silent, system-wide installation of IBM Aspera Connect. It requires administrative privileges and closes open browsers and existing Connect instances. The command uses msiexec to install the MSI package with specific properties for per-machine installation and suppressed reboot.

```batch
C:\Windows\System32\msiexec.exe /i C:\path\to\IBMAsperaConnect-ML-version.msi WIX_APP_FOLDER=WixPerMachineFolder ALLUSERS=1 REBOOT=REALLYSUPPRESS /qn
```

--------------------------------

### User Install Script for Firefox Extension (Bash)

Source: https://www.ibm.com/docs/en/aspera-connect/3.10_topic=a-deploying-connect-extensions-in-closed-environments-1

This Bash script facilitates the user installation of the Aspera Connect Firefox extension by copying the XPI file to the user's extension directory. Ensure the XPI_FILE variable points to the correct path.

```bash
#!/usr/bin/env bash
XPI_FILE=INSERT_XPI_PATH_HERE
EXT_ROOT="$HOME/Library/Application Support/Mozilla/Extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}"
mkdir -p "$EXT_ROOT"
cp $XPI_FILE "$EXT_ROOT"
```

--------------------------------

### Firefox: Manual Extension Deployment (XPI)

Source: https://www.ibm.com/docs/en/aspera-connect/3_topic=appendices-deploying-connect-extensions-in-closed-environments

Installs the IBM Aspera Connect add-on for Firefox by manually downloading the XPI file and installing it via the add-ons manager. This method is suitable for individual user installations.

```text
1. Download the Connect extension XPI file from Mozilla. To do so, right-click this link and select Save Link As: Connect extension for Mozilla
2. Open `about:addons`
3. From the menu, select Install Add-on From File.
```

--------------------------------

### Launch IBM Aspera Connect Application (Linux/macOS)

Source: https://www.ibm.com/docs/en/aspera-connect/3.10_topic=suc-basic-configuration

This command executes the IBM Aspera Connect application manually, typically used when the application is not running or needs to be started from the terminal. It assumes a standard installation path.

```shell
# ~/.aspera/connect/bin/asperaconnect &
```

--------------------------------

### Windows Silent Installation of IBM Aspera Connect

Source: https://www.ibm.com/docs/en/aspera-connect/4.2_topic=connect-silent-installation

Performs a system-wide silent installation of IBM Aspera Connect on Windows using msiexec. Ensure all browsers and older versions of Connect are closed before running. The command requires administrator privileges.

```batch
C:\Windows\System32\msiexec.exe /i C:\path\to\ibm-aspera-connect-version_win64.msi WIX_APP_FOLDER=WixPerMachineFolder ALLUSERS=1 REBOOT=REALLYSUPPRESS /qn
```

```batch
C:\Windows\System32\msiexec.exe /i C:\path\to\ibm-aspera-connect-version_win64.msi WIX_APP_FOLDER=WixPerMachineFolder ALLUSERS=1 SHELL_EXTENSION_REQUESTED=0 /qn
```

--------------------------------

### Machine Install Script for Firefox Extension (Bash)

Source: https://www.ibm.com/docs/en/aspera-connect/3.10_topic=a-deploying-connect-extensions-in-closed-environments-1

This Bash script is used for machine-wide installation of the Aspera Connect Firefox extension. It requires root privileges (sudo) and copies the XPI file to the system-wide extension directory. Update the XPI_FILE variable accordingly.

```bash
#!/usr/bin/env bash
XPI_FILE=INSERT_XPI_PATH_HERE
EXT_ROOT="/Library/Application Support/Mozilla/Extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}"
mkdir -p "$EXT_ROOT"
cp $XPI_FILE "$EXT_ROOT"
```

--------------------------------

### Install IBM Aspera Connect with Shell Extension Disabled (Windows Command Prompt)

Source: https://www.ibm.com/docs/en/aspera-connect/4.2_topic=connect-silent-installation

This command installs IBM Aspera Connect for the current user while disabling the shell extension. It uses the per-user installation path and suppresses reboots. Verify the MSI file path before execution.

```batch
C:\Windows\System32\msiexec.exe /i C:\path\to\ibm-aspera-connect-version_win64.msi WIX_APP_FOLDER=WixPerUserFolder ALLUSERS=0 SHELL_EXTENSION_REQUESTED=0 /qn
```

--------------------------------

### Edge: Deploy Connect via Windows Registry (64-bit)

Source: https://www.ibm.com/docs/en/aspera-connect/4_topic=a-deploying-connect-extensions-in-closed-environments-1

This path indicates the registry key location for deploying extensions to 64-bit Windows systems for Microsoft Edge.

```powershell
HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Edge\Extensions
```

--------------------------------

### Firefox: Deploying Add-on with Custom Build

Source: https://www.ibm.com/docs/en/aspera-connect/3_topic=appendices-deploying-connect-extensions-in-closed-environments

Provides guidance on deploying the Aspera Connect add-on with a custom build of Firefox, referencing external Mozilla documentation. This is intended for enterprise-level deployment.

```text
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Distribution_options/Add-ons_in_the_enterprise#Bundling_add-ons_with_a_custom_Firefox
```

--------------------------------

### Configure IBM Aspera Connect for FIPS (JavaScript)

Source: https://www.ibm.com/docs/en/aspera-connect/4_topic=appendices-enabling-fips

This JavaScript code snippet demonstrates how to modify application code to automatically link to the FIPS version of IBM Aspera Connect during guided installation. It shows the before and after states of the ConnectInstaller configuration, highlighting the addition of the `useFips: true` parameter.

```javascript
Before: var asperaInstaller = new AW4.ConnectInstaller({});  
After: var asperaInstaller = new AW4.ConnectInstaller({useFips: true});
```

--------------------------------

### Configure Aspera Connect for FIPS Mode (JavaScript)

Source: https://www.ibm.com/docs/en/aspera-connect/3.10_topic=appendices-enabling-fips

This code snippet demonstrates how to modify your application code to enable FIPS mode in IBM Aspera Connect. By setting the 'useFips' configuration value to true, the Connect guided installation will automatically link to the FIPS version. This is a client-side configuration change.

```javascript
var asperaInstaller = new AW4.ConnectInstaller({}); // Before modification
var asperaInstaller = new AW4.ConnectInstaller({useFips: true}); // After modification
```

--------------------------------

### Configure IBM Aspera Connect for FIPS Mode (JavaScript)

Source: https://www.ibm.com/docs/en/aspera-connect/3_topic=appendices-enabling-fips

This code snippet demonstrates how to configure the IBM Aspera Connect guided installation to automatically link to the FIPS version of Connect. It shows the modification needed in application code to enable FIPS mode. The `useFips: true` parameter is crucial for this configuration.

```javascript
var asperaInstaller = new AW4.ConnectInstaller({}); // Before
var asperaInstaller = new AW4.ConnectInstaller({useFips: true}); // After
```