# Installation of the IPI Client Application

The installation package for IPI Client comes in two formats:

* **Bootstrapper (.exe)**
* **MSI package (.msi)**

{% hint style="info" %}
**You can find the .exe installation file** [**here**](/product-updates/ipi-client-updates.md)**, and the .msi installation files here:** [**x86**](https://update.ipi.com/update/ipiclient/x86/clientsetup.msi) **version and** [**x64**](https://update.ipi.com/update/ipiclient/x64/clientsetup.msi) **version.**
{% endhint %}

### **1. Bootstrapper (.exe)**

{% hint style="info" %}
The Bootstrapper automatically detects the system architecture (x86 or x64) and installs the necessary components:

* IPI Client MSI (for x86 or x64)
* C++ Redistributables 2015-2019 (for x86 or x64)
* .NET Framework 4.7.2 web installer
  {% endhint %}

## **Installation Process for IPI Client using Bootstrapper (clientsetup.exe):**

1. Download [`clientsetup.exe`](/product-updates/ipi-client-updates.md) from the official website or internal resource.
2. Run the downloaded installation file (as administrator).
3. Accept the license terms by checking the box next to **"I agree to the license terms and conditions."**
4. Select the necessary installation options:
   * **Enterprise version** or **Home version:**

     * **Enterprise version** allows connecting to the IPI Enterprise Server (IES).
     * **Home version** is more suitable for personal use.

     <div><figure><img src="/files/QkBfcIFxQzgi4Tl8cq8i" alt=""><figcaption></figcaption></figure> <figure><img src="/files/eFXYjnS3KKTRzWhtDzSK" alt=""><figcaption></figcaption></figure></div>
5. Choose the Bluetooth connection type:
   * **Use Windows Internal Bluetooth (Beta version)** — suitable for computers with built-in Bluetooth.
   * **USB Dongle** — for connection via an external Bluetooth dongle.
   * **Do not use Bluetooth** — only for using the mobile application without hardware keys.

{% hint style="info" %}
**Using Bluetooth for Proximity:**

Using Windows **Internal Bluetooth** or **USB Dongle** is necessary for the Proximity mechanism, which automatically unlocks the workstation using IPI Key.

* **Proximity** activates workstation unlocking when the user approaches the computer with the IPI Key.
* **Bluetooth** is used to determine the distance between devices.
  {% endhint %}

{% hint style="warning" %}
The internal Bluetooth option is supported only for Windows 10 version 1903 (2019) and later. In earlier versions (before 1903), the IPI Key will only work with the external IPI Bluetooth dongle. This means that for Proximity to function correctly on older versions of Windows, an external dongle is needed to establish communication between the key and the computer.
{% endhint %}

6. Specify the IPI Enterprise Server address if you are installing the Enterprise version.
7. Choose the desired interface language (e.g., Ukrainian or English).
8. Click the **Apply** button to complete the installation.

<figure><img src="/files/o9dNFibNKujAYTodbQkr" alt="" width="328"><figcaption></figcaption></figure>

**After Installation:**

* The application will be ready for use. If using Proximity, ensure the connection to the IPI Key is set up via the selected Bluetooth (built-in or USB Dongle).

{% hint style="info" %}
Next, you need to approve the workstation on the IPI Enterprise Server (IES) to enable interaction with the server and receive the necessary settings for Proximity and other security mechanisms.
{% endhint %}

* If you did not specify the address during installation, it can be added later in the application settings.

<figure><img src="/files/C1rMKg3v1XLJSVDNtvll" alt="" width="563"><figcaption></figcaption></figure>

## **Silent Installation via Command Line**

### **1. Bootstrapper (.exe)**

```bash
clientsetup.exe -silent Config="-winradio -enterprise -loc=en-US -server=http://192.168.10.249/"
```

This command performs a silent installation of the Enterprise version with a connection through WinRadio (built-in Bluetooth), in English localization, and connects to the IPI at the address <http://192.168.10.249/>.

### **2. MSI Package (.msi)**

The MSI package allows administrators to automate the installation via GPO (Group Policy) or manually through the command line.

```bash
msiexec /i IPIClient.msi /quiet CONFIG="-enterprise -no_ble -server=http://192.168.10.249/ -loc=en-US"
```

This command performs a silent installation of the Enterprise version with a mobile app-only scenario in English localization, and connects to the IPI at the address <http://192.168.10.249/>.

```bash
msiexec /i IPIClient.msi /quiet /norestart
```

### **Modifications During Installation:**

* Client files are installed in `%ProgramFiles%\IPI\Client\`.
* A registry key is created at `HKLM\SOFTWARE\IPI\Client`, storing your IES server address.
* A custom IPI CSR driver is installed.
* A shortcut to the application is created in `%ProgramData%\Microsoft\Windows\Start Menu\Programs\IPI\`.
* The application is added to the Windows Programs list.

### **Important Parameters for Installation:**

* `-enterprise` — installs the Enterprise version.
* `-dongle` — installs using the USB Dongle.
* `-winradio` — uses the internal Bluetooth.
* `-noble` — only uses the mobile application without hardware keys.
* `-loc=` — sets the language (e.g., `-loc=uk-UA` for Ukrainian, `-loc=en-US` for English).
* `-server=` — specifies the IES address (e.g., `-server=https://hes.example.com`).
* `-silent`, `-s` — silent installation mode without windows (**for .exe**).
* `/quiet` - silent installation mode without windows **(for .msi**).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://enterprise-ipi-en.hideez.com/ipi-client-app/windows-deployment/set-up-ipi-client-app.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
