Jump to content

Mihlfeld

Members
  • Posts

    5
  • Joined

  • Last visited

About Mihlfeld

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    USA
  1. I was noticing that inside of ESET Remote Administrator and the list of policies that there is no built-in or default policies to use for Mail Security for Microsoft Exchange Server. Are there any default good starting policies available out there which would be good starting points to use for this product? I'd prefer not to just build one from the ground up and would like to start with a good baseline and tweak from there. Thanks.
  2. I found the svchost.exe process (C:\WINDOWS\System32\svchost.exe -k netsvcs) that is responsible for BITS, and see it's responsible for maybe about 20 services after poking around a bit in Process Explorer. How exactly would I go about adding this as an exception without doing all of svchost.exe processes?
  3. I am uncertain what you are referring to when you say installed modules. Can you elaborate?
  4. I more or less have the exact same issue that was posted here back in December: hxxp://www.wilderssecurity.com/showthread.php?t=338009 I, too, am running Microsoft WIndows Server Update Services (WSUS) 3.0 SP2 on a 32-bit Windows Server 2003 R2 machine. With protocol filtering enabled, I repeatedly get these two errors in the Application log in Event Viewer when it attempts to download updates: ===== Event Type: Error Event Source: Windows Server Update Services Event Category: Core Event ID: 10032 Date: 7/23/2013 Time: 5:36:37 AM User: N/A Computer: WSUS-SERVER Description: The server is failing to download some updates. For more information, see Help and Support Center at hxxp://go.microsoft.com/fwlink/events.asp. ===== Event Type: Error Event Source: Windows Server Update Services Event Category: Synchronization Event ID: 364 Date: 7/23/2013 Time: 5:28:36 AM User: N/A Computer: WSUS-SERVER Description: Content file download failed. Reason: The server does not support the necessary HTTP protocol. Background Intelligent Transfer Service (BITS) requires that the server support the Range protocol header. Source File: /msdownload/update/software/defu/2013/07/am_delta_patch_1.155.325.0_717c923552c0311b07a5ccd36c48a9c1407028ee.exe Destination File: d:\WSUS\WsusContent\EE\717C923552C0311B07A5CCD36C48A9C1407028EE.exe. For more information, see Help and Support Center at hxxp://go.microsoft.com/fwlink/events.asp. ===== I am running ESET File Security version 4.5.12011.0. I have added the protocol filtering exception mentioned in the link above: This, however, is not solving the problem for me. Disabling protocol filtering does work for me, but I'd rather leave it on and fix this proper. Are there any ideas what more I can do to resolve this problem short of disabling a feature in ESET File Security on this server?
×
×
  • Create New...