Client Config file

Discussion in 'Other ESET Home Products' started by a_kerbouchard, Apr 17, 2008.

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

    a_kerbouchard Registered Member

    Joined:
    Apr 17, 2008
    Posts:
    35
    If we have 21 branches each with a Remote Administrator/Mirror server at them for the clients at each branch. Will I need to create 21 separate config files so the clients will update from their respective server?

    Thanks,
     
  2. bdmc

    bdmc Registered Member

    Joined:
    May 11, 2006
    Posts:
    55
    No, you can have 1 config for all sites. Point your NOD32 config to something like NOD.domain.com.

    Then create DNS CNAMES that point to the ra/mirror in each site. Turn on Netmask Ordering in your DNS server.

    Now your sites should all get the local ra/mirror server when they lookup NOD.domain.com
     
  3. a_kerbouchard

    a_kerbouchard Registered Member

    Joined:
    Apr 17, 2008
    Posts:
    35
    Problem with this is we only have 2 AD sites, not one for every branch.
     
  4. bdmc

    bdmc Registered Member

    Joined:
    May 11, 2006
    Posts:
    55
  5. a_kerbouchard

    a_kerbouchard Registered Member

    Joined:
    Apr 17, 2008
    Posts:
    35
    I was able to fix that by the mac-address rewriting in the server config. Our old symantec corporate antivirus had that problem, but it did not check the number of clients to your license.
     
Thread Status:
Not open for further replies.