Notes: Running ELK 7.11.2 Standalone OS Windows Server 2008 R2 Standard
I am deploying the Elastic Endpoint on several servers. On servers running OS Windows Server 2012 R2 Datacenter and Windows Server 2019 Datacenter, the deployment of the Elastic-Agent and Elastic Endpoint runs fine, without issues.
On the other hand, on servers with OS Windows Server 2008 R2 Standard I can deploy the Elastic-Agent, start its service and confirm it's checking with ELK node, but it is failing to deploy the Elastic Endpoint. Agent shows status "Unhealthy" and message shows "FAILED: operation 'Exec' failed: ", but no logs are being uploaded so I can check them in Fleet/Agents/Agent/Logs.
I went to check the logs in the server and found many error lines. Please check the link below and help me to fix this issue.
Thanks for the logs. It looks like you're using a 7.11.2 Elastic Agent. If you upgrade to a 7.12 Elastic Agent when this issue happens you should see additional logging from Endpoint as it tries to install. Would it be possible for you to try that?
Are you by chance running a 32bit version of Agent on a 64bit Windows machine? If so, that will prevent Endpoint from being able to be installed.
You can try installing Endpoint manually to see logs from when it tries to install.
From within an unzipped Elastic Agent download, enter the downloads directory
Unzip Elastic Endpoint
Install Endpoint manually to see the install logs. Make sure to do this from an Administrator prompt. If you can't resolve your issue from looking at those logs, please share them so we can help diagnose your issue.
I will try the steps provided. Thank you for the step by step tutorial. I was not aware that there was a way to manually install just the Endpoint Security. As exposed before, the Elastic-Agent was successfully installed, the related service is running and the agent is reporting to Fleet. The only thing failing is the Endpoint installation.
I have a couple of questions:
If the Elastic-Agent was successfully deployed, doesn't this mean that the x86_64 version was the right one, according to the OS and then also the Endpoint Security should have been installed without problems, or does the Endpoint installer work differently? I'll try the 32bits installer version anyway.
According to the logs, the Elastic-Agent seems to retry the Endpoint installation every few seconds. Should I stop the Elastic-Agent service before trying manual Endpoint installation, or it does not matter?
I tried to run the manual installation of the Endpoint, but got the error below:
PS C:\Program Files\Elastic\Agent\data\elastic-agent-1d9cce\install\endpoint-security-7.11.2-windows-x86_64> .\endpoint-
security.exe install --resources endpoint-security-7.11.2-windows-x86_6\endpoint-security-resources.zip --log stdout --l
Program 'endpoint-security.exe' failed to execute: Windows cannot verify the digital signature for this file. A recent
hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicio
us software from an unknown source
At line:1 char:24
+ .\endpoint-security.exe <<<< install --resources endpoint-security-7.11.2-windows-x86_6\endpoint-security-resources.
zip --log stdout --log-level debug.
At line:1 char:1
+ <<<< .\endpoint-security.exe install --resources endpoint-security-7.11.2-windows-x86_6\endpoint-security-resources.
zip --log stdout --log-level debug
+ CategoryInfo : ResourceUnavailable: (:) , ApplicationFailedException
+ FullyQualifiedErrorId : NativeCommandFailed
I have been researching and in order to fix this error, it looks like the “ driver signature enforcement ” must be disabled, involving a server reboot. The servers cannot be rebooted at this time.
Hi @ManuelF. endpoint-security.exe is compiled with /INTEGRITYCHECK, which forces Windows to verify its digital signature upon load. It's signed with SHA256 because Microsoft has deprecated SHA1. If your machine is unable to verify the signature of endpoint-security.exe, then you likely need to apply some Windows Updates. See this Microsoft document for more information.
Hi @gabriel.landau and thank you for joining efforts. I have been researching on my own and I have arrived to the same conclusion. That server may be missing some security updates. Now that you confirmed the installer is digitally signed, I'm pretty sure we are missing updates. I will take care of that as soon as possible this week and then I'll try Endpoint deployment again.