Data Collection exclusions are not working correctly if a child path is explicitly included

Version 1

    Verified Product Versions

    AppSense Environment Manager 10.1

    Introduction

    For folders, if a path such as abc\def\ghi is added as an include for data collection, and the parent path abc\def is added as an exclude then, once data has been collected, the path abc\def still appears in the list of path inclusions in the “Manual Configuration” dialog.

    Note, this does not mean the exclusion has failed as the folder abc\def\xyz would be ignored.

    However, as the excluded parent folder is made available for selection due to the inclusion of the child path, this would effectively break the exclusion if selected.

    A similar problem occurs for registry paths but here the exclusion does fail if a child path is added as an include. If, for example, the path HKCU\abc\def\ghi is added as an include and HKCU\abc\def as an exclude then the path HKCU\abc\def\xyz would appear in the collected data if encountered.  

    The problem, therefore, is somewhat different for registry paths than folder paths as non-included sub-paths have been included.

    Detail

    The following screenshot may help to illustrate the symptoms:-

     

     

     

    The registry path HKEY_CURRENT_USER\software\test1 has been added as an exclude and HKEY_CURRENT_USER\software\test1\test2 as an include.

     

    The folder path {CSIDL_PROFILE}\test1 has been added as an exclude and {CSIDL_PROFILE}\test1\test2 as an include.

     

    As can be seen, with the folder paths no other sub-folder, other than the explicitly include one, has been captured (these did exist) but with the registry paths HKEY_CURRENT_USER\software\test1\subkey has been included implicitly.

     

    In the case of folder paths the UI is incorrectly displaying the parent folder path. But for registry paths it appears the agent is incorrectly including excluded sub-paths when another sub-path is added as an explicit include.

     

    When using the Manual Configuration dialog do not select the incorrectly included paths