Tranquil IT Forum

[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.

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.

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

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?

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."