Solved! Go to Solution.
OK, I was close to give up.
After updating the ENS extensions as suggested did not fix the problem, I was close open a support ticket or start a clean re-install.
But then I found the fix / workaround (whatever you will call it).
When adding a new exclusion, I have to add the path without the "Also exclude subfolders" option (as it is still greyed out) and click OK.
And then I select the previously created exclusion, click the edit button and - voila - it then it allows me to select the "Also exclude subfolders" checkbox.
Don't know what the logic is behind it, but at least it works now.
I would like say Thank You to all who supported me with their suggestions.
I tried to reproduce the issue. If I write C:\root then 'Also exclude subfolders' is grayed out but if I write c:\root\ (ends with \) write Also exclude subfolders got enabled and I am able to check the box.
Guys, thank you very much for your responding already within a few hours. I really appreciate it.
However I already tried your suggested solution already before (that's what I meant when saying "w/ and w/o ending "\"").
Unfortunately it didn't make a difference.
The setup I am working with is ePO 5.3; ENS 10.5.05.
Thanks, Martin
Folder exclusions require a trailing backslash. What version of epo and what extension version of ens do you have?
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
Thank you very much for your responding already within a few hours. I really appreciate it.
However I already tried your suggested solution already before (that's what I meant when saying "w/ and w/o ending "\"").
Unfortunately it didn't make a difference.
The setup I am working with is ePO 5.3; ENS 10.5.05.
Thanks, Martin
Policies are added by the point product extension. Does the issue occur if you duplicate the McAfee default policy and try to add the same exclusion? If not, it may be a policy corruption issue which you would need to recreate the policy from scratch (do not duplicate it) and delete the corrupted policy. If issue is present still after duplicating the default, I would suggest first upgrading the extension to a higher build (you do not have to upgrade the clients for this). If the later extension does not resolve it, please open a ticket with McAfee so we can look into it.
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
The issue occurs no matter if I am creating a new task or trying to edit a copyed existing tasks.
Try using a different browser.
sorry for the late response on this.
Nice try, but as already posted in the inital message, I already tried different browsers (Chrome, FF, IE, Edge), two different hosts, and two different admin accounts.
All attempts ended unsuccessful.
Do you have simillar issues with other checked in products, like VSE for example?
Corporate Headquarters
6220 America Center Drive
San Jose, CA 95002 USA