Good afternoon,
Wasn't sure where to post this, but wanted to notify folks of an issue we were running into with a batch of new machines one of our clients purchased. The client purchased a newer model machine with an AMD Ryzen AI Pro 5 processor. OSDCloud just wouldn't boot, no matter what I tried. After doing some digging, found out that these newer machines either don't include the 2011 Microsoft Secure Boot certificates or they just flat out block them. I was using a Lenovo T590 to write OSDCloud. Also attempted to put OSDCloud behind Ventoy, boot into that (which worked) and call the boot.wim in OSDCloud (which would freeze the machine). Even tried disabling Secure Boot and allowing 3rd party certificates to no avail. I took that same USB, passed it to a VM and it booted fine.
I then shift gears and used the new AMD Ryzen AI Pro 5 processor machine to create the thumb drive, and it worked. I had a colleague stand up another one of these AI processor machines at the client site, configured OSDCloud, burned the USB, and it worked. They then tested that same stick on the older machines and it worked just fine.
It seems that manufacturers are finally pulling the plug on the 2011 Microsoft Secure Boot certificates and OSDCloud will need to be configured and burned from a newer machine, that way when it actually writes your ISO's and USB's, that it's able to include those latest keys within the WIM's and EFI files. And, the process of configuring OSDCloud and creating the USB are exactly the same on these newer machines as they were on the older ones.
Just wanted to throw that out there in case anyone else is running into a similar situation.
Thanks
Good afternoon,
Wasn't sure where to post this, but wanted to notify folks of an issue we were running into with a batch of new machines one of our clients purchased. The client purchased a newer model machine with an AMD Ryzen AI Pro 5 processor. OSDCloud just wouldn't boot, no matter what I tried. After doing some digging, found out that these newer machines either don't include the 2011 Microsoft Secure Boot certificates or they just flat out block them. I was using a Lenovo T590 to write OSDCloud. Also attempted to put OSDCloud behind Ventoy, boot into that (which worked) and call the boot.wim in OSDCloud (which would freeze the machine). Even tried disabling Secure Boot and allowing 3rd party certificates to no avail. I took that same USB, passed it to a VM and it booted fine.
I then shift gears and used the new AMD Ryzen AI Pro 5 processor machine to create the thumb drive, and it worked. I had a colleague stand up another one of these AI processor machines at the client site, configured OSDCloud, burned the USB, and it worked. They then tested that same stick on the older machines and it worked just fine.
It seems that manufacturers are finally pulling the plug on the 2011 Microsoft Secure Boot certificates and OSDCloud will need to be configured and burned from a newer machine, that way when it actually writes your ISO's and USB's, that it's able to include those latest keys within the WIM's and EFI files. And, the process of configuring OSDCloud and creating the USB are exactly the same on these newer machines as they were on the older ones.
Just wanted to throw that out there in case anyone else is running into a similar situation.
Thanks