The RES VDX screensaver does not start after the specified timeout

Version 1

    Problem

    The RES VDX screensaver, which is part of RES Subscriber for VDX, does not start when the timeout has passed. Either the local Windows screensaver is started or nothing happens after the timeout. This depends on the settings of the local Windows machine. When the user tries to lock the session through the "Lock Icon" in the system tray, nothing happens.

    Expected behavior:
    When the screensaver is configured in the RES Workspace Management console and enabled, the RES VDX screensaver should start after the timeout has passed. Clicking the "Lock Icon" should result in starting the RES VDX screensaver.
     

    Cause

    One or more prerequisites of the RES VDX screensaver are not available
     

    Solution

    The RES VDX screensaver has the following prerequisites:

    - RES VDX is integrated with RES Workspace Manager. In the RES Workspace Manager Console at "Setup > Integration > RES Software > RES VDX" the options "Enable RES Virtual Desktop Extender (VDX) integration" and "Enable VDX Engine" need to be enabled.

    - In the RES Workspace Manager Console at "Composition > Desktop > Screensaver" the screensaver composition needs to be enabled and the option "Set mandatory timeout for screensaver (1-60 minutes)" needs to be enabled with a specified time.

    - On the local client in the RES Subscriber for RES Configuration Window at the tab "Screensaver" the option "Use Subscribed screensaver" needs to be enabled and the following authentication method needs to be used: "Session (request password of user logged in to remote session)".

    - On the local client in the RES Subscriber for RES Configuration Window at the tab "Behavior" the option "When the Subscriber starts, keep the local desktop active" needs to be disabled.