theskyisthelimit99

I have a couple of things going on here i believe.. For instance.. i have several 6.2 clients out there that arent getting the task to update to the 6.6 client (i just replaced the old file with the new one and created a new task to push this to "workstations" asap).. Even on those machines, though, i can see they are set in the tools... proxy to point at the eset remote admin server.. On the one of the machines.. i cant even find the machine workstation name in the eset remote admin tree anywhere, which is odd (i verified they had the agent installed as well, which is an older agent, unsure if the agents need updated ever or how that part is supposed to work).. Any thoughts or suggestions?

On our domain we run version 6.2 through 6.6 of the client which gets distributed through the remote admin tool on the server. Several users report after rebooting that disk utilization sky rockets on logging in and stays that way for at least 10-15 mins.. disabling the AV doesnt help when it has already occurred. Is there a known issue or work around to this? The client machine is windows 10 1703 x64. Thanks in advance

As far as I know, when i set this up, it was AD integrated, though looking through settings on the console, I dont see how to verify this or change it if not? EDIT: appears there is a task under server tasks - static group synchronization, not sure if this one is related to the issue, but says it was last run in aug (when i installed 6.x)..

Curious question for everyone.. Given how this one update affected one service on a local domain.. maybe this is a stupid question, but would it make sense to blanked exclude all local servers with key services (exchange, sql etc) from the web and protocol filtering, or perhaps that opens up too many holes?

Any idea how to tell which policies? I created and applied one for sure, unless there are defaults. Or it's related to multiple nics showing as machines

I also have the same issue with new machines going to lost and found.. was there ever a fix for this? (and duplicate machine names due to more than one nic)...

Same issue here, did you ever find a solution..

We are running 6.x of the remote admin console server... i have a workstation policy in effect.. i have the agent deployed via gpo, then the eset console detects new agents and auto installs the clients.. However, upon doing so, 4 smart scans start up at once on the new client.. i'm not sure why.. Any thoughts on where to look first? Thanks in advance

I recently changed part of the workstation policy (exclusions for ips under web and email).. it seems that some clients aren't seeing the change yet on their machine, 4 hours later? Is there some way to force this or figure out why this is going on? Thanks in advance EDIT: appears the affect machines were in Lost and Found.. i have since moved to workstations.. not sure why they ended up there? (do new clients auto get put there?)

I'm running version 6.x of the server side and a recent update breaks opening office documemts from sp 2013, confirmed by uninstalling the client, disable didn't help At least one other case of this has been reported elsewhere Is there a fix? Excel will say contacting server and get stuck Thanks

I've been trying to test my GPO deployment of the agent to new workstations.. so i have a workstation i created.. new name, joined the domain.. ran the GPO installer just fine, agent installed too.. But in the ESET admin tool, i dont see the workstation.. i tried clicking gear and doing a "scan" but that didnt help.. How are workstations populated.. maybe every 12 hours? whats the refresh rate? Is there a manual way of forcing it? Thanks

Actually, i cant seem to find the option you have for first connect to console etc.. I click my OU for workstations.. then new tasks.. task software install.. the only option for the static group "workstations" lists trigger type static group and Execute asap once then join the "workstations group".. I even tried creating a dynamic group, though one for "no agent installed" and set the parent group to be "workstations", for some reason it didnt populate the machines not installed, but all machines pretty much that had an agent.. something is amiss Yes, those options for the new task are OK. Once you complete all the settings in the task and save it any device that is either in that group or gets placed in the that group will have that task run against it. This assumes that the agent is already installed on the PC. I have found that if the task fails it will run the task again at a later time. Not sure if the time is hours later, next time it checks in based on your agent connection interval or if it is once a day. If you want to adjust the Expiration date select the static group by checking the box in the target list and click the Assign Trigger button. So are you saying that i basically click admin.. Groups.. then in the middle tabs.. Tasks.. New Client Tasks at the bottom.. Task Category ESET Security Product.. Task.. Software Install Target (default, all workstations) Settings.. antivirus in my case Under Target.. if i check off Static Group, i get the option to assign a trigger, I think what you are saying is that, if i leave it alone, "as soon as possible", it will NOT try to install the client AV software if its already installed? That is, i dont see a way to get it to say like yours does, trigger first time joins the group (i'm assuming this is just your description)?

Actually, i cant seem to find the option you have for first connect to console etc.. I click my OU for workstations.. then new tasks.. task software install.. the only option for the static group "workstations" lists trigger type static group and Execute asap once then join the "workstations group".. I even tried creating a dynamic group, though one for "no agent installed" and set the parent group to be "workstations", for some reason it didnt populate the machines not installed, but all machines pretty much that had an agent.. something is amiss

Ah ok, so creating a task that basically says, if client agent is installed, a few minutes later fire off the client antivirus install? How bout on the agent install itself.. do you define yours in gpo somehow.. maybe a software installation package that has this for the command? msiexec /qr /i "\\servershare\agents\Agent_x64.msi" ALLUSERS=1 REBOOT=ReallySuppress P_CONNECTION_CHOSEN=Host P_HOSTNAME=ServerName P_PORT=2222

yeah i saw that that could be done.. i was just trying to figure out, how in the client's settings, they were getting the update server to be the local server.. or is this maybe initially set by the agent and when the client installs it just auto defaults to it.. meaning that really, nothing client side is set in a policy until you define one either way?

Ok, but which policy.. i'm assuming i go under policies then set it there, but there are a ton of policies, i'm not sure which is the main one workstations get (by default)?

Yeah i hadnt realized the need for the mirror (AV installation on Vsav02 with mirror option) for now... Ok, so in policies i dont see where this setting is coming from.. i'm not sure which policy is the one that all the workstations are getting.. i've gone through quite a few and looked for the option that specified the manual server name.. i will change it to automatic (internet) once i can find it?

I'm not sure i follow the first part of your question? I ran the full Eset v6 installer, it installed everything, apache, sql etc.. Are you saying there is another admin portion that needs installed, related to the Endpoint AV? I havent set up a mirror .. the proxy setting/update server setting i referenced, is showing up on the client ( i expected the vsav02:2221 but not the proxy) Are you saying I would need to install the EndPoint Antivirus on the server where the updates point to (vsav02)? In this case, i wouldnt install the endpoint AV for file server package then? Then enable mirroring?

I've installed the new V6 server portion.. forced out client agents via the webconsole, as well as the AntiVirus Endpoint through the console.. All of my clients aren't updating, nor will they update if you do a manual click on the update button.. throws the error.. Looking in the settings on the client.. I see it references my server: http:\\vsav02:2221 and there is also a proxy set to the ip of the server (these were autoconfigured).. Is there some step i'm missing for this to fully work? Thanks in advance

I'm curious what everyone is doing to update their clients to Eset v6.x? As of now, i've just gone through the interface and pushed out agents on machines that are listed in my workstations OU group.. however, this only works if those machines are online.. I saw that the agent could be pushed in gpo via software installation policy.. but i'd rather not force that out, especially if a client already has the agent (unless it stays silent as with the manual process).. Then on top of this.. once the agent is installed, i have just been checking everyday and doing a re-push on the Antivirus Endpoint client, which is also tedious.. At this point i'm guessing the only real way to ensure client workstations have AV is to push these out via software installation GPO or run a batch file at login, short of manually continuing to check and install? Thanks in advance

This seems to work for the agent.. but maybe i'm missing something here.. how do i deploy the endpoint antivirus.. i had assumed the agent would install then install the endpoint antivirus as a result.. is there a second step to be done in the console to make that happen?