ENS OAS Standard Process - Folder Exclusion

[iverbuyst]

Hello,

We're having problem with the installation with AutoDesk AutoCAD 2021 which returns the message that installation could not be completed because there was a problem downloading the software.

We don't see any events in de McAfee Logs, even with full logging & debugging active, but noticed that when we disable the OAS the installations completes.

During the installations we see the creation of an autodesk folder on the c-drive so we've added this folder to the exclusions of the standard, high and low risk processes.

We launched the installation and it failed again.

When we take a look at the McAfee ENS OAS settings using the McAfee ENS Client on the computer we see that the exclusions are shown for the high risk processes but not for the standard processes.

When we manually enter the autodesk folder to the standard processes directly in McAfee ENS Client on the computer the installation works fine. 

When we force a policy collection this manually added exclusion stays visible and is not reset.

How can we get this exclusion to be active on the client side without entering it manually?

Is this normal behaviour or a bug?

Kind Regards,

Ivan

[Pravas · Accepted solution]

Hi @iverbuyst ,

The Standard, High & Low Risk exclusion are maintained separately on client as well.

Incase this is not working, please raise a ticket with McAfee Support for investigation.

Thanks

[iverbuyst]

Hi,

SR had been submitted to further investigate.

Best Regards

[iverbuyst · Accepted solution]

Hello @Pravas ,

We found the problem.

We've made a duplicate of the McAfee Default OAS Policy and started  entering all our exclusions manually and at some point we tried to enter vm* as filetype and got an "enter a valid filetype" error message so the filetype should be vm?.

When we modified this entry in the original OAS Policy, which was having issues with the exclusions, all exclusions are visible and active. When we export the "defective" OAS policy on top of the XML file we see "Migrated_EAM_General_Policies" so we suspect that an older ePO migration, from a version where * were allowed in filetypes, caused this.  

Sorry for the inconvenience.

Best Regards,

Ivan