[WAPT INFO]
OS: Windows
WAPT Version: 2.4.0.14031
Enterprise Edition
Hello,
we are experiencing a WADS error, as shown in the attached image.
We have migrated our enterprise solution to a new Windows VM.
We already encountered this bug in version 2.3; the rest of the deployment is working correctly.
in the deployment command parameters,
`verify_cert=0`
but this does not resolve the issue.
Thank you in advance.
Best regards,
Mathis.
[SOLVED] WADS Error - Self Signed Certificate
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
The configuration signature appears to be invalid
since version 2.4. A button in the right-click menu allows you to verify the machine configuration signature in WADs.
To re-sign, stop the deployment and then restart it.
Another possible issue is that timing is important in signature verification, so the time setting in the BIOS may have an impact.
since version 2.4. A button in the right-click menu allows you to verify the machine configuration signature in WADs.
To re-sign, stop the deployment and then restart it.
Another possible issue is that timing is important in signature verification, so the time setting in the BIOS may have an impact.
If I check the configuration signature, I get this display:
And if I sign the packages, start and stop the deployment, I get this display when checking the configuration signature:
Despite this, I still get the same error during the "Self Signed Certificate" deployment
- Wapt_CertNo.png (34.93 KB) Viewed 3281 times
- Wapt_Cert.png (9.81 KB) Viewed 3281 times
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Two possible scenarios to check:
The WinPE file doesn't include the key that signed the WADs system (when you generate the WinPE file, you see a list of recognized certificates). You can regenerate a WinPE file, making sure that your certificate is included.
Also check:
Is the BIOS clock correct?
The WinPE file doesn't include the key that signed the WADs system (when you generate the WinPE file, you see a list of recognized certificates). You can regenerate a WinPE file, making sure that your certificate is included.
Also check:
Is the BIOS clock correct?
Hello,
to resolve the issue, we generated a new certificate separate from the old one. To ensure the hosts had this new certificate, we deployed it via Group Policy, thus discontinuing the use of the old one.
Since then, there have been no problems; the new certificate works perfectly with WADS.
The issue likely stemmed from the certificate itself; when viewing its details, it displayed an error: "The integrity of this certificate cannot be guaranteed. The certificate may have been damaged or altered."
to resolve the issue, we generated a new certificate separate from the old one. To ensure the hosts had this new certificate, we deployed it via Group Policy, thus discontinuing the use of the old one.
Since then, there have been no problems; the new certificate works perfectly with WADS.
The issue likely stemmed from the certificate itself; when viewing its details, it displayed an error: "The integrity of this certificate cannot be guaranteed. The certificate may have been damaged or altered."
