I do appreciate the video, but as an actual user, I would prefer a practical OME integration example. OME already gets the latest updates from Dell online. That is the one scenario shown and the one that is not useful because it makes no sense to use DRM and have the same result to what is built-in OME. Why would someone integrate DRM with OME? 1) There is a N-1 policy and you want a baseline that shows compliance based on the desired version, not the latest version. 2) You want to separate BIOS and LCC firmware from the rest (you didn't show that can be done in the video). A baseline using a custom repository wher only those two are selected would report compliance specificly for BIOS and LCC only. 3) An organization has a lot of servers that aren't current and their firmware needs to be staged (I.e. install from 2020 firmware to 2021 to 2022) and you want it done in bulk. This is where manual repositories are great. You can create a repository for each year and import specific versions that apply for each year. Now a baseline can be created that is associated to each staging year and the firmware updates cab be applied in bulk using OME. Again, appreciate the video but would really love to see real-life practical examples.
Hello Trevor Westerdahl, maybe this OME Plugin is an alternative for DRM for you: dell.to/42FmRVU If you need further help, please contact the Dell Support at dell.to/42E7yfU Thank you.
I do appreciate the video, but as an actual user, I would prefer a practical OME integration example. OME already gets the latest updates from Dell online. That is the one scenario shown and the one that is not useful because it makes no sense to use DRM and have the same result to what is built-in OME.
Why would someone integrate DRM with OME?
1) There is a N-1 policy and you want a baseline that shows compliance based on the desired version, not the latest version.
2) You want to separate BIOS and LCC firmware from the rest (you didn't show that can be done in the video). A baseline using a custom repository wher only those two are selected would report compliance specificly for BIOS and LCC only.
3) An organization has a lot of servers that aren't current and their firmware needs to be staged (I.e. install from 2020 firmware to 2021 to 2022) and you want it done in bulk. This is where manual repositories are great. You can create a repository for each year and import specific versions that apply for each year. Now a baseline can be created that is associated to each staging year and the firmware updates cab be applied in bulk using OME.
Again, appreciate the video but would really love to see real-life practical examples.
Hello Trevor Westerdahl, maybe this OME Plugin is an alternative for DRM for you: dell.to/42FmRVU
If you need further help, please contact the Dell Support at dell.to/42E7yfU
Thank you.