cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrading from agent 4.6 to 4.8 causing file issues

Does anyone know if agent 4.8 has a new scanning policy in regards to the folder c:/users/<name>/appdata/local/temp?  Our database servers use these directories to compile reports and ever since I upgraded, the times are much slower and in come cases the queries have stopped.  We had an entension exclusion but the on-access scanner is now scanning these files where before it wasn't.

To solve the issue, we needed to use a path exclusion to point below the TEMP folder.  Anything above that folder, the exclusion would not work.

Any ideas?

5 Replies
Tristan
Level 15
Report Inappropriate Content
Message 2 of 6

Re: Upgrading from agent 4.6 to 4.8 causing file issues

The agent doesn't do any scanning. All it does is provide a interface to manage all the other McAfee products installed on the computer.

If all you've done is install a new agent and not installed a new version of VSE then the first step is to double check your applied VSE policies in ePO and see if the upgrade hasn't mistakenly applied a default VSE policy instead of your standard one.

Re: Upgrading from agent 4.6 to 4.8 causing file issues

We upgarded to 5.1 at the same time.  Also applied a couple of VSE patches so perhaps that is what happened.  The policies are the same.

Re: Upgrading from agent 4.6 to 4.8 causing file issues

Would not be better to exclude by filename (using wildcards) or extension better than exclude the whole temp folder? You are opening a big security whole ....

Cheers,

Re: Upgrading from agent 4.6 to 4.8 causing file issues

That is the problem.  They are text files but when we use a .txt extension exclusion, it does not work.  We needed to use a path to the directory below the temp folder(not the temp folder itself).  This why I am confused why the extension exclusion no longer works in the temp folders.

Message was edited by: krmason on 23/06/14 9:08:10 GMT-06:00 AM

Re: Upgrading from agent 4.6 to 4.8 causing file issues

Normally by default it comes in OAS all files types to be scanned, please try the second option and include the extension .txt as a test and try to see if that works

Cheers

El mensaje fue editado por: llamamecomoquieras on 25/06/14 8:31:14 CEST

El mensaje fue editado por: llamamecomoquieras on 25/06/14 8:31:28 CEST