Exchange XMON Creating Large Temp files

Discussion in 'Other ESET Home Products' started by aread, Jun 19, 2007.

Thread Status:
Not open for further replies.
  1. aread

    aread Registered Member

    Joined:
    Jan 30, 2007
    Posts:
    3
    Hi all,

    Our exchange server some times creates large (500MB+) files in the C:\WINDOWS\Temp directory. These files are deleted, so I imagine they are used as part of teh scanning process.

    Can I configure NOD to use an alternative location. I'd rather these files weren't written the the C: Drive.

    Also, the largest file I can see transferred around the time I saw one of these large files created was 1MB. So why would a 500MB file be created?

    Regards,

    Andrew
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Hi Andrew,
    NOD32 only creates temp files when scanning inside archives. It could be that a so-called archive bomb resides in the Exchange store which causes NOD32 to create large temp files during extraction. As for the option allowing you to customize the temp folder, it was introduced in XMON 2.71 (currently beta, downloadable from http://www.eset.com/xmonbeta).
     
  3. aread

    aread Registered Member

    Joined:
    Jan 30, 2007
    Posts:
    3
    Thanks for the response.
    I'll await a production release of 2.71
     
Thread Status:
Not open for further replies.