Monday, April 09, 2012 8:44 PM
I have sharepoint 2010 being monitered by Forefront for sharepoint 2010 I get an occaisonal hit for an Incident:
Category: File filter
Incident Name: Filedefault: *
Scan Job Name: Realtime
RMS Protected: False
Transfer Direction: Upload
I would like to keep the current file filtering settings and not get these to be see as issues, is this possible?
File filtering settings:
Microsoft Windows Executable (EXE, DLL, OCX, SYS, SCR)
ARC Archive & Compression Format (ARC)
ARJ Archive & Compression Format (ARJ)
GZip Compression Format (GZIP)
Hyper Archive Format (HYP)
Java Archive Format (JAR)
LHA/LHarc Compression Format (LHA, LZH)
PKLite Compression Format
RAR Archive & Compression Format (RAR)
ZOO Compression Format (ZOO)
TAR Archive Format (TAR)
Unix Compression Format
Audio Video Interleaved (AVI)
MPEG Animation Video Format (MPEG1)
MPEG Layer 3 Audio Format (MP3)
Quick Time Video Format (QT)
Waveform Audio Format (WAV)
Microsoft Windows Animated Cursor (ANI)
Microsoft Windows Icon Image File Format (ICO)
Lotus Notes Database (NSF)
MacBinary Format (BIN)
Java Bytecode (CLASS)
Object Code Format (OBJ)
Microsoft TrueType Font (TTF)
Type 1 Font (PFA, PFB, PFM)
Microsoft Help (HLP)
Microsoft Help Index (CHI)
Microsoft Object Code Library
Microsoft Shortcut (LNK)
Microsoft Type Library Format
Microsoft Windows Program Information (PIF)
Microsoft Windows Write Format (WRI)
Tuesday, April 10, 2012 6:27 AMModerator
Thank you for the post.
What is the Forefront software version? And What specific filters are you trying to configure?
Nick Gu - MSFT
Tuesday, April 10, 2012 3:27 PM
Forefront Protection 2010 Sharepoint (version 11.1.394.0)
I would like to verify that the incident is a actual issue and not just being registered as a issue by Forefront due to a filter.
The "folder" that is reporting the issue was created by Office Web Apps, the incident email shows the sharepoint \system as the user who caused the incedent with no other information given. I am thinking it is due to the .ODTTF being seen by the file filter that is for Microsoft TrueType Font (TTF). But if that is true then why do I not have this incident more often than four times in the past year?
Monday, April 16, 2012 2:00 AMModerator
Thank you for the update.
Please update FPSP to the latest version rollup2(11.1.413.0) and see if any help.
Nick Gu - MSFT
- Proposed As Answer by Nick Gu - MSFTMicrosoft Contingent Staff, Moderator Tuesday, April 17, 2012 2:47 AM
- Marked As Answer by Nick Gu - MSFTMicrosoft Contingent Staff, Moderator Wednesday, April 18, 2012 5:34 AM