@Tom-Elliott Hi Tom, this problem is resolved now.

Thanks.

I’m confused. There is no issue in the db, but the data is stored in the db as base64 encoded, though I plan to move this to aes encrypted just to ensure somebody can’t just steal your data.

@kverkiss said:

@Wayne-Workman I have set a DHCP reservation for this laptop in W2K8 server. I am able to define a bootfile for this specific laptop, in this case to boot realtek.kkpxe. This should solve the problem for the laptop not able to boot over pxe.

Great! Just a hint on this: ipxe.kkpxe should have the realtek driver included. Just undionly.kkpxe comes without native drivers.

That said I still think that you are good to go with your solution. Some buggy BIOS versions just won’t run with the normal kpxe files and you just have to come up with a special solution for those.

@kverkiss Good !!! The next time I see a jumble of nonsense errors such as this I’ll recommend trying a different drive.

@kverkiss You can also pull your product key from the machine using Magical Jelly Bean. https://www.magicaljellybean.com/

Thanks for your info. I will provide this information after a wedding.

For now I have resolved the problem by using the undionly.kpxe file from my previous install. However it seems after each SVN update, I need to restore the same file, I wonder if my future hardware is supported by it.