Versions / Builds Affected
EndPointSecurity 2013 (all builds)Status
OpenProblem Summary
Configured file type filters do not work, and the user is allowed to access file types that should be blocked.TT / JIRAID
381How to Identify
Issue occurs when the policy is a new created policy and in the Create Protection Policy wizard, the 'Blank protection policy' option is selected.
In the agent log file, you will find the following error:
2013-07-21,14:00:33,353,3,"#00001144","#00001f58","info ","DevicesController"," policy guid: 6686fe16-804a-4372-8786-62a054c990bc"
2013-07-21,14:00:33,353,3,"#00001144","#00001f58","info ","DevicesController"," read controlled categories:"
2013-07-21,14:00:33,353,3,"#00001144","#00001f58","info ","DevicesController"," enabled categories: 0,1,2,3,4,5,6,7,9,"
2013-07-21,14:00:33,353,3,"#00001144","#00001f58","info ","DevicesController"," read controlled ports:"
2013-07-21,14:00:33,353,3,"#00001144","#00001f58","info ","DevicesController"," enabled ports: 0,1,2,3,4,5,6,7,"
2013-07-21,14:00:33,353,3,"#00001144","#00001f58","info ","DevicesController"," read power users:"
2013-07-21,14:00:33,353,3,"#00001144","#00001f58","info ","DevicesController"," read exception devices:"
2013-07-21,14:00:33,353,3,"#00001144","#00001f58","info ","DevicesController"," read permissions:"
2013-07-21,14:00:33,353,3,"#00001144","#00001f58","info ","DevicesController"," user fshq.fs\Ahmed.Elhosseiny (sid S-1-5-21-792885814-1249132539-559391517-28246) has"
2013-07-21,14:00:33,353,3,"#00001144","#00001f58","info ","DevicesController"," read/write for category 2 with priority 1"
2013-07-21,14:00:33,353,3,"#00001144","#00001f58","info ","DevicesController"," read encryption support:"
2013-07-21,14:00:33,353,1,"#00001144","#00001f58","error ","DevicesController","Failed to read FileOptions settings!"Workaround / Fix Details
To workaround this issue:
1. Create a new policy
2. In the wizard choose 'Copy the settings of an existing protection policy'
3. Select the 'General Control' policy (It is important to select this policy, and not another one which was created by the user)
4. Click on the Finish button
5. Go to the new policy settings, delete current settings and configure as necessaryRequired Actions
1. Provide workaround to the customer
2. Attach this article and close the case