How to update iProtect™ to 10.4

Owned by Arnout van Wanrooij
Last updated: Oct 15, 2024 by MB
4 min read
image-20240409-111113.png

How To Article | HTA-20241011-AVW-01

iProtect Access / Security | How To Articles | How to update iProtect™ to 10.4

 

How to update the iProtect™ Application.

Introduction

This how-to guide provides you with instructions on how to update your iProtect system to the latest 10.04 version, allowing you to take advantage of the latest improvements and features.

Update workflow

Download files

Download the latest files on our download section of the knowledgebase:

  • iProtect Serverbox

  • IProtect Database

*iProtect™ - Software Downloads | Version 10.4

Pre-checks

Before the update it is required that the state of the system is known. Not functioning readers, nodes and lines must be noted. If possible, restore the connections first, if this is not possible, then put the relevant lines inactive. Check and test database couplings and other custom intergrations, it's best to test them on a 10.4 test-system first to see if they work or still need adjustments first.

Compatibility and discontinued hardware/software is noted in the release notes:

 

Minimal requirements / tested versions:

Before updating to iProtect version 10.4, controllers should be running RootFS v6.11 or higher.

iProtect - Release notes 10.4 | 2.4.1 Which iProtect version supports which Pluto RootFS

Getting the necessary files

Creating a new Backup of the iProtect system and download the Backup from the maintenance page.

Updating the iProtect version.

First, it is important to bring the server fully up to date, you can do this by going to the “Software updates” tab in CockpitPanel and then running a scan to see if any updates are available.

Cockpitpanel is reachable by the url https://{ipadress}/cockpitpanel

Install the new serverbox at the maintenance page.

  • Go to the iProtect™ maintenance page (Click on the iProtect maintenance tab in cockpitpanel)

  • Activate the maintenance functions by clicking on the activating button at the top left.

  • Go to file upload section at the maintenance page (Install > Upgrade > Configuration)

  • Click on the “...” button below Upload iProtect™ (1) and select the new maintenance page version and click on the “Post” button.

  • Refresh your browser webpage.

Install the new iProtect™ version at the maintenance page.

  • Install > Upload iProtect (1)

  • Click on the “...” button and select the new iProtect™ package and click on the “Post” button.

When the “Check requirements” button appears, press it and a check will be done. Check the log and see what is needed to continue.

  • If the check is passed you get a “Start Upgrade” button and can start the upgrade by a click on this button.

You can follow the installation at the User interface logging, if you see the messages below the GUI is ready and you can login in iProtect™ again (only the root user can login at this point).

Installing the new license:

*How to import an iProtect™ license (>=10.1)

If a new license is needed, please contact our orderdesk.

Activating lines

To be sure all lines and nodes gets the latest software, select the system default Provisioner group.

  • Go to iProtect™ menu option Installation > Hardware > Line

  • Select System default at the Provisioner group options.

The components under the line config will automatically be provided with the latest firmware version.

 

Activate the line’s now, the Door controllers will get the new software and start with the installation automatically. The doors will be non-functional for 5-10 minutes (depending on network speed). Open doors beforehand if they are critical.

When updating iProtect to version 10.04, all network controllers will be updated automatically to a new rootFS version. This update will be processed in the background and will take aprox 5 -15 minutes (depending on network speed).

During the preparation of the Pluto rootfs update, the customer will not experience any inconvenience.

When the rootfs update is complete, the system administrator must reboot the controller to finalize the rootfs update. Booting up the controller will take approximately 2-5 minutes (depending on network speed). During this time, the customer may experience problems opening the door.

Below elements will be installed on both rootfs partitions and other hardware during the update.

Pluto

  • Device certificate (if not valid or missing)

  • Pluto rootfs

  • Reader manager

  • Pluto maintenance page

Orion

  • Bootloader Orion

  • Orion Firmware

Reader

Reader (only Sirius iX versions):

  • Reader firmware

Open firewall ports on the Pluto

Starting from Rootfs version 6.12 a firewall is actively running on the Pluto. If necessary, you can open the required ports by sending a .taz file to the Pluto. The files can be obtained via the link below.

This is required for certain integrations that are configured on the Pluto. For more details, please refer to the page below.

Firewall settings rootFS v6-12

Finishing the update

When all lines are updated and the re-index message is gone, you can finish the update with the button in the menu:

Installation > Database restore > Activate line

Some points to check at the end of the update:

  • Readers

  • Database couplings

  • Client login (remove browser cache)

  • Import / Export

  • iNVR

  • Printing badges/cards

  • Intercom

  • browser certificate