Mike Raineri

> One last change request, then we can merge (assuming that @mraineri does not have further comments). I do not have anything else; everything looks good to me so far.

Are you able to add `boot_override_mode: UEFI` to your request? If the boot override mode is currently configured as `Legacy` on the system, then that would explain why it's rejecting...

> > Are you able to add `boot_override_mode: UEFI` to your request? > > As listed in OP, adding `boot_override_mode` made no difference. > I missed that statement; this is...

This should be the equivalent curl command if you want to experiment on your system: ``` curl -k -u -H "Content-Type: application/json" -X PATCH 'https:///redfish/v1/Systems/System.Embedded.1' -d '{"Boot": {"BootSourceOverrideTarget": "UefiTarget", "BootSourceOverrideEnabled":...

I'm trying a few different systems I have available to see if things are better on newer versions of firmware. Unfortunately I do not have anything that goes back as...

Well, nothing has really improved except for the fact that it returns with 200 with the same error message in the response body instead of 400, which is just going...

I would fully expect the textual representation to be supported in Redfish. The mockups from the DMTF that have sample UEFI device paths show the textual format rather than the...

I've been pointed to the following script as an example: https://github.com/dell/iDRAC-Redfish-Scripting/blob/7d1e39ab6277bb09da7de6d0e842acbbd25a2cce/Redfish%20Python/SetNextOneTimeBootDeviceREDFISH.py One thing I noticed is the `BootSourceOverrideEnabled` is not specified in the request. Removing that property from the curl...

> > One thing I noticed is the `BootSourceOverrideEnabled` is not specified in the request. Removing that property from the curl request I built allows the PATCH to go through....

I was able to confirm that on HPE systems, providing both properties in the same request is valid. The documentation is supposed to indicate that you cannot have a target...