Client Installation Task Failed -- But only partway?

[chockomonkey 1]

I'm trying to use ERA to deploy File Security to 2 hypervisors and a domain controllers. Unfortunately, the task fails ambiguously. 

I say ambiguous because all the information i'm given is that the task failed. Let me point out that it'd be immensely helpful to have more information in the task execution area. even a link from the failed area to a report or a log file would be an improvement. These things existed in ERA5, and should be in new versions of your software.

Searching for information as to why, I generated a report which further confused me:

Here you can see my two hypervisors. For some reason when I generated the task, there was a task for Security Product, as well as Operating System. Looking back at the Admin section, I can only assume this is because when I click onto one Software Install section, two are indeed selected, one for Security Product and the other for Operating system. If anyone can explain this bizarre behavior, that'd be great. 

So, at this point in time it seems that my Deploy File Security Task, while failed, did succeed in at least some of its capacity. Supporting this is the fact that the File Security icon now appears near my hypervisors:

However, the software does not appear to be present on either (I have rebooted them both):

What further confuses me, is that as you can see above, there's an alert on VHOST. The alert is that the product is not activated:

This seemed silly, but nevertheless i went ahead and attempted an activation task, which failed as well.

Lastly, when I look in the log files (again, this manual step should NOT be necessary), I see a lot of this, which I can only assume is related to my issues, but I have no idea what to do about it:

Please help! What used to be a simple deployment of software in ERA < 6, is now a major time-consuming and confusing mess! 

Thanks for your time.

 

Edited January 16, 2018 by chockomonkey

[chockomonkey 1]

I hope the length of this post isn't scaring people away form helping.. I have purchased file security, but am currently unable to use it because ERA will not deploy it. 

Help!

[MichalJ 434]

Can you please post “execution history”, for the task results “software install” from one computer? It looks to me, that the weird results are caused by actual installation working, but subsequent activation failing. Have you tried to activate EFSW manually? Is the license you have really eligible for activation of EFSW? 

[chockomonkey 1]

Thanks for offering to help, MichalJ--

I'm almost certain my licenses are okay:

Here's the Execution history for my Deployment task:

I have not tried to activate manually, because the application does not seem to be installed on any of the above machines. All that is installed on each is the ESET shell, which I'm guessing comes with the Agent, which did properly deploy.

[MichalJ 434]

Can you click on any of the entries in the task list and choose the “history” option? That should tell you what went wrong. ESET shell is part of EFSW, which might indicate the deployment went OK. Was any older EFSW version installed there before? 

Edited January 17, 2018 by MichalJ

[chockomonkey 1]

Ohh, okay. I see what you mean now, and it does look like it was installed: 

 

 

[chockomonkey 1]

So, I think i figured out what i did. This is the package i installed, quite by accident actually:

So now my question is: Due to the Core product being behind 2 versions, is it safe to use? Can it be activated? 

Actually based on this article https://support.eset.com/kb2789/?locale=en_US&viewlocale=en_US, it seems that i should uninstall this and proceed with regular EFSW, which unlike this version can be administered via ERA 6+

Edited January 18, 2018 by chockomonkey

[MichalJ 434]

EFSW 4.5 is a legacy product, and if the system is older, I would recommend to uninstall it, and install the newest version. You can install EFSW 6 also in setting recommended for the CORE systems: http://help.eset.com/efsw/6.5/en-US/index.html?installation_cmd.htm

EFSW 4.5 is manageable via ERA, and it should be possible to activate it. However, in this case, the product activation is done via ERA agent, which activates on behalf of the File Security, and converts the license into the format, that was used by the old product versions (it embeds the old license credentials, and license file into the product configuration). I Assume, that something wrong happened in that process.