`Custom User Interface` Group Policy Object is not always loaded

Version 1

    Problem

    It can occur that RES Workspace Manager is not started when using the`Custom User Interface` Group Policy Object.

    For example: The Group Policy Object is loaded correctly at the first logon and RES Workspace Manager is started as a custom shell. The second logon, the Group Policy Object is not loaded correctly and the Windows Explorer is set as shell  and so on.

    NOTE: `Custom User Interface` Group Policy Object is the best practice for loading RES Workspace Manager on a Terminal Server, NOT for a Workstation or Laptop.
     

    Cause

    Due to a timing issue, the Group Policy Object is not yet  loaded when logging on.
     

    Solution

    Make sure Group Policy processing is synchronously applied. This can be configured by enabling the following Group Policy Object:

    Computer Configuration/Administrative Templates/System/Logon/
    "Always wait for the network at computer startup and logon" = Enabled