Microsoft App-V 4.6: Application task based on OU membership not executed in user sessions

Version 1


    Consider the following scenario:

    At User Context > Directory Services, a Microsoft Active Directory domain containing OU1 and OU2, was configured for an environment. OU2 was child OU of OU1.

    At Composition > Applications, a Microsoft App-V 4.6 application was configured with the following setting:
    - On the Configuration > Actions tab of the application, a task, for example User Registry Setting, was configured.
    - On the Access Control tab of the new task, in the Identity section, a rule was added for Organizational Unit and OU2 was selected (Include child OUs was not selected).

    A user that was member of OU2, logged in to an RES Workspace Manager session.
    In this scenario, the task was not executed.


    This issue is resolved in RES Workspace Manager 2012 SR5 and RES Workspace Manager 2014 SR1.

    In case the Service Release is not (yet) available or in case the Service Release cannot be installed, a revision containing this update is available on request at RES Support.

    IMPORTANT: A revision contains multiple code changes. Please note that these changes are not regression-tested. Only apply this revision when you are experiencing a specific problem and are not able to wait for the Service Release. Unless you are severely impacted by this specific problem, RES Software recommends that you wait for the next Service Release containing these updates.

    Workaround: Activate the Include child OUs option

    On the Access Control tab of the task, in the Identity section, edit the rule based on OU and check the option Include child OUs.

    Even when no child OUs are available, activating this option will solve the issue.

    Make sure that activating these options (and allowing members of the child OUs get this Action executed) is allowed within your organization.