Updated MSI Install

Hello,

I need to push out an install that is up to date over 50-100 56k frames via FTP. Once they reach their destination then I have 2-8 servers per frame that need to have Nod32 installed. Optimally I want to FTP the Nod32 installer and config xml to a server, copy it to other servers at the destination on that remote LAN, then be able to run the install and all servers connect up.

These remote destinations are isolated from the internet on a closed LAN connected to my company. I don't have any problem pushing the installer, copying it, and installing it. The problem I've run into is that once Nod32 is installed on the remote servers the version is 3832. And to get from 3832 to 4009 (as of this morning) it's over 22 megs. Each server then has to pull 22 megs over the 56k frame individually to get up to date.

So basically, My question is, how do I get an up to date installer and XML ready to go? I need to be able to push it over a slow frame, install it on several servers, then the servers connect to the Nod32 Server and only need to get updates from there forward?

 

Just wait, a new version should be released soon that should have reasonable updated bases.

 

Sounds like a good case for a Mirror server. As of 3.x, any PC running Nod32 can operate as a mirror - if you have BE.

If you don't have BE, it's probably a good case for it.

 

We have business edition installed, as well as the Remote Administrator Console. Good idea, however I'm not sure that a mirror is optimal.

I would like each server to receive it's updates without having to depend on each other. Daily updates aren't so bad, it's just that initial 21 meg push that's my hurdle for now.

 

I've opened a ticket with Eset, we will see what returns.

 

Looks like they released a new version. I opened the ticket on Friday morning and have no response, Also waiting on a response for a ticket I opened this morning. Called them but after waiting 25 minutes on hold I hung up. It's a shame their sales department has such good turnaround time when their Customer Service leaves you in the dark.

 

Your concern about the servers depending on each other can be rectified by creating two update tasks.

The first update task updates from the mirror, perhaps hourly.

The second update task updates from nod32 over the Internet as normal, and runs perhaps at 6pm? The mirror server should not be setup to update from itself.

Just pointing this out as an option.

 

Thanks,

This sounds like a good idea, however my current problem is that the update tasks are failing, I'm assuming this is because no one is logged into the server when it is trying to update. Even worse is the fact that I can't download the new client from Eset in the 1st place because it says our username / password can't be authenticated.

I have yet to hear back on my tickets, and when I call them I still get the automated message about people are having subscription issues, they recommend me opening an online ticket, which I've already done. I get tired of waiting on hold for over 15 minutes.

Once I get a word back on our login problem, finally get logged in and download the new client, get it installed, then figure out why it's not updating daily, I'll look into the mirror idea. My only concern is I don't want to have to configure separate IP Addresses for over 60 networks, let alone keeping configurations up to date, as servers we use are usually built from an image, which I'd like to integrate the install to.

One thing is for sure though, with service like this there's no way we'll be purchasing a renewal for our 700 licenses when the year rolls around, Id just like to use something until then.

 

I did finally get ahold of a rep by waiting on hold for 20 mins. Turns out that when we purchased our licenses of Nod32 they never sent us our new username and password, and the trial one expired. Now I'm manually pushing out clients to as many servers as I possibly can, but just being a couple days old each server is having to pull a meg and a half of updates, which takes a while on a 56k frame. The clients aren't getting updates either, it just sends an e-mail: "the following warning occurred:" but theres no actual error just blank after that.

However, I should post my concerns in another thread, so I'd say this is closed. Nod32 has no way to get an updated package other then when they decide to get around to it.