[Configure EPNS]

Hi,

I am not able to configure EPNS, I do not know where I am setting up, I am configuring this feature.

Can you help me please?

Is it necessary to activate the machines or only to force synchronization?

[Eset Endpoint Security 7 remote installation]

Hi,

Need more information?

[Eset Endpoint Security 7 remote installation]

Em 07/11/2018 às 17:01, Marcos disse:

O problema ocorre mesmo que você instale manualmente uma versão mais recente do Nó de Extremidade em cima de um antigo mais antigo? Qual versão mais antiga do Endpoint está instalada nas máquinas problemáticas? Que oper. sistema está lá?

I'll confirm that the local installation is running on top of an old version, as far as I remember it is running yes. But anyway, I want to solve the problem of remote installation.

The two machines have the same operating system and old product:
Windows 7 Professional x64
ESET Endpoint Security 6.2.2033.0

The installation problem occurred in updating the network agents too, it caused a lot of failure to install the new version over the old one. For agents, it has these old versions:
ESET Remote Administrator Agent 6.2.190.0
ESET Remote Administrator Agent 6.1.444.0

[Eset Endpoint Security 7 remote installation]

10 minutes ago, MartinK said:

Could you please provide us software-installation.log of this failure upgrade attempt? It should be located in the same directory as is AGENT's trace.log. Generic task failure might be caused by failure in installer itself. You also mentions "Failed to synchronize package repository" which indicates that AGENT was not even able to download installation package. In this case, there will be more detailed error message in AGENT's trace.log, but most probable issue is either network problem, or overloaded state of ESET infrastructure.

This machine generated the sync failure: ws66786
This machine generated the manual installation failure: ws67513

The logs are attached.

software-install_ws66786.log

software-install_ws67513.log

trace_ws66786.log

[Eset Endpoint Security 7 remote installation]

Hi,

Need help. It seems that in some cases trying to install the new version of Eset Endpoint Secutiry 7 on top of an old one is not being possible. Another case is of even showing in the console that a machine does not have the antivirus does not install the new version. And there is one last thing happening, I have to install and it turns the Running status from one day to another, and sometimes it stays that way and it does not end, neither with failure nor with success, and in some I even verified that it was installed new version.

In these three cases the Eset management Agent is up to date.

I looked at the local installation log but could not identify the problem, can you help me?

Failures:

Task failed, try to install software manually.

Failed to synchronize package repository. See traceability for more details. (in this case I tried to look at the trace, which I imagine is local, but I could not find any problems).

[I can not perform DB backup]

Guys, I can not perform the database restore, please help me. By command line I was only able to backup. I tried to upgrade to SQL Server Management Studio, but when I restore it, I can no longer access the remote administrator's web console, and the remote administrator's service keeps dropping.

I am trying to restore an ERA 6.1.444 backup in an ERA 6.1.444 installation.

[I can not perform DB backup]

Good afternoon.
I had to reset the user's sa password (by the SQL Server Management Studio console) to be able to perform backup via the command line (from cmd in administrator mode), where I used the -U and -P parameters to put the user sa and their respective password. I have completed the installation of ERA 6.1.444 by the all-in-one installer and only the web console user password is requested. Could you inform me the SA user's default password so that I can perform the backup correctly without having to install Management Studio?

[I can not perform DB backup]

I set the command, was setting the wrong instance. But still it generates error, now of login failure, could you tell me what it can be and how to correct it?

[I can not perform DB backup]

I can not back up my database every time I use this procedure: https://support.eset.com/kb6048/?locale=en_US&viewlocale=en_US. Error is generated already in bank creation. I can not identify what I'm missing, could you help me?
I'm looking to migrate from version 6.1.444 to version 7. In Lab until I've already done this upgrade, but I can not perform this backup, and I'm afraid I need to.

[I can not install agent era remotely.]

Can someone help me please? Where can I open call to Eset without being here in the Forum? Is there a channel to open calls to customers?

[I can not install agent era remotely.]

Good afternoon, how are you guys?

Could you understand my latest posts? Can you help me? Thank you for your attention.

[I can not install agent era remotely.]

Picture of the installation error that is shown in the  " Agent Deployment tasks information in last 30 days" report

[I can not install agent era remotely.]

On 30/08/2017 at 3:48 PM, MartinK said:

First of all, there is a report named " Agent Deployment tasks information in last 30 days" available directly from console - it is easiets way how to find out in which phase deployment failed.

In case it won't help, or in case problem will be with connection to client machine, analysis of SERVER trace log may help. Location of trace log can be found in documentation article I referenced in previous post.

 

 

I will try to explain the situation at the moment. An image is used to install Windows on computers, one with Windows 7 and one with Windows 10, and both contain the era agent and EES installed.

When the Windows 10 image is used to format some machine, it works correctly, this computer can communicate with the ERA and takes a license and is activated.

When the process is done with the Windows 7 image, it is wrong, the computer can not communicate with the ERA and it is not even possible to force an era agent installation on that computer, and the error generated in the report refers to communication failure (later I'll be posting a print of the report). But if I do connection tests to this computer, I have a positive answer, for example, I can ping to it, I can access the share C $ and ADMIN $, I can execute the compile nslookup to know if it has a return on the network, and it returns ok. One thing I found strange, is that this machine with Windows 7, despite getting such access, if I try to access via RDP, I can not, it is necessary to configure to release so that I can. Windows Firewall per GPO is disabled.

Thank you for your help.

[I can not install agent era remotely.]

22 hours ago, MartinK said:

During exeucion of remote deployment, all 3 methods are tried, including SSH. There should be also failure for both methods for deploying to windows machined (Windows network and WMI). There is a special report for remote deployment, which should provide more details of deployment progress - at least whether it failed during connection, or installation of AGENT.

Unfortunatelly you have not provided any specific details (trace log errors, ERA Server is runing on windows or linux?). I would also recommend to check steps described in documentation for deployment troubleshooting.

 

Good afternoon. The server that is installed on the ERA is running Windows Server. Where are the trace files related to the agent era installation on the ERA server? Thank you for your help

[I can not install agent era remotely.]

When I try to install the era agent remotely, an error is generated. When I check in the reports, an attempt is made to install via SSH, but I do not understand why it is trying to install this way, especially since it is an installation on a Windows 7 computer.

Windows Firewall is disabled, I can access the share "admin $" without problems, the user configured in the task is a network administrator. Please help me figure out the problem.

[Server ERA PROXY/PROXY HTTP]

 

 

 

First I'll leave the dp HTTP Proxy error log, soon I'll be posting the machine settings. I appreciate it.

 

Is this log complete? There seems to be only older entries indicating connection problem - machine hosting Apache HTTP Proxy has direct visibility to internet or it connect to another proxy? It seems that it was not able to connect to ESET servers which resulted in failure.

 

 

My page did not update and I did not see your answer. Yes, this server that appended the Apache log is the ERA Proxy + HTTP Proxy server, and it connects to the ERA server, to return information and also to fetch updates and thus create the local chache. I attached the complete log, I had not tried the date, so probably everything is ok today because this server is fully updated.

 

And this morning when I accessed the ERA I was in the group where this ERA Proxy + HTTP Proxy server and the branch machines, I identified that of 5 machines only two still are not able to update, they are in the status of "Failed to try Update ". The last log I posted is from one of these machines.

[Server ERA PROXY/PROXY HTTP]

Follows the network agent log of one of the machines that can not update. It looks like your update is being stopped.

trace.log

[Server ERA PROXY/PROXY HTTP]

 

Sorry, could you point me to the location of these HTTP Proxy files that you want me to collect?

 

What about the settings, do I want to export policy settings?

 

I await and appreciate your help.

 

 

HTTP Proxy logs should be located in C:\Program Files\Apache HTTP Proxy\logs\

Regarding configuration, it is easiest to request exported configuration from client computer (client details -> configuration -> request configuration) and check it once it is received. You should be able to see whether AGENT is configured to use HTTP Proxy as expected.

 

 

First I'll leave the dp HTTP Proxy error log, soon I'll be posting the machine settings. I appreciate it.

http-proxy-error.log

[Server ERA PROXY/PROXY HTTP]

Could you please check Apache HTTP Proxy logs (error_log or error.log in logs sub-directory) for possible problems? Also I would double check HTTP Proxy configuration for both AGENT and EES as it is different policy type. Mentioned error indicates that connection to either proxy or server was successful, but data of requested file was not received properly, i.e. connection was closed before file was fully downloaded.

 

What version of Apache HTTP Proxy and ERA are you using?

 

Sorry, could you point me to the location of these HTTP Proxy files that you want me to collect?

 

What about the settings, do I want to export policy settings?

 

I await and appreciate your help.

[Server ERA PROXY/PROXY HTTP]

I have configured ERA PROXY and PROXY HTTP in a branch office on a server and the local machines must report only to that server, and that server reports to the ERA.

Apparently the machines are with their communication established with the ERA PROXY server because last connection information is being returned in the ERA Web console, there are five machines and one server (ERA PROXY) and three returns fault status in the recent update attempts, one That can not take license and another one is ok, updated and with no negative status whatsoever.

 

The machine that has LICENSE error, I even trying to locally activate with the license key I could not, I tried to uninstall and returned that I needed to be with administrator account and I was, so I had to uninstall manually with an ESET application via prompt Command and then reinstall, but it continued the same way.

 

I accessed one of the machines with failed status in the update attempts and it looks okay, it connects via telnet on ports 2222 and 3128 of ERA PROXY, but if I try to run local update, nothing happens, but it has a message on the interface where I run updates Saying to be in the last. In Trace the agent log of this machine has the following error: Performupdate: Module update failed with error: Download interrupted. (Error code 8453). I do not know what to do, I tried to stop the firewall and it still did not help. I did not understand why one of the machines is ok and the other 4 is not.

 

All machines are running Windows 7 Enterprise and are x86. If you can help me, I appreciate it.

 

I'm sorry for the writing errors, I do not speak English, I'm using a translator.

[Trouble in the remote installation of Network Agent]

Task configuration is correct. Proper platform for installation should have been chosen.

Please provide some details about target operating system (Windows version ...) as there is a chance we are not correctly recognizing target platform. Also SERVER's trace.log will contain more details - even more if you enable full trace logging in SERVER's configuration.

In case you are not able to resolve this issue and there are only few problematic computers I would suggest to install AGENTs manually using live installer generated by ERA server.

 

 

When you say the right platform should be chosen is referring to the ERA server should send the correct version for the host, is not it? In this case, should be chosen automatically and not by me, would not that be I responsible for choosing the version in choosing the task, is not it ?! I ask this because the task does not have this kind of option.

 

I'll see if I can collect this information, but as I said earlier, I tried this installation on a machine with x86 version of OS.

[Trouble in the remote installation of Network Agent]

Could you specify details about your remote deployment task settings? First setting enables you to select AGENT version you want to install (default is automatic resolution of suitable version) and in case you select wrong platform, it may end just like in your case.

 

I'll describe the way I used to create the task so that it is understood what I did.

I selected the ADMIN panel / after Server Tasks / Agent Deployment / New:

Now I configured as follows:

Basic:

I put a name to the task.

Settings:

left enabled "Automatic resolution of agent subtable"

targets:

I chose the machine.

username:

I put the user

pasword:

I put the password

Server Hostname:

I left blank

Cerrtificate Settings - Peer Certificate:

ERA certificate

ERA certificate:

Agent Certificate

Certificate Passphrase:

I left blank

triggers:

I not created.

FINISH

 

Now I just went to the created task and clicked on and then selected "Run now". And it was there that returned the flaws I mentioned, with this I saw as an alternative download on the site eset the individual ERA agent package for x86 version.

This installation from ERA Server does not have to choose the version of WAS agent, this is done automatically.

[Trouble in the remote installation of Network Agent]

ok, in one of your earlier posts you mentioned:

 

"No, I'm trying to perform the installation by task."

 

Is this a task within ERA? If so, then ERA tasks work by communicating with the Agent. So by definition you need already have the agent insatlled on the computers.

 

To install the agent on PCs, you really have these options:  AD deploy from within ERA; AD GPO Software Install entry, or Agent Live Installer.

 

 

Jim

 

I'm trying to perform a remote installation by Eset Remote Administrator, a task of implementing the agent was, is an assisted installation by ERA server. I am using the method GPO or the Agent Live.

 

When I tried to accomplish this remote installation is generated an error that is not supported by the platform and in another case the task completed but not installed anything, veirifiquei locally on the machine and did not contain any folder ERA agent or service running. In both cases the installation attempt was made in Windows 7 x86.

 

After that happened I saw as a solution, download the agent for ERA x86 version and performed the local installation, which needed only to point the server and then put the ERA Web console credentials, and performing this procedure the agent ERA was installed.

I want to understand why I can not perform remote installation and how this concert, it is of paramount importance to remote installation. Thank you and look forward.

 

Note: My English is poor, I am using a translator, if something gets confused me know that I try to explain again.

[Trouble in the remote installation of Network Agent]

I'll ask again:)

 

What is "Network Agent" ? If you mean "ESET Remote Administrator Agent" then please confirm. If you menas something else, tellus what it is :-)

 

 

It's the same as me saying "I'm trying to install a document editing package" when I really mean "MS Word 2016 x64"....

 

Exact, precise names and versions are important in allowing others to help you.

 

 

 

 

Jim

 

Well, it is that so far here in the forum talking to the moderators of Eset I did not have to speak his name as seen in the manual, so did not get to understand your question because there is only one agent, so I thought it would be enough, but yes, Eset Remote Administrator agent.

[Trouble in the remote installation of Network Agent]

Please give more information. By "a network agent" do you mean ERA Remote Administrator Agent", or some other agent? If its some other agent, what is the agent and how are you trying to do the install?

 

 

Jim

 

 

Good Morning. I'll try to explain. I'm trying to install Network Agent remotely, the ERA server, then I create the server task "Agent Deployment" for an installation on a Windows 7 x86. There were two situations, one after sending perform this task a status was returned to "Done" to find nothing on the host, or the folder containing the files installed and running or service. In another case returned status of "failure, unsupported system."

 

I understand that the agent that the ERA server should support both versions. After I performed a local installation with the release of the agent for x86 and installed smoothly and communicated with the ERA.