Sign in
Microsoft.com
 
Forefront Server Security TechCenter
 
 
 
Forefront Server Security TechCenter > Forefront Server Security Forums > Forefront Security for Office Communications Server > Forefront for OCS Issues
Ask a questionAsk a question
Search Forums:
 

AnswerForefront for OCS Issues

  • Thursday, November 06, 2008 8:45 AMEkramy Elnaggar Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
     hi ,
     
    i installed Forefront security for OCS , Beta Version: 10.2.0163.0  , and i configured it using : Microsoft® Forefront™ Security for Office communications Server User Guide Version 10.2 Published: August 2008

    i have an issue and also a question :

    Question : does it support arabic keyword and content filtering ?

    Issue : i already configured it to block certain filenames or files with certain sizes or files with certain extensions , also to block some keywords ( english keywords )

    but acually it doesn'r block anything and from incidents in the statistics it shows that the scanned or repaired or infected files and also messages are Zero ( 0 )

    note that all services are running correctly and i already make updates to it .

    so , any one can help me in this ?
    ekramy
     

Answers

  • Thursday, November 06, 2008 1:16 PMMolly Gilmore MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Hello Ekramy,

    Keywords are detected within IM Message Content and Text-based transferred files through symbolic matching so you should be able to filter on arabic words and characters.

    In regards to your filtering settings, did you set up a filter list specifically for Keywords for the filter? Make sure the filter is enabled and the detect action set to "block - prevent transfer".  If your certain your filters are configured correctly, then do you see any errors in the programlog.txt file or FSOCS messages sent to the Event log?

     

All Replies

  • Thursday, November 06, 2008 1:16 PMMolly Gilmore MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Hello Ekramy,

    Keywords are detected within IM Message Content and Text-based transferred files through symbolic matching so you should be able to filter on arabic words and characters.

    In regards to your filtering settings, did you set up a filter list specifically for Keywords for the filter? Make sure the filter is enabled and the detect action set to "block - prevent transfer".  If your certain your filters are configured correctly, then do you see any errors in the programlog.txt file or FSOCS messages sent to the Event log?

     
  • Monday, November 10, 2008 3:53 PMEkramy Elnaggar Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
     yes i set up a filter list containing some english words and assigned it to the IM Scan job , and i enabled it and choosed "block-prevent transfer "  . also i found the following errors on event viewer :


    Mon Nov 10 17:43:24 2008 ( 3996-   17), "ERROR:

    ForefrontNotificationAgent.exe.NotificationAgent.imClient_LoginDone("<System.Object

    sender><FSOIMClient.ReportSuccessEventArgs e>") - Failed to login."

    also

    Mon Nov 10 17:44:03 2008 ( 3996-   17), "ERROR: Microsoft.FSO.IMClient.dll.IMClient.RaiseLoginDone("<System.Boolean success><System.String message>") - Error occured logging in to server: 80EF0193: Forbidden."

    so what do you suggest ?


    ekramy
     
  • Tuesday, November 18, 2008 9:55 PMMolly Gilmore MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    This error is usually generated by the FSOCS IM Notification Agent. This is the component that sends notifications to IM Senders and Recipients when a  filtering rule is triggered or a virus is detected. 

    This agent is actually a client to OCS as it needs to send IM messages to other users within OCS. As a result, it needs to run under a valid OCS user account. This is set up during the installation process.

    We can validate this user information when the install occurs in the internal network, on the Front End, Standard Edition and Director server roles. When installing on the Access Edge, we don't typically have access to Active Directory so cannot verify the entered credentials. Check to make sure the user account is valid in OCS. The information you entered during the install is available in the General Options Settings in the FSOCS Admin Console.
     
  • Thursday, November 20, 2008 11:54 PMJohn Castillo - MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    1
    Sign In to Vote
    - Attempt to enable diagnostics for "Additional IM" located within the Settings - General Options page
    - Also if you view the Operate - Run Job page, Make sure the IM ScanJob state is "ENABLED" and that "Keyword Filtering" is enabled
    - Duplicate your issue again and check the logs and hopefully this will provide some additional details of the problem
    - Can you also provide the Keyword Filter you are using so I can see if there is any typos with the configurations
    John