4.14.0007 (Service release 2 Hotfix 1)
- Updating must be carried out by an installer with knowledge of the particular VAKA system.
- Updating must not be done over the internet.
- Before upgrading to a new VAKA version, it is important to ensure compatibility with third-party integrated solutions * . Examples of such solutions are Renz mail boxes and Amido Alliera. To avoid operational disturbances, check with respective party that applicable versions are compatible.
- After updating, it can take up to 45 minutes before the system is fully operational.
- Before upgrading make sure the system security is set to default level (Settings->System->Security).
What is new?
Java/PC-Client
- JNLP file fix. The JNLP file makes sure that compatible Java versions (JVM runtime) are used.
Alarm related improvements
- Fixed problems with door controller (with C12) restarts when setting the alarm.
Update information
Berfore upgrading to VAKA 4 SR2 HF1, the system must run at least 3.86, 3.87 or 3.88. In the event that the system is in an older version, follow previous upgrade instructions to upgrade to any of the 3.8 versions.
For help with upgrading, please contact the local distributor or the Axema support department, +46 (0)8-722 34 40 (keypress 2) or [email protected].
After upgrade, the following versions apply
| Product | Version | Showed in |
|---|---|---|
| B60 | 4.14.0005 | System diagnostics |
| B05, B06, B15, B16, B17, B17-R, B25, B26, B27, B27-R | 4.14.0003 | System diagnostics |
| B28, B18 | 4.14.0003 | System diagnostics |
| PC-client | 4.14.0003 | VAKA window |
| Info- and booking panel | 4.14.0001 | Configuration menu in panel |
| A6x (HW:2) | System diagnostics as A66: | |
| A6x (HW:1) | In system diagnostics as A66. | |
| A6x (HW:0) | 1.07.01 | In system diagnostics as A66 |
| A45 | System diagnostics | |
| A42, A52, A53, A56 | 1.06.02 | System diagnostics |
Update inside VAKA generation 4
Follow the instructions for Manual update with the package vaka-mini-4.14.0007.vfp.
Uppdate from 3.86, 3.87 or 3.88
To do before upgrade
Configure system security
Ensure that the system security is set to the default level (Settings->System->Security).
Create a backup of system data
Create a backu by following the instructions in the Java-client in Settings -> Backup.
Open port 443
After the upgrade, some communication will be done over HTTPS. Therefore port 443 must be open where system parts communicate between network segments and where connection for remote administration is needed.
If there is at least one B60 in the system
Restart a B60 by:
- From Main Menu in B60, navigate to Tools and press return.
- Navigate to Restart Device and press return.
Update
System without B60
Follow the instructions for Manual update with the package vaka-mini-4.14.0007.vfp.
System with B60
Follow the instructions for Manual update with the package vaka-maxi-4.14.0007.vfp).
To do after upgrade
Set country- and area code
In order to prepare for future functions, the country code and area code for the intercom must be entered at the first login after upgrading. This is done in the dialog that is presented.
Associate email address with migrated administrators and installers
When upgrading to VAKA 4 or later, former administrators and installers are migrated to users/persons with roles (and rights) to interact with VAKA. Theese users should be given valid e-mail addresses. Please note that, when an e-mail address is specified, this is used as the username when logging into VAKA.
Change playlists from HTTP to HTTPS
If there are playlists where HTTP is used, these must be changed to HTTPS.