4.12.0004 (Service release 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?

VAKA Admin (Needs a B60)

  • Cog wheel menu added, includes language setting, backup and system information.
  • Updated languages: (English, Swedish, Finnish, Dutch and Norwegian).
  • Improved scrolling of live events.
  • Improved scrolling of organisational groups and users.
  • Possibility to pause updating of events.
  • Many improvements in the user interface.
  • Improved search function.
  • Fixed problem with "port forwarding" from alternate ports through router not working.
  • Time schedule can now be created from access group- and door view.
  • Support for usage of other port than 443.

Java/PC-Klient

  • Updated languages: (English, Swedish, Finnish, Dutch and Norwegian).
  • New tab Applications under Settings/ System settings.
  • Extended field lengths for DynDNS account and domain name.
  • DynDNS password is not possible to read after saved to database.

General updates

  • Support for motor lock module C14.
  • Events via email: Option to include the name of the person who generated the event.
  • Black listing of radio tags removed.
  • Added support to door controllers Bx7 to manage 15 event channels.
  • Improved commissioning/ start-up of Bx7-R after long storage time.

Info- and reservation panel

  • Fixed problem with panels not always lighting up when passing through door with same location.
  • Shows on-going reservation for logged in user.

Update information

Berfore upgrading to 4 SR1, the system must run at least 3.8x. 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.12.0001 System diagnostics
B05, B06, B15, B16, B17, B17-R, B25, B26, B27, B27-R 4.12.0003 System diagnostics
B28, B18 4.12.0003 System diagnostics
PC-client 4.12.0002 VAKA window
Info- and booking panel 4.12.0001 Configuration menu in panel
A6x (HW:2) 3.10.01 Systemdiagnostiken som A66:
A6x (HW:1) 3.00.09 In system diagnostics as A66.
A6x (HW:0) 1.07.01 In system diagnostics as A66
A45 3.09.02 System diagnostics
A42, A52, A53, A56 1.06.02 System diagnostics
ClosedUpdate inside VAKA generation 4

Follow the instructions for Manual update with the package (vaka-mini-4.12.0004.vfp).

ClosedUpdate from VAKA 3.8x

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:

  1. From Main Menu in B60, navigate to Tools and press return.
  2. Navigate to Restart Device and press return.

Update

Follow the instructions for Manual update with the packaget (vaka-maxi-4.12.0004.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.

Other news

In addition the the news above, see also the news in VAKA 4 and in the hotfixes that has been released.

Updated24/06/2024