"Waiting" during installer PUSH

Discussion in 'ESET Server & Remote Administrator' started by Altramarine, Mar 29, 2012.

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

    Altramarine Registered Member

    Joined:
    Sep 25, 2008
    Posts:
    10
    Hi,

    Perhaps this will be useful to whoever is getting the "Waiting" during package installer push.

    Here is my short story:

    I deployed a package to around 40 clients.
    around 15 of those got stuck on the "Waiting" statuso_O . I gave it 15 minutes with no progress.

    I found the following article:
    http://kb.eset.com/esetkb/index?page=content&id=SOLN2486
    that advises to run "ESET Remote Administrator Server" service as a username with domain administrative privileges.
    Sure, did that. Restarted the Service.
    Bam:argh: ! the 15 "Waiting" clients suddenly woke up and picked up the package.
    So I felt all warm and fuzzy :ninja: about this for the remainder of the day.

    Comes day two, I deployed a package to yet another 20 new clients.
    All 20 got stuck on the "Waiting" message.
    I restarted the "ESET Remote Administrator Server" service and behold, all 20 client started picking up the packages again.:blink:

    3rd day comes, the same bloody issue with a few other new clients.
    But, again, restarting the service did the trick.o_O o_O :'(

    I totally am fine with this work around, but please correct me if I am wrong, this is NOT normal.

    I have followed the documentation and beyond guildes to make sure my NOD32 server has everything it needs (all necessary open ports, domain rights, mirror setup correctly, etc)
    I cannot be the only one having this problem, any suggestions? Is this a bug? an undocumented one?

    Thanks



    ERAS (4.0.13:cool:
    ERAC (4.0.13:cool:
    ENOD32 Antivirus Business Edition (4.2.76.0)
     
  2. foneil

    foneil Eset Staff Account

    Joined:
    Dec 7, 2010
    Posts:
    255
    Location:
    San Diego
    Thank you for detailing your issue. I will forward this information to our Technical Support and Product Development teams for review. If I find out anything, I will post it here and/or update the ESET Knowledgebase article.
     
  3. kr0ss

    kr0ss Registered Member

    Joined:
    Apr 4, 2012
    Posts:
    1
    I'm actually having the EXACT same problem with a new ESET install. Restarting the service before each push is a hassle.

    I've also noticed that unless restarted daily, the "last contacted" date will grow.
     
  4. Altramarine

    Altramarine Registered Member

    Joined:
    Sep 25, 2008
    Posts:
    10
    Thanks for the reply guys.

    Kr0ss,

    Sorry to hear you got the "last connected" issue.
    I remember experiencing something similar but after adjusting the below, everything worked out fine.

    ...->ESET Kernel -> Setup -> Remote Administration:
    * Interval between connections to server (mins): 5
    * Primary server password: (make sure this one is dead on matches your "Password for ESET Remote Installer (Agent)"

    The above is what each of my nod32 clients has as config. (pushed through nod32 Server Policy)
     
  5. splansing

    splansing Registered Member

    Joined:
    Jul 7, 2012
    Posts:
    13
    Location:
    USA
    If I roll out to a large number of clients, 20, 30 or more, the installer STALLS repeatedly and I have to restart the service, which has domain admin credentials in it.

    I've had a lot of issues dealing with ESET's enterprise features so far. Here we have this killer tiny footprint AV engine, and, it would seem, an afterthought of an enterprise system that has a few flaws in it.

    This is easily the most egregious one so far. Why is the service stalling? How is restarting the service the answer? Why does it seize up in the first place?! What can I do to stop this? Can I apply an update? Can I tweak a setting? Can I do anything? Or do I simply have to check back with the console 5 times a day and restart the service until my deployments finish?

    THIS is enterprise software? I think not.
     
Thread Status:
Not open for further replies.