Tranquil IT Forum

Hello,

I'm currently testing WAPT Discovery.
I've configured Kerberos authentication and deployed the agent via GPO on an on-premises Active Directory (Windows PC).
The agent deploys correctly and is accessible on the machine via the address 127.0.0.1:8088.

While browsing the forum, I tried using the command: `wapt-get register -l debug` as an administrator on the Windows console
. Among other things, I get this response:

WARNING: Kerberos can not be enabled, "register" must be launched under system account to use Kerberos machine account auth. Use --service switch or "psexec -s wapt-get register". Registering host against server: https://wapt.mydomain.local.
Then it waits for an account to register:
Please get login for add_host:

when I connect to http://127.0.0.1:8088/register.json?notify_user=1. The PC appears correctly on the console.
Perhaps I missed a step during the Kerberos setup, but I followed the wiki meticulously.

Can you help me?

Sincerely

Hello Emmanuel,

the Kerberos register uses the machine account, so it must be run as the SYSTEM account (as indicated in the error message).

When the service starts, it will register, so if everything is configured correctly, the machine will appear in the console. You can verify in the "Registration Method" column that it is indeed set to Kerberos.

Regards,

Denis

Hello,

thank you for your quick reply.
Indeed, on another computer, after restarting it, it reappeared in the console.

A small piece of information that seems logical, but which must have been my mistake: as stated in the documentation, the default CN is CN=Computers. If I understand correctly, the CN to save is the one where the computers are located (for me, they are in a different OU).

Have a good day.

Hi Emmanuel,

the OU isn't calculated by the server but is retrieved by the agent (as inventory data). The agent retrieves the OU through the GPO engine (which itself needs to retrieve the correct OU to know which GPOs to apply). If the correct OU isn't retrieved (after the next inventory), it means there's a GPO issue on the machine, or a problem with the data retrieval.

Please open a new topic for a new issue.

Denis