ShaneDT

ERA 6.3 doesn't automatically update for daylight saving? When I setup my ERA server I noticed the time being reported by agents and the time of the server were out of sync by an hour. So I clicked the Administration link in the top right corner, disabled 'Use browser local time' and left it with the correct time zone and the 'Daylight Saving Time' option enabled. All was now correct. Our daylight saving ended on the weekend (Sydney, Australia), and I've just noticed that the time is out by an hour again. So I've now unselected the 'Daylight Saving Time' option and the last connected time for agents is now showing correctly again. The server is set to the correct time zone etc but with 'Use browser local time' enabled the time was out by an hour during daylight saving. I just tested re enabling 'Use browser local time' and the last connected time is showing correctly now that daylight saving is over. ??

Maybe I'm missing something, but it seems to me the threat reporting in ERA is next to useless. OK so it tells me a computer at a certain time experienced a threat, it generally tells me the virus name, but that's about it. I want to know what the folder path and file name were. I want to know what process triggered the alert. I don't want to have to go to the client to find out this information. Also looking at a Firewall / Web Threat Detection on one of my customers ERA servers. Again other than the time and computer, that's all the info I'm given. How about what browser, what website, what type of threat, was it an exe or some other form of code. All this information should be easily accessible in ERA without having to click through multiple site pages or menus and without having to go look on the actual client.

Seems to be a problem with the forum search feature. If I try to search "Windows 10", all I get are results for the word 'Windows'.

Looks like I found the problem. It was inheriting Proxy Server settings under \Tools\Proxy Server\ from the default ‘Security Product for Windows – HTTP Proxy Usage’ policy. After applying the Force flag to not use Proxy Server in this section of the settings in the policy for this computers static group, then restarting the computer (required), I was then able to run the activation task successfully from ERA. Going to uninstall EES and then re test deploying from ERA to confirm all is now OK.

Yep can access that site fine, brings up an xml 'Unsupported Content-type: unknown' message. I did try to manually enter my licence key on my main PC which wouldn't work, the licence key is of course for EEPA. There shouldn't be anything being blocked outgoing, and as said the agent is connecting back to ERA fine, and ERA can send tasks to the client that run fine, just cannot activate.

I've been trying to get this to work for several days now, and assumed there must be something wrong on my PC, so I built a clean Windows 7 Pro PC, installed all available MS updates, along with Microsoft Security Essentials, and nothing else, but still having the same problem. I've setup an ERA6.3 server running on W2012R2 hosted on Microsoft Azure. I then installed EFS on this server and all appears fine. I created an agent install package from the ERA console and can successfully run this on multiple computers which then successfully connect back to the hosted ERA server, continually as expected. At this point I only have port 2222 open to the hosted ERA server. I then run a standard software deploy task, selecting my licence and EES from the repository. A few minutes later I see in Task Manager on the client the software downloading, and then the software installs, but once installed it reports 'Product is not activated'. Also in ERA it reports the install failed. So I create a task to activate the software. These tasks continually fail. I can send a 'Scan' task to the client from ERA and EES on the client begins scanning the system a few minutes later. So the agent is successfully reporting back to ERA and successfully receiving commands/tasks from ERA, yet the licence still fails to activate. My licence is Eset Endpoint Protection Advanced, which includes EES. There doesn't appear to be anything being recorded in the agent logs on the client when I'm sending the activate tasks. I'm not sure where to look or what to look for on the server. Can anyone help please? Thanks

And it worked! Thanks everyone for your help. Cheers.

I think I've figured it out. First I tried enabling the Proxy settings in the Security policy applied to the External group, with no proxy settings configured, and the Force setting applied. Still no joy. I then duplicated the Remote Administrator Agent applied at the All group level, and configured this the same as above, and assigned this to the External group. No more proxy server setting applying on the client I'm now just waiting for the software deploy task to complete, but so far no error

OK, checked the log on the client, getting the following error; Software installation failed: GetFile: Failed to connect to HTTP proxy server 'ERA server internal IP address' (port: 3128) So Marcus was on the money Anyone know how to change this on the agent side? Without affecting all other clients? The proxy server settings is being applied to all groups at the All level. Looks like there are multiple policies applied at this level that include the same proxy server settings.

Hi everyone thanks for your replies. Marcos I'm not sure that applies until after the Endpoint Security software is installed? I have configured the policy to allow downloading updates directly from the Eset servers, this is working correctly on notebook computers that are out of the office for a few days at a time. It seems to me that the command to install the software isn't getting to the client. The agent is reporting back to the server though, as I can see the 'last connected' time updating regularly. Jimwillsher I'll check that log on the server. Might tell me something more. Edit: Just realised I need to check that log on the client right Currently I only have ports 2222 & 2223 open on the firewall at the server location. This is allowing the agent to connect to the ERA server. Do I need to configure any open ports on the client firewall (ie Windows Firewall)? I wouldn't think I should need to? Or any other ports at the server location?

I've been searching but can't find an answer to this, and have tried everything that I can think of or that's obvious. We have Eset Remote Administrator 6 installed with all internal network clients installed successfully with Eset Endpoint Security. We have a couple of computers that are external to the network that we want to deploy from the ERA server so they report back via the agent. I've opened ports 2222 and 2223 on the firewall, created an 'Agent Live Installer' on the ERA server and run this on the external client. The agent has installed successfully on the client and has reported back successfully on the server, and I can see the Agent is regularly connecting back to the server. I've tried running a Client Task / Software Install task from the server to deploy the Endpoint Security software, the same as I would for an internal client, selecting the 'Repository' for the installation software. I've also tried entering a direct URL (below). Each time I try this I just get a Failed status in Details / Executions in the task properties. The direct URL link I've tried is; hxxp://www.eset.com/int/download/thank-you-business-v6/file/12627/ I can't find any further information in the ERA server reports on what has failed. If I check the Agent log on the external client (C:\Users\%user%\AppData\Local\Temp\ra-agent-install.log) there is no entry in the log at all since the installation of the agent. So I'm assuming the Agent on the client computer is not receiving commands from the server. What do I have to do to get this to install the client software? Thanks in advance for your help