Tranquil IT Forum

Hello everyone,

We have recently started using WAPT and, following a deployment on a few workstations, we are encountering the following error:
We searched for the public key in the UUID.wapt file corresponding to the machine in question and this file does not appear anywhere on the server.

It appears that the key was not retrieved correctly. However, this does not explain how the device still appears in the console.

We have already tried removing the machine from the console and uninstalling the agent on the machine in question, but the automatic reinstallation of the agent by the GPO that we put in place did not solve the problem.

Do you have any suggestions for bypassing this blockage from the console, directly on the server, or on the workstation?

Thanks in advance.

Hello InfoChesnay,

InfoChesnay wrote: ↑Oct 9, 2018 - 5:12 PM We have recently started using WAPT and, following a deployment on a few workstations, we are encountering the following error:

Code: Select all

ERROR IN APPLICATION
An unhandeld exception has occured
EWaptCryptoException: PEM file does not exist

Which log did you get this error in? Could you also provide the version information, e.g. viewtopic.php?f=9&t=886

Do you have the same problem on all workstations, or only on some workstations?

InfoChesnay wrote: ↑Oct 9, 2018 - 5:12 PM We searched for the public key in the UUID.wapt file corresponding to the workstation in question, and this file doesn't appear anywhere on the server.

It seems that the retrieval of this key wasn't done correctly. However, this doesn't explain how the workstation still appears in the console.

Registering a workstation on the WAPT server is not based on any key. The first registration is either "open" (no restrictions), or in Kerberos mode (using the shared secret between the workstation and AD for authentication), or in login/password mode (the admin is at the workstation and enters the server's admin password).

Once the workstation is registered, it exchanges keys with the server, and it is the workstation's key that is then used for authentication. However, the initial authentication (or lack thereof) must be based on something else.

Sincerely,

Denis

Hello dcardon,

Thank you for your feedback.
For your information:
- WAPT version: 1.5.1.23
- Debian server OS, version 9.5
- Administration is done via the WAPT console on a Windows 10 machine and a Windows Server 2012 R2.

To answer your questions:

1) I didn't see this error in a log file. This error occurs when I'm in the administration console and I try to add a dependency. See attachments "error 1" and "error 2".


2) This problem exists on a few recently installed workstations. The operating system of the user workstations is Windows 10.

3) Regarding the workstation registration in the WAPT server, it is successful since the workstation appears in green in the Status and Reachable columns. See attachments "workstation registration". Furthermore, the agent is installed via a GPO, which, after checking, is working correctly.

To clarify my problem, I want to explain that from my user workstation, I can launch the WaptTray console and then download the packages to install them on the machine. However, when I try to do the same thing via the WAPT management console, I get the two errors shown in the attachments.
Error 1 occurs when I right-click on the host => add a dependency (in my case, a package group) => OK.
Error 2 occurs when I edit the machine => select packages => add dependencies to the package => save and apply.

I think that, based on these two errors, there's a key exchange problem between the host and the server, which prevents authentication and therefore the application of operations from the WAPT management console.

Thank you for your help and feedback. I hope the information provided is clear and sufficiently precise.

Sincerely,

InfoChesnay