2.7 to 4.0 - Little Lost

Discussion in 'ESET NOD32 Antivirus' started by marley1, Apr 22, 2009.

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

    marley1 Registered Member

    Joined:
    Mar 13, 2009
    Posts:
    30
    Hey all this deals with the business setups. When I first became a reseller 2.7 was out so I was putting 2.7 on the servers (mostly SBS 2003 with Exchange running) and pushing out 2.7 to the clients with a package. This was easy, I created the Mirror on the server in the Nod client not ERA and used the same package for all the setups.

    Now 4.0 is out and I would like to be using that. Is 4.0 recommended on servers running Exchange or is 2.7 still recommended?

    Also if using 2.7 on the server do we still create mirror using the ESET client or through ERA.

    I was having the hardest time configuring a package for 4.0 clients. I looked through it but saw no spot where to configure the LAN IP of the Mirror server.

    I saw in ERA Console that you can make a mirror in that, but saw no where in the XML file to enter the lan addy and port of hte server.

    Can someone fill me in on this. I tried calling ESET Reseller Support a 619 number and was on hold for about 45 minutes before I left a message.

    Thanks,
    Dan
     
  2. YeOldeStonecat

    YeOldeStonecat Registered Member

    Joined:
    Apr 25, 2005
    Posts:
    2,345
    Location:
    Along the Shorelines somewhere in New England
    On SBS you still want the 2.7 client, as XMON is currently only 2.7, you cannot put 3 or 4 on the machine and run XMON 2.7 inside of it.

    The mirror is now setup through the RAC, go to the tools drop down menu, you'll see where you create the update mirror now. There's also a checkbox for creating a subfolder (nod32v2)in the mirror for 2.7 clients on your network....which you'll point your servers 2.7 to for its updates.

    Point your 2.7 clients to your mirror but include the subfolder in the path.
    http://192.168.10.11:2221/nod32v2
    Point 4.0 clients to your mirror just like you did with the old way.

    The old update mirror used to run default on port 8081, which conflicted with Sharepoint on SBS, so I'd customize the port to 8088. 4.0 update mirror defaults to port 2221 for updates, which so far I've not seen any conflict with on SBS, so I leave it at default. Probably don't even need the enter the port in that case.
     
  3. marley1

    marley1 Registered Member

    Joined:
    Mar 13, 2009
    Posts:
    30
    Thanks YeOlde.

    So you can configure it for 2 different ports for both v2 and v4?

    The problem I was seeing is where the hell do you tell it in the XML to grab the mirror from?

    When I go to XML Editor, At the top is Version 2, then one below is Eset Smart Security/Nod32 Antivirus. I imagine the one for Nod32 Antivirus is the one I want to configure for V4 clients, but I do not see a spot for the lan mirror.
     
  4. AJStevens

    AJStevens Registered Member

    Joined:
    Aug 27, 2008
    Posts:
    97
    Location:
    Surrey, UK
    marley1,

    Configure the Mirror and Mirror for NOD32 version 2 on the ERA server.
    Go to Server Options, Updates and enable the Mirror settings and tick "Create update mirror for NOD32 version 2 products"
    Then go to Other Settings tab, "Edit Advanced Settings" button.
    ESET Remote Administrator
    |- ERA Server
    |- Setup
    |- Update <- Ensure this is setup and getting updates from Eset using your license username and password.
    |- Mirror <- Enable/set options to your requirements
    |- Mirror for NOD32 version 2 <- Enable/set options to your requirements


    Then for v2 clients push out the following settings:
    NOD32 version 2
    |- Update module
    |- Profile (My profile)
    |- Setup
    |- Update server <- Edit this to something like http://192.168.16.1:2221/nod32v2

    Then for v3/4 clients:
    ESET Smart Security, ESET NOD32 Antivirus
    |- Update module
    |- Profile (My profile)
    |- Setup
    |- Update server <- Edit this to something like http://192.168.16.1:2221

    http://192.168.16.1:2221 is the address and port of your ERA server, if you server is called SBS1 you could use SBS1:2221. Port 2221 is the default and recommend, ensure this is not blocked by firewalls.

    The important thing to note is you NEED /nod32v2 on the end of the server address for v2 clients only. Both clients use the same port, but use different folders for their updates.

    That should be it, you don't really want mirrors on the clients unless you have some specialist need, but you can enable this by importing your business license .lic file into the client, you'll then be able to setup the mirror, but you will have to do that at the client, not through ERA.

    Finally, for NOD32 Version 2 that's running on your Exchange server, just have this update itself and not bother with a mirror, or pointing to the ERA mirror as I don't think that will work.
     
  5. marley1

    marley1 Registered Member

    Joined:
    Mar 13, 2009
    Posts:
    30
    Thanks man I kept looking in the old spot nder profile update.

    so for the server with era installed just have the nod32 pull the update right from eset not off the mirror?

    I should mention this server is sbs without xmon installed but I figure most people are still running 2.7 on servers?

    I will try in a little have to go drop off a machine and find out why another server crashed
     
  6. AJStevens

    AJStevens Registered Member

    Joined:
    Aug 27, 2008
    Posts:
    97
    Location:
    Surrey, UK
    For the server with xmon installed, pull it off directly from Eset.

    I'm surprised if you have an SBS server you don't have Xmon.

    Most believe 2.7 is best for servers, however we put version 3 on all servers, except Exchange/SBS servers (can't load 2.7 and 3 on the same server).

    If the server is running just basic NOD 2.7 then you can have it update from the ERA Mirror. Be sure the ERA Update settings are correct and working, version 3.0.105 is great for giving more information about this, so check you've got the latest version of ERA Server and Console.
     
Thread Status:
Not open for further replies.