Hello,
I had set up a virtual server (Windows 2022) and installed the WAPT console on my machine (Windows 10) with a trial version. Everything worked perfectly.
Recently, we acquired a license for several dozen machines, and I removed it for my own installation to create a "clean" server and install the console on a dedicated machine, but since then, it's been malfunctioning… My machines appear correctly in the console after the agent is distributed via GPO. However, the WAPT packages don't work. When the machine restarts, the WAPT window launches on my client machines, but no installation begins. The same thing happens when I try to send a simple message to the client machines from the console; nothing happens. I'm not getting any error messages and I've disabled my antivirus to see if that was the problem. I've deleted everything and reinstalled, but the problem persists for several days now... I'm out of ideas...
WAPT 2.2.2.12388 on a console running Windows 10 21H2 and a server running Windows Server 2022 21H2.
Thank you in advance for your help.
Sincerely,
Philippe
[RESOLVED] Posts are reporting correctly but no deployment
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Philippe,
regarding the symptoms described, it's very likely a mismatch between the certificate deployed on the workstations and the certificate in the console.
When you performed your new installation, you probably generated a new private key/public certificate pair. In the WAPT security model, packages and all actions must be signed by PKI. If the key doesn't match the certificate, the workstation will reject the actions and packets.
Regards,
Denis
regarding the symptoms described, it's very likely a mismatch between the certificate deployed on the workstations and the certificate in the console.
When you performed your new installation, you probably generated a new private key/public certificate pair. In the WAPT security model, packages and all actions must be signed by PKI. If the key doesn't match the certificate, the workstation will reject the actions and packets.
Regards,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
-
Philippe StSeb
- Messages: 2
- Registration: January 10, 2023 - 3:46 PM
Hi Denis,
Thanks for your reply.
I haven't had time to check that yet, and yesterday at lunchtime I opted for a more radical solution: I deleted the VMs hosting my server and console and started from scratch to have a "clean" installation!
This time it works!
++
Philippe
Thanks for your reply.
I haven't had time to check that yet, and yesterday at lunchtime I opted for a more radical solution: I deleted the VMs hosting my server and console and started from scratch to have a "clean" installation!
This time it works!
++
Philippe
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Philippe,
OK, thanks for the feedback. If it happens again, make sure the private key and certificate match. And when reinstalling a server and wanting to reuse the existing certificate, be careful not to generate a new one!
I'm marking this topic as resolved.
Have a good day,
Denis
OK, thanks for the feedback. If it happens again, make sure the private key and certificate match. And when reinstalling a server and wanting to reuse the existing certificate, be careful not to generate a new one!
I'm marking this topic as resolved.
Have a good day,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Hello,
I seem to be having the same problem. The computers I install via GPO aren't receiving the installations either. On my console, the WUA (Windows Access Unit) is showing a question mark, and I do get an error message when I try to install software (trusted signer certificate). What I don't understand is that I followed the documentation for installing WAPT via GPO, and I can't find where I'm supposed to generate this certificate.
Could you help me?
Sincerely
I seem to be having the same problem. The computers I install via GPO aren't receiving the installations either. On my console, the WUA (Windows Access Unit) is showing a question mark, and I do get an error message when I try to install software (trusted signer certificate). What I don't understand is that I followed the documentation for installing WAPT via GPO, and I can't find where I'm supposed to generate this certificate.
Could you help me?
Sincerely
