Configure Companion

The Windows Companion policy configuration controls the behavior of the Relution Companion for Windows → on managed Windows devices. The configuration is divided into four sections: General, App handling, Server communication and User change on login.

General #

Log level #

Defines how detailed the log entries written by the Windows Companion are. Available options are None, Critical, Error, Warning, Information, Debug and Trace — verbosity increases with each level.

Action Timeout #

Defines the maximum time in minutes for an action to be processed until it is aborted by the Windows Companion.

App handling #

App installation timeout #

Defines the maximum time in minutes for an app installation to be processed until it is aborted by the Windows Companion.

App removal timeout #

Defines the maximum time in minutes for an app uninstallation to be processed until it is aborted by the Windows Companion.

Manage WinGet and its dependencies #

Defines whether WinGet and its dependencies, like Microsoft VC Redistributable, are managed and updated automatically by the Windows Companion.

Server communication #

Communication between the Relution Companion and the Relution Server is necessary for Relution to work properly. Communication is initiated either by:

• the Server, telling the Companion to start communicating
• the Companion, if no interaction between Server and Companion occurred for some time

The settings below allow administrators to optimize the behavior of this mechanic, although this should not usually be necessary. After the time defined by Check interval, the Companion will start communication if the last communication with the server is older than the time specified by Time since last communication.

Check interval #

Defines the interval at which the Windows Companion checks whether a request to the Relution Server is necessary.

Time since last communication #

Defines the minimum duration the Windows Companion waits before sending the next request to the Relution Server.

User change on login #

As of version 26.4, the Relution Companion for Windows can automatically update the device user assigned in Relution as soon as a different person logs into the Windows device. This is especially useful for devices shared by several people, e.g. in a classroom or open-plan office: the device user stored in Relution always matches the person actually logged in on the device.

Enabling the feature #

The feature must be enabled in two places before it takes effect:

1. Organization-wide under Settings → Relution Client Apps → Windows companion using the Enable device user change toggle.

   

2. Additionally, in every policy that should use it, in the Windows Companion → User change on login section via the User change mode.

   

When enabled, the Windows Companion will change the assigned device user in Relution each time someone logs into Windows. Be aware: an unintended user may trigger policy changes meant for someone else, and an administrator’s access token may become exposed to other users of the device. Each configured policy must explicitly opt in for this to take effect.

User change mode #

• Disabled: No automatic user change.
• Only domain users: The change only happens if the logging-in person’s UPN matches the configured domain. A domain and at least one allowed identity provider are required for this.
• All users: The change happens regardless of domain or identity provider. Domain and identity provider are optional here.

For both active modes, the selection can additionally be restricted to specific Allowed identity providers and Allowed users and groups. If these fields are left empty, no additional restriction applies.

The match is made using the Windows login name, which is compared against the username in Relution within the same organization. If the logging-in person is not known in Relution or does not meet the configured conditions, the assigned device user is removed, but no error is shown on the device.