Tranquil IT Forum

Hello,
I'm new to using WAPT.
I just installed my WAPT Community server on CentOS 7.
I configured my console on my Windows 10 machine and generated my wpatagent.exe file for my client machines.

I successfully created my first 7-Zip deployment package by following the video on the page https://www.wapt.fr/fr/doc/wapt-create- ... index.html.

I managed to deploy my 7-Zip package on my administration machine (the one with the console)
, but I can't do it on my first test machine where I only installed wpatagent.exe.

When I add my 7-Zip package to deploy it on my test machine, the "Save and Apply" and "Save" buttons remain grayed out.
When I try to add a dependency via right-click, I get the message "The user certificate c:\private\privatekey.crt is not authorized on the selection."

While right-clicking and selecting "Add Dependency" works on my machine with the console, I get a window asking for my private key password...

What have I missed to make it work on my client machines?

Regards

As the error message states, your private key does not match the certificate (or lack thereof) deployed on the client machine. You likely installed waptsetup.exe instead of generating an agent and deploying waptagent.exe.

Hello Denis,
Thank you for your reply.
Indeed, the certificate was missing from the directory structure installed by the WaptAgent installer.

I manually copied the certificate to c:\program files x86\wapt\ssl.
I thought the certificate was automatically included in the installer when it was compiled on the server.
In the form, I had specified c:\private\privatekey.crt as the path to the certificate.
Perhaps I should have left the default path, c:\program files x86\wapt\ssl?

In any case, once the privatekey.crt file was pasted into c:\program files x86\wapt\ssl on the client machine, I can deploy my packages from the admin console.

Since the latest version of WAPT, the WAPT console no longer starts automatically as administrator; it can now start as a regular user.

And as a regular user, the console cannot copy anything to wapt\ssl, which would explain why the certificate was not present on your machine.

The procedure should specify that the Waptagent should be installed on the machine that just generated it.