Multi Site installation

Discussion in 'ESET NOD32 Antivirus' started by reflux, Apr 16, 2010.

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

    reflux Registered Member

    Joined:
    Aug 16, 2006
    Posts:
    27
    We are just about to move from Nod32 2.7 to V4 and previously we modified the server name in the registry to point it at the local server for updates, we have 150 locations. In the current version of Nod32 the registry settings are protected by nod and we are unable to modify the url. What is the best way to force a client to connect to their local server for updates?

    Cheers

    Jason
     
    reflux, Apr 16, 2010
    #1
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,456
    Try pushing an installation package with a correct ERAS configuration to the clients.
     
    Marcos, Apr 16, 2010
    #2
  3. reflux

    reflux Registered Member

    Joined:
    Aug 16, 2006
    Posts:
    27
    We were wanting to push out the installation through SCCM. Remember I have 150 definition servers. I don't want 150 different configs.
     
    reflux, Apr 17, 2010
    #3
  4. Rmuffler

    Rmuffler Former Eset Moderator

    Joined:
    Jun 26, 2008
    Posts:
    1,000
    Location:
    Bismarck, ND USA
    Hello Jason,

    The solution for your question would be to disable self-defense.

    Disable self-defense then pull the configuration with it disabled and push that configuration out to your other machines.

    Thank you,
    Richard
     
    Rmuffler, Apr 20, 2010
    #4
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.
    Accept Learn More...