.png?version=1&modificationDate=1682599136539&cacheVersion=1&api=v2)
How To Article | HTA-20230206-LG-01 iProtect Access / Security | How To Articles |  |
How to update the iProtect™ Application.
Download the latest files on our download section of the knowledgebase:
Prechecks
Before the update it is required that the state of the system is known. Not functioning readers, nodes and lines must be noted.
Check and test database couplings and other custom intergrations, it's best to test them on a 10.2 system first to see if they work or still need adjustments first.
Compatibility and discontinued hardware/software is noted in the release notes:
https://tkhsecurity.atlassian.net/l/cp/1JpMgs8A
Minimal requirements:
Firmware intrusion detection (Unii 2.4.0 / XL 3.11 / ML is EOL)
Rootfs Pluto's (5.68a)
Firmware polyx (UBIFS)
Diva/Sense (2.6.13)
iProtect version 10.1.37
Update iProtect first to version 10.1.37 https://tkhsecurity.atlassian.net/l/cp/5tgAjCAi
Getting the necessary files
Download the Backup from the maintenance page. Unpack the backup and unpack the file in the backup. You will find 2 files in there. Mail the backup.key.asc to the TKH security supportdesk. They will generate a restore.taz for this backup.
Setting up Ubuntu server for iProtect
Use the manual that TKH security will provide to set up the new Ubuntu server and to setup the iProtect-Setup.
If you use the same hardware server, it is recommended to use a new harddrive if the drive is more then 5 years old. Also make sure the memory is sufficient of iProtect (https://tkhsecurity.atlassian.net/wiki/spaces/KB/pages/9268232203/iProtect+-+Release+notes+10.2#2.2-Hardware-specification) )
Upload the new iProtect™ version at the maintenance page
Go to the iProtect™ maintenance page (Click on the gear button on the login screen)
Install > Upload iProtect (1)
Click on the “...” button and select the new iProtect™ version at the maintenance page 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 upload 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 iProtect 10.1 over 10.2
The new server has a valid empty 10.2 database, now upload the restore.taz and after that upload the backup.
iProtect will now be updated to the 10.2 version. This can take up to 30 minutes until you can log into iProtect.
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:
https://tkhsecurity.atlassian.net/l/cp/51UgXjhX
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. Open doors beforehand if they are critical.
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:
Readers
Database couplings
Client login (remove browser cache)
Import / Export
iNVR
Printing badges/cards
Intercom
browser certificate