Blocked URL addressing policy not propigating

Discussion in 'Other ESET Home Products' started by SmackyTheFrog, Oct 6, 2011.

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

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    I added a number of malicious URLs in to our domain policy a few days ago, but the clients aren't taking it. When I request a client configuration, the "List of blocked URL addresses" entry is marked as grey as if no settings are being applied to it, but that isn't how the policy is configured. The policy change has been in effect for a number of days now so the clients should be refreshing at this point. Has anyone else gotten this to successfully work through ERAS policy? I can manually add them in directly to a client and that works, but doing this through a configuration task just isn't as clean as policy methods.
     
  2. JesusV

    JesusV Former ESET Support Rep

    Joined:
    Jan 21, 2010
    Posts:
    93
    Adding addresses to "List of blocked URL addresses:" only applies to version 3If you are using Version 4 then the area to add addresses for blocked/allowed addresses would be under Web Access Protection > Http Address Management.

    Let me know if this works for you.

    Regards,
    Jesus
     
  3. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    That got it. Thanks for pointing me in the right direction.
     
  4. JesusV

    JesusV Former ESET Support Rep

    Joined:
    Jan 21, 2010
    Posts:
    93
    Glad It worked.

    Regards,

    Jesus
     
Thread Status:
Not open for further replies.