Distribution of Installation packages

Discussion in 'ESET NOD32 Antivirus' started by coiter, Sep 29, 2009.

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

    coiter Registered Member

    Joined:
    Mar 4, 2008
    Posts:
    37
    Hi

    I have searched and searched but i dont seem to find any answers to my question, so i though i should ask.

    I have a simple setup of 1 main ERAS server, and 3 replica servers on different locations.

    I have just created now a new package with the 3.0.694 version of NOD on the Main ERAS server to be distributed on the network.

    How can i make sure this installation package is also on the replica ERAS servers without having to manually transfer the file and create the package there manually.

    Isnt there some automatic setup for transfer of new packages the same way a virus definition is replicated to the lower tier servers?
     
    Last edited: Sep 29, 2009
  2. WayneP

    WayneP Support Specialist

    Joined:
    Apr 9, 2009
    Posts:
    339
    Hello coiter,

    Packages do not replicate to lower servers, as this could possibly take up a lot of bandwidth. The packages need to be created on each RA Server and pushed out from there.
     
  3. coiter

    coiter Registered Member

    Joined:
    Mar 4, 2008
    Posts:
    37
    my replica servers is on the same WAN link, so if i download them manually there or send them by means of ditribution, it would take the same amount of time, so for me it makes no difference.

    just the time having to redo the same package all over place, not to mention what it would be like if i had 50 replica servers and having to manually do them all.

    there gotta be an easier way of doing it.
     
  4. WayneP

    WayneP Support Specialist

    Joined:
    Apr 9, 2009
    Posts:
    339
    You can save the configuration xml for the package and just use that for the settings. This way you will only have to add the package and the xml file and not have to go through the whole configuration.
     
Thread Status:
Not open for further replies.