dlb 0 Posted August 6, 2015 Share Posted August 6, 2015 I'll first start that I don't totally hate the new console. It has it's positives and negatives. The part that irks me is the lack of detail in installation failures. Case in point... I have the agent running on every PC. I successfully installed the Endpoint product on several PCs, but I was rolling the product out in stages. The last group for some reason failed to install. Checking the Client Task, it shows each PC starting the installation but the shows that it fails. I checked every log and report I could find in the console but none of them told me why. I finally found a post in the forums that showed where the trace.log was located on the client (C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs). Upon inspection, the failure was due to a missing package. Apparently there was an updated client between the installs so the original job that was duplicated failed since the package was no longer available. Seems like there should be some detail in the failures found in the ERA. If the trace.log has the reason for failure, seems logical that the ERA could find that and report it. dlb Link to comment Share on other sites More sharing options...
Recommended Posts