Server 2003 / 2008 recommended settings

Discussion in 'ESET NOD32 Antivirus' started by duijv023, Aug 15, 2011.

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

    duijv023 Registered Member

    Joined:
    Feb 16, 2006
    Posts:
    230
    Location:
    Rijnsburg, Netherlands
    As we all know, this is how ESET recommend us to configure a server that is not used as a workstation.

    But I have several servers that communicate e-mails with a software to process electronic transactions. And some of these servers also run IIS to feed an external service like a webshop e.g.

    Should i configure other things like protocol scanning as well? Or not?

    Greetings from Holland
     
  2. dmaasland

    dmaasland Registered Member

    Joined:
    Nov 10, 2010
    Posts:
    468
    On 2008 servers you would normally rename the WFP driver to avoid the driver conflict (BSOD) issue. This also stops the protocol filtering from working alltogether.

    Alternatively though, I would suggest waiting for the final release of ESET File Security for Microsoft Windows Server as it has automatic exclusions (Also for IIS).
     
  3. duijv023

    duijv023 Registered Member

    Joined:
    Feb 16, 2006
    Posts:
    230
    Location:
    Rijnsburg, Netherlands
  4. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,411
    You needn't rename the driver unless you experience issues like system unresponsiveness or BSOD. However, I'd suggest you do so as a preventive measure as the servers are most likely critical. This does not apply to Windows 2003 Server which doesn't support Windows Filtering Platform, however.
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.