winstonsmith84

Yes. This worked for me every time. About 3/4 of the computers would upgrade with no issues but those that failed required this step to correct it. You will have doubles of the same computer name in your license manager after doing this though it doesn't appear to take up a second license. You can just remove the duplicate. Best option is just to not update any computers at all. Skip this update and wait for the next one. I got about 130 computer up to this version but I won't be upgrading any others.

This is still a problem. Message sent.

uninstalls aren't possible. freeze on preparing uninstallation. only solution is forced uninstall via the command line uninstaller which has to be run in safe mode. this is a serious nuisance for affected PCs in other parts of the country that don't have anyone in that location to fix this.

Same problem here. Having to uninstall via the command line uninstaller tool and then reinstall manually. Afterwards the license server shows duplicate entries for the same machine. I'm avoiding this update on any further machines. There's something seriously wrong with it.

Push install and manual install will fail on 1 in 10 PCs. Affected computer will have the error "Modules update failed. Product is not activated." This only happens when installing version 6.6.2068.0. Older versions install without errors. The only way I've found to get around this is to use command line uninstaller tool and then reinstall manually. This is dramatically time consuming to update hundreds of computers one by one. Please, why is this happening? If no one knows, then I'm skipping this buggy update.

I think the issue is that the installer says finished but it isn't actually done. I send a reboot to the PC and then it comes back up and says the installer is running again but Eset never functions again. It just says the modules can't be updated because there is no license file. I have to uninstall and manually reinstall to get around this. Why does the remote admin always say an install process is finished when it actually isn't?

The install task says finished. Product is installed. Computer is restarted. Now the client install task once again says running and stays this way. Why?

Never mind. Gave up and got rid of the computer. Replaced it with another one and this one works.

This is still a problem. Cannot get this to work. Have uninstalled and resintalled and the problem persists. Tried running the following commands: sc query epfwwfpr Result was that the service epfwwfpr was running. sc qc epfwwfpr Result showed the kernel driver was set for system start and was located in the normal location The driver for this appears to be installed but it doesn't run for some reason. This computer is setup up as a training station kiosk so I had originally thought that perhaps the software that locks it down from regular users was causing the issue even though it wasn't running when Eset was installed. I've since installed it on another one of these kiosk machines with the same lockdown software and there was no issue. Eset works perfectly on the other one.

Registering callouts and filters through BFE. Detected product with firewall: no Detected Windows version: 0x601 Detected product "eea", version: 6.5.2107.1 FwpmTransactionCommit0 error 0x1a91 Added 32 (0) filters, 16 callouts, 3 sublayers, 1 providers. Exit status 0x1a91: Transaction support within the specified resource manager is not started or was shut down due to an error. eea_logs.zip

I have about 5 random PCs a day report the following error: During execution of Email client integration on the computer, the following event occurred: An error occurred while removing integration with Outlook Express/Windows Mail What does this mean exactly, should I be concerned and how do I correct this?

How do I get these ELC logs and how can I get this tool? The link provided does not work.

Can't download that rar file. The page you are trying to access is not available for your account.

Nothing? What would cause these to not work? No ideas at all?

I have one computer that i cannot get this to enable on. All other computers have no issues with this. Eset was not upgraded on this machine. Eset was uninstalled and then 6 was installed. I haven't yet tried uninstalling 6 and re-installing but for what it's worth, the one thing about this machine that is different from the others is that it is used as a kiosk and runs a program called Internet Explorer Lockdown. IE lockdown was disabled while I removed the old version of eset and installed the new one but those two modules in Eset will not turn on no matter what I do (and this is with IE lockdown still turned off). When I try to enable them my only option is Permanently Disable. There is no option to enable. How do I fix this? Is there a log file somewhere that will show what is happening?

We have software we use in our company that is being caught by Eset as a Potentially unsafe application. I need to know how to get eset to stop triggering warnings on this executable. We have Eset 6.5.2107.1 How can I use the Remote Administrator to tell eset to leave this exe file alone?

I need a way to stop a serve task as well. Any info on how to do this?

Yes ERA 5. I thought there was a way to create a scheduled scan task and say "only apply to the following group". I could have sworn I did that before but I can't remember how I did it. I know I didn't create two policies though.

I still can't figure out how to do this. I know how to schedule a scan through the policy manager / scheduler but that affects every single computer in the company. I don't want to do that. We run 24 hours. I can't have people working the night shift being hit with the scheduled scan while they're working. I have created two groups. One that is for day shift PCs and one that is for night shift PCs. I need to create two scheduled scans. One for each group so they can have their own start times. As it stands now everyone gets the scheduled scan at the same time at night and it's slowing down the night shift PCs. I tried right clicking on a group and choosing New Task but there was no option called New Task. I only get Create, Edit and Delete.

I have two seperate groups (regular PCs and one for PCs that are used late into the night). How do I schedule a full scan for one of these groups in particular? There is already a full scan task applied to the regular group which works. I want to move certain PCs to the late night group and schedule the task to start at a later time. Currently there are a small number of users that constatnly shut the scan off because they are still working. I did create another scan task but I have no idea how to apply it to the new late night group.

Is there a more thorough guide for upgrading Eset server than the one listed below? hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN2439 I've done this before but I don't remember everything I did and the process has way more steps than are listed in that article so I have no idea what I'm needing to do. I downloaded the new server and console install files and I've located my license file but beyond that I don't really remember what to do. We're on version 5.1.38 currently.

I think it was related to the size warning that popped up. I ran the "compact database" function and the error has happened again so far.

I'm finding that this file is being detected as malware and being quarantined on several machines. It's for Intel integrated graphics. Why is Eset calling this malware? So far it doesn't appear to have caused any issues by being quarantined but why is it even happening?

I try to do a configuration task (which has been working fine for two weeks now) and all of a sudden I just keep getting this error when I try to finish setting the task up. An error occurred. Error code: 20036, 11 If the error repeats, you can check the server logs for more information or contact ESET support. No idea what this is. I am getting a message that my logs are reaching 1.9GB and that the limit is 2GB. I don't know if that would have anything to do with it.

I started another push install and it just says "in progress" for over two hours. I went home. When I came back the next day it was installed. WTH? It used to take about 15 maybe 30 minutes tops to push this. The install still doesn't work correctly though. I have to manually add the update server settings and the remote admin settings on the client. It also installs the "default" policy instead of the actual one that has our license. We have a policy made that all the clients use but for some reason they don't install with it now. I can manually fix those problems each time but I don't know why it's not working now when it used to. Also, if it means anything, when I've fixed those problems the client still won't update virus definitions. It says "Cannot connect to server" even though the settings are correct and the client and server can ping each other. If I leave it alone and do nothing after a long enough time the client begins updating it's definitions. I'm starting to think part of the problem is the network itself. Communication between the Eset server and the clients must be . The package that was created for push installs must be made wrong since it's not passing on the correct policy and is using the default one instead. I sort of inherited this thing. My only responsibilty was doing push installs on new machines. I did not run the server nor did I create it. I do not know how it works.