If a folder more than one level below the managed object is excluded from a blocking policy, the exclusion may fail, preventing users from saving data to the excluded folder.

Example:
At the root of C: there is a folder called MyFolder1. MyFolder1 contains MyFolder2, MyFolder2 contains MyFolder3 as shown in Figure 1 below.

Figure 1
 


If a blocking policy is created to exclude MyFolder3,  the exclusion property window Filters (Optional) reflects the full path to MyFolder3 with the exception of the drive letter as shown in Figure 2 below.

Figure 2
 


Upon creation of a managed object for C:\MyFolder1, applying the file blocking policy that is configured to exclude MyFolder3, the expected results would be the blocked file types in the file blocking policy can be saved to MyFolder3.

Unfortunately, the exclusion configured in the policy will not successfully exclude the MyFolder3 folder from the policy, files of the excluded type will be blocked.

To successfully exclude the MyFolder3 folder from the file blocking policy, the path must be amended.

Edit the path in the filters (Optional) so that the managed object is not part of the path as shown below in Figure 3

Figure 3
 


Once the path has been edited, the folder specified for exclusion will be excluded and files of the blocked type can be saved successfully.