NWDreamer

I'm afraid I can't contribute to the original question since I'm about as new to ERA6 as they come, however I can comment on the sentence I quoted above. From both what I read and what I saw with our own console, the dynamic group computers gets populated from the hierarchy of the AD on the server (i.e., you can see them in the console, but they are kind of dim and without icons or highlighting). Only once I was able to deploy an ERA Agent to the client was I able to see the Agent icon (as well as others that describe the client like desktop, file server, exchange server, etc.).

I checked those before I posted here. From my original post: I'll check out your last point and see what I can find. Thanks again for the ideas!

Hi, thanks for the reply! Yes, we just upgraded to ERA6 so I am new. The targets were definitely connecting to the ERA Server, in fact, manually deploying the ESET upgrade on a client is reflected in the Computers tab as managed (and the last connection time to be updated is, well, updating!). Although I set each task's trigger to run "As Soon As Possible," in the client task information the summary line would say "no" under Planned but each detail line under that would say "Run As Soon As Possible." Since, unlike with the Server Tasks area, there's no "Run Now" button, I couldn't do much except watch them eventually expire. I couldn't find any reason why they won't run. Also thanks for confirming my guess on the misleading numbers. I'm already finding out that, for whatever reason, sometimes just rerunning a task that gets an Access Denied or Failed Task can cause it to be successful. Since I'm new, I'm just trying to determine if I did something incorrect to cause the client tasks to not run or if it's something else and I'll have to update each client manually.

Hi, I'm a long-time IT guy who just started working last week for someone else after many years of being in business by myself. Needless to say, I'm new in their environment and with their tools so this question may simply be a learning issue. For all of the below I followed the steps I found from ESET. The task for yesterday was to use ERA to first deploy the ERA Agent to all the clients. After a couple of tests I sent the main task off to 64 clients (of which the detail of the results says 26 Denied Access, 40 Failed Task and 38 were successful - not sure how it came up with 104, but that's a different question). Next I tried a test of setting up a couple of Client Tasks to deploy the update using the directions that can be found here: hxxp://support.eset.com/kb3605/ Although each one used the trigger type "As Soon As Possible," each one showed up as Planned: "no" even though the detail showed it was set to run ASAP. Since there was no "Run Now" button like I found with the Server Tasks, each eventually timed out with the error "Failed to start task." A quick search of the forums found other things I ran into, but not this one so I'm hopeful that it's simply a learning issue on my part. Thanks, Craig