I'm happy you found a solution.

And thank you very much for the detailed explanation, I'm certain other customers can benefit from this.

Proxy settings are missing for SYSTEM.

Solved by set up the proxy for Local System account.
Download PsExec.exe.

Start a command shell (cmd.exe) with administrator privileges.

PsExec -i -s cmd.exe
This will open a new cmd.exe that is running under Local System authority. You may check this by executing "whoami" command into that new command shell which will return "nt authority\system"

Open the Internet Options with this command:

inetcpl.cpl
Go to “Connections” tab, click on “LAN settings”, and set up the “Proxy server” section with the relevant proxy address and port number.

(optional) If you need to Bypass proxy server for local addresses, tick the relevant checkbox.

(optional) If you need to specify exclusions, click “Advanced” and set up the “Exceptions” section accordingly, and click “OK”.

Click “OK”, and exit all open command shells.

Secteer agent is now communicating with the Secteer backend!

Thanks for your answer and pointing to a direction to investigate and possible solution.

Also we will update the whitelisted servers in our Proxy server.

Kind regards,

Hi,

It appears that we have some outdated documentation, it will be fixed within a day or two. The OCSP / CRT hosts should be:

• r3.o.lencr.org
• r3.i.lencr.org

However, this is most likely not the cause of the issue that you have.

I can see that the host got registered with the system. This means that the installer managed to contact the backend and get the authToken, that you see in the logfile.

Since the installer is invoked interactively by the logged in user, it uses the same network / proxy settings as the user that is logged in, when it invokes the Agent to register for a authToken.

While the Agent runs as the SYSTEM user, after it is installed.

In some environments, there is restrictions on what the SYSTEM user can do on the network and whether it has access to a proxy.

I suspect that is what you are seeing here.

Since I don't know anything about your system configuration, it is hard to advise on the proper cause of action to allow the Agent network access.