Open

Release notes | 10.5

Table of contents

1. Introduction

These release notes provide information about the latest features of iProtect, including required software versions and hardware installation and operating manuals.

2. System requirements

This chapter lists the required hardware and software for iProtect, including the licensing scheme of iProtect upgrades and other important information.

2.1 Supported servers

For installation and support of the iProtect server, the system requirements of Ubuntu server are followed. This may differ depending on system use and size.
In addition, the duration of support is determined by the lifespan of the hardware. This is issued by the hardware manufacturer and described as MTBF (Mean Time Between Failure).

2.2 Hardware specification

The hardware specification depends on many variables, so the required specification is customer specific.

Guide lines for 2500 card users and 250 readers and 5 concurrent users*.

2.3 Software

The required operating system version for iProtect:

For iProtect 10.05 and Ubuntu 24.04, there is a TKH repository with all needed files for installing and maintaining the setup files.

The operating system can be downloaded from Ubuntu's default repository.

2.4 Update policy

TKH security works non-stop to improve its products and their safety.
From iProtect version 10.5, the software version from which you update and the software version to which you update must be taken into account.

2.4.1 Which iProtect version supports which Pluto RootFS

To ensure a reliable and secure system, the following software versions are required:

2.5 Software and firmware

Software versions of the connected hardware are managed from iProtect by default.
Below you will find an overview of the most used hardware and the minimum version that are installed (provisioned) when updating iProtect.

2.6 License

When a major version number changes, it should be taken into account in advance that a new license is necessary. Please contact TKH Security service department or your account manager for this.

2.7 Browser support

All tests are done with default browser settings, if some functionalities require changes to the settings, this will be mentioned in the specific manual. The following browsers are supported in iProtect:

2.8 API-support

Customers using the API are advised to test the link in an acceptance environment before the update is released in your environment.

3. End of support

• Sirius 1 support in combination with Reader manager version 6

• SimonsVoss SI2

• Traka 32 support

• Support of INVR / License plate recognition on Polyx and IPU-8

3.1 Pre-announcement

3.1.1 Network controller

• Polyx Network controller: End of life: 31-12-2025

• Apollo 1: End of life: 31-12-2025

• iPU-8: End of life per: 31-12-2025

3.2 Revised advance notice

Making use of the hta-tool can entail security risks. That was the reason we wanted to deprecate this.
Since many customers are still using this tool, an option has been added to continue using this hta tool. This usage is disabled by default.

The following option has been added to the dialog:

• Installation | Settings | System parameters, tab: Other, “HTA enable”.

4. iProtect server and application

In every new version of iProtect, there will be product improvements (bug fixes). The section below lists changes or newly added fucntionality compared to iProtect 10.4.

4.1 Free unique text field

In iProtect version 10.5 it is possible to use a unique free (pager) number (range). If the number already exists, you will get an error message.

• button (next free number)

• manual entry