Enabling the Feature

Before you can use this feature, you must enable it by clicking on the Enable button. Once enabled, Universal Settings Distribution will start immediately if the Central Server is running. If you wish to review the Universal Settings Value prior to distributing them, you can either stop or pause the Central Server.

Note: It is safe to enable this feature even while the Central Server is running.

Later on, if you no longer need this feature, simply click on the Disable button in the control bar.

Configuring the Universal Settings

Once enabled, the interface discloses the available Universal Settings, their current values and configuration type.

To modify the value of any Universal Setting, you must enter the Modify Mode first. To do so, click on the Modify Settings link in the controls area. Then double click on a setting to modify its value.

Defining a Universal Setting Value

A Universal Setting value property window displays the following sections:


This section provides a summary of the purpose and possible values of the setting.


A Universal Setting can be configured to have the same value for all machines, or a different value for specific groups of machines and a default value for all other machines. This is done via the setting scope.


The Setting Scope area always includes an All Machines / Every Other Machine item which is used to define the default value to apply. You can optionally define other values for specific sets of machines. To do so, create a new Setting Scope as follows:

  1. Create a new Setting Scope by clicking on the Add Scope button or double-clicking on the Add New Scope icon.
    • If this is the first time that you are creating a setting scope, the New Scope property window opens which allows you to define a new scope.
    • If you already have defined scope objects which are not currently used by the focused setting, then you will have a choice to re-use these scope objects.
  2. Once you have added a new scope in the Setting Scope area, select it and configure the value for this scope.


If two or more scopes are defined for a setting, and a machine requesting for settings belongs to more than one scope, the scope with the highest priority (left most) is used. Use the Shift Priority button to change the priority of a scope.


Once you have created a scope, it automatically becomes a template which can be re-used for other settings. Clicking on the Add Scope button will present you with the available scopes to choose from.

  • Any changes to a scope object are reflected in all settings which are using this scope.
  • If you remove a scope object from a setting and this scope object is used by other settings, you will have the choice to remove the scope from this setting alone or from all settings (in which case the scope template is deleted).


Your scope object may include dynamic machine sets. For instance, an Active Directory container or group which may hold different accounts over time. The Goverlan Central Server is designed to automatically take these changes into consideration while keeping the response time to client machines very low.

To do this, a dynamic scope's content is cached and the cache is updated periodically. If a scope content change is detected, the Settings Version Id is incremented so that the new contents can be processed.

The frequency at which the server checks for changes in the scope contents is defined by the Client Refresh Interval setting (every 30 minutes by default). This means that modifications made to an Active Directory OU or group used in a scope will only be detected by client machines within the Client Refresh Interval time frame.

A detected change in a machine scope's content will result in the Settings Version Id being changed even though the settings themselves haven't changed. When this happens, the Settings Version Id reported in the Server Activity monitor may be different that the Settings Version Id reported in the Universal Settings tab.

Scope change detections are also registered in the Execution Log.


Once you have selected the Setting Scope for which to apply this setting, use the Setting Value area to configure the setting value. Note that the Setting Value title will always include the Setting Scope for which this setting applies.

A universal setting value can be configured using the following options:

  • Do not enforce this setting
    • Not all settings need to be securely transmitted to your clients. In some cases, you may want to allow the end user to change the value of one or more setting. For instance, you may authorize Goverlan end users to control the Application Directories settings. Select this option if a particular setting does not need to be forced upon your clients. When selected, the Goverlan client applications simply resume standard behavior and either uses the group policy value or the default value (if the group policy is not defined).
  • Use the Group Policy or Default Value
    • This mode is the default for all settings. When enabled, the Universal Setting value is derived from its Group Policy value or from its default value (if the Group Policy is not defined), and then it is securely transmitted to the clients. This mode is very convenient since you can still use a domain Group Policy Object to define your values. However, only the Goverlan Central Server reads them and then they are securely distributed to your clients. This mode is particularly useful if you have more than one Goverlan Central Server and do not want to synchronize their Universal Setting values.
  • Use the following Value
    • Select this mode if you want to manually configure the value of the setting.

Publishing your Changes

Once you have configured all values to the desired value, click on the Publish Settings link in the control area. If you do not wish to publish these setting changes, click on the Cancel Changes link.

Every time you make a change to the Universal Settings and you publish it, the Settings Version ID changes and this indicates to the clients that an update is available. For this reason, try to make all setting changes at once and publish the changes.

Note: The Settings Version ID may change even if you do not change the Universal Setting Values. For instance, changing the Client Refresh Interval will change the Settings Version ID. Additionally, the version ID displayed may be lower than the version ID actually distributed to client machines.


To have all clients updated with a fresh set of settings, it will take, at most, the Client Refresh Interval time. The Client Refresh Interval defines the frequency at which Goverlan Client Application check with the Central Server for updates, and its default is 30 minutes. This value is configured via the Server Settings.

There is a number of factors which will affect this time frame such as network latencies or server and client load.