Tranquil IT Forum

Good morning

I can no longer get WADS to work.
After updating WAPT, I updated winpe with the new minimal wads package.
Despite this, I am experiencing the following malfunction:
- The PC boots via PXE and we reach the point where we name the PC
- It appears correctly in WAPT and I can validate the configuration as well as the DJOIN; I launch the deployment
- On the PC, I press "2" to launch and I end up with this: If I manually restart wgetwads64, I get this (and it loops indefinitely): If I manually rerun wgetwads64 BUT WITHOUT the double space before --server-url, I get this: A little help would be welcome.

Hello,

this happens to me from time to time.
To work around it:
- delete the registration in the deployment console and restart the PXE boot process, then re-register the machine.

If it happens consistently, try registering the machine using the MAC address, preparing the image and drivers, and making the machine available for deployment directly in the console. This is less flexible, however.

Regards

The strange config data error indicates "config data verification failed,"

which suggests that the configuration (XML) is incorrectly signed or not signed by a recognized key.

Do you have multiple keys?

If not, edit the XML configuration (add just a space, for example); this will re-sign it.

Hi Simon,

we have certificates for each of our technicians, but I assume that's not what you mean by "key"...

I'll look into re-signing the configuration.

Result:
After re-signing the configuration file, I restarted the installation, and this time it was the ISO that needed re-signing.
So I downloaded it and re-uploaded it, and this time, finally, it worked.

My question is: could it be the WAPT update, or a Linux system update, that caused this double problem?
Or something else?

Thanks for your help,

Tom

Hello,

when you generate a WinPE file, you include accepted certificates within it.

Are your technicians' certificates included in the WinPE file?
If not, that explains why there's a rejection.

The certificates have been in place for a while now...
At least, mine hasn't changed.
I haven't touched WinPE since its last update (and I haven't touched it today).

The only actions I took today were:
- Downloading the ISO from Wapt and then re-uploading it.
- Removing a space from the config file to re-sign it.

(*This isn't a mistake; it is indeed "a" space when referring to a syntax character .)