Configuration Update Management

Updated 3 days ago by Stephanie Krenz

Note
The organization decides whether updates are available to the user directly from the application, or whether they are rolled out centrally by IT.

Overview

From version 2.8.34, dab Link has a configuration option for centralised software updates.

This allows the organisation to centrally manage updates and make them available to end users via software distribution.


Settings - implemented by the customer's IT department

Note
The adjustments shown here, which result in the activation of central software updates, are not carried out during the update or installation of dab Link.

When centralised software updates are used, the following steps are first defined by the IT department and then rolled out to all end users via software distribution.

The HKEY_LOCAL_MACHINE\Software\dab\dabLink registry key will be used in the future to control the dab link update mechanism (see screenshot).

Changing the value of the ManagedUpdates key will enable the company managed functionality. Adjust the value of ManagedUpdates and change it to = 1


How does the end user know if updates are centrally managed by the organisation?

When centralised management is enabled, the previous update button will no longer be available to the end user or will be replaced by a notification. This message will indicate that updates are managed by your own organisation.

Update notifications are no longer necessary as IT ensures that all users automatically receive the latest version.


Benefits for the users

  • No need for users to actively check for updates - no need for manual update checks
  • Users no longer need to actively check for updates - no manual update checks required
  • Internal IT support available as contact point for questions or problems
Note
If the organisation does not activate central administration, nothing will change for users - the update button will remain as usual and they will receive notifications of new dab Link versions.


How did we do?


Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)