Campbell IT 4 Posted October 30, 2018 Share Posted October 30, 2018 ESMC is showing 14 of my machines failed to install when they are in fact, installed, activated, checking in and updating. Any ideas? Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 434 Posted October 30, 2018 ESET Staff Share Posted October 30, 2018 Hello, Can you clock on the individual computer, and show the "history" of the task execution progress on any of those computers? It might actually correct itself after some time, but it would be helpful for us to be able to see the detailed progress. Thank you. Link to comment Share on other sites More sharing options...
Campbell IT 4 Posted October 30, 2018 Author Share Posted October 30, 2018 Here is a screenshot of the History of one of the machines. Second screenshot is the status from the Details page. Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 434 Posted October 31, 2018 ESET Staff Share Posted October 31, 2018 It seems to fail on activation. What is the license used for the activation? Does it support more products than one? Is it a bundle? But in this case, it looks that product is correctly installed and running, We might need an agent trace log, from the moment of the failed install / activation, to be able to precisely identify the cause of the fail. Have you submitted a ticket? Link to comment Share on other sites More sharing options...
Campbell IT 4 Posted October 31, 2018 Author Share Posted October 31, 2018 It is a bundle license. I have had a certain number of machines that would not automatically activate. I had to create an activation task for those machines. I have not submitted a ticket. I don't know that it is an urgent issue if I can activate the machines and they are checking in. I just wanted to post here in case it was a known issue. Should I create a ticket anyway? Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted October 31, 2018 ESET Staff Share Posted October 31, 2018 According to screenshot, there is no problem with activation itself, but in logic that executes it after product installation. It seems that product is not started in time once installed and that results in this state, but it is hard to confirm without full verbosity trace logs enabled before installation attempt. What type/platform of product was installed? Was it clean installation or upgrade of previous version? Link to comment Share on other sites More sharing options...
Campbell IT 4 Posted October 31, 2018 Author Share Posted October 31, 2018 These are all 32 bit Windows 7 physical machines upgraded from ESET Antivirus 5.x. Link to comment Share on other sites More sharing options...
Recommended Posts