IT/TECH: Windows Deployment Services (WDS) do not work and fails with "The Following Client failed TFTP" or similar

If you, like I did in the past weeks, find the following or a similar error, the solution maybe far easier than you believe:

The Following Client failed TFTP
Download: Filename: boot\x64\wdsmgfw.efi
ErrorCode: 1460

This error maybe easily resolved. Check whether or not your NICs use Jumbo Frames of whatever size. If so, for this server, specifically, for the NICs responsible for the WDS service, turn Jumbo Frames simply off.

After trying really everything, including re-installation of the whole system, I finally found the one thing I always do (use max. Jumbo Frames) I shouldn't have done with this system.

However @microsoft, the error message is 'missleading' - actually not helping, so much is for sure.

IT/TECH: SYSPRP Package [..] was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

It may be that I am the only one running in this stupid problem due to my own 'fooliness', the problem however fills the one or other forum.

What happened

• Created a Windows (10, v1809) image for deployment (with all needed pre-installed software due to the lack of SCCM or similar tools and since network speed and capacity is not a problem (yet), ...)

• For a number of reasons I decided to activate the Administrator user to do this instead of using the 'interim' one I did setup in first place.
• I also deleted the user in "Computer Management"
  
• Of course, at a certain point, a sysprep /oobe /generalize /shutdown needed to be run

• The unexpected result:
  
  The error: SYSPRP Package [..] was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image was the result.

The solution is as easy as simple...

1. Delete the user profile in the computers in Control Panel\All Control Panel Items\System\Advanced system settings\User Profiles 
2. reboot

done and solved, at least for my issue.

Note

All powershell [...] Remove-AppXPackage [...] haven't worked for me nor it seems they are somehow leading into a helpful image state from my point of view. However, you may want to try them as well.

PS
Sorry for the short and not really inspired explanation and elaboration on this error and its potential solution... I hope it is understandable and solves your issue even in this short form.