Set up IPI Client app
IPI Client App – Setting up IPI Client
Last updated
IPI Client App – Setting up IPI Client
Last updated
The installation package comes in two forms:
Bootstrapper (.exe)
MSI package (.msi)
You can find the .exe installation file here and .msi installation files here - x86, x64.
Bootstrapper is a special application that is used to install prerequisites that are required by the installed application.
The IPI Client Bootstrapper contains:
Two IPI Client MSI. One for 32-bit architecture and one for 64-bit architecture
Two C++ 2015-2019 Redistributables. One for 32-bit architecture and one for 64-bit architecture
.NET Framework 4.7.2 web installer
The bootstrapper automatically determines the architecture of the system (32-bit or 64-bit) and installs the respective components without the need for user input on the matter.
To proceed with the installation, check the I agree to the license terms and conditions checkbox.
IMPORTANT: Please, notice that Internal Bluetooth option is supported only for Windows 10 version 1903 (2019) and later. In earlier versions, IPI Key works only with the IPI dongle.
You need to select the Enterprise version option and specify the Use Windows 10 Bluetooth option if you will use the built-in Bluetooth or Use an external IPI dongle if you will be using the dongle. Here you have to provide the IES address. In addition, you can choose the language required. Choose desired options and click the "Apply" button.
In case you did not provide the IES address during the installation, you need to enter IES address in the 'Settings' section.
And save it by clicking the 'Save' button.
Then the server indicator becomes yellow and you will need to approve the workstation on IES. Then you will have to click the "Reconnect' button:
Installation from an MSI file does not install additional components. They must be installed separately, but the MSI file can be used in automatic installation scripts.
During installation the package will make the following modifications to the system:
Application is installed under the following path %ProgramFiles%\IPI\Client\
A new registry key is created under HKLM\SOFTWARE\IPI\Client
A registry value client_hes_address (type REG_SZ) is created under HKLM\SOFTWARE\IPI\Client and contains IPI Enterprise Server address
A custom IPI CSR driver is installed on all compatible devices
A new folder is created in the following location %ProgramData%Microsoft\Windows\Start Menu\Programs\IPI and contains a shortcut to the IPI Client executable file
A registry value IPI Client is created under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run and contains a path to the application executable file clientsetup.exe from the installation folder
The application is added to the Programs and Features table in Windows
If installed using Bootstrapper, the entry is called IPI Client
If installed using MSI, the entry is called IPI Client Update <version>, where <version> is changed based on assembly version
If IPI Client application is running during the installation process, the installer will try to stop services and client application without asking for additional user input.
Both installation options (Bootstrapper and MSI package) support the transfer of parameters from the command line:
Argument | Description |
---|---|
-standalone | Set application mode to Standalone |
-enterprise | Set application mode to Enterprise |
-dongle | Set connection type to External Bluetooth dongle |
-winradio | Set connection type to Windows internal Bluetooth |
-loc= | Set application localization by specifying culture after = Supported cultures: en-US, uk-UA For example: -loc=en-US, -loc=uk-UA |
-server= | Set connection address to Enterprise server after = For example: -server=https://address.com |
-silent, -s | Skip the configuration window in attentive installation |
The parameters are not mandatory. The installation can be performed without specifying parameters.
If no arguments were specified, installation defaults to Standalone mode.
If no connection type was specified, it defaults to WinRadio in Standalone mode only.
Enterprise mode is not affected by this rule and permits no connection modes, which limits client application usage with the mobile authenticator.
If multiple application modes were specified, Enterprise mode takes higher priority.
If multiple connection types were specified, both will be enabled, but application stability is not guaranteed.
If multiples of the same parameter are specified, only the first one is considered.
The following line is executed from the command line terminal:
The execution of this line will result in the silent installation of a standalone version with an external dongle connection type and English localization. The installed application will then try to connect to the IPI Enterprise Server at the following address: http://192.168.10.249/
Note: For the quiet (silent) installation, the command must be executed with administrator permissions.
The following line is executed from the command line terminal:
The execution of this line will result in the silent installation of a standalone version with an external dongle connection type and English localization. The installed application will then try to connect to the IPI Enterprise Server at the following address: http://192.168.10.249/