Yes, I am referring to OME stage for next server reboot option. We are using the latest version of OME.
Every other month we are patching Windows security update and it needs a downtime.
I am thinking, if I stage the component one by one, say starting from iDrac LLC firmware update, stage it to all our stand alone remote servers just awaiting for the next reboot to be installed. (Of course, we would target only per Dell server model associated with specific catalogue). Then by the time the Windows update rolls out, firmware updates that has been stage successfully will eventually be installed once the host is being rebooted.
Instead of having a separate downtime for Windows security updates and firmware update, could we do this strategy, having only one downtime. What do you think?
I'm not sure if the option Stage for next server reboot check box is available if you stage components without baseline settings. But you can give it a try on the next downtime, or if you have any offline servers that you can try on. Unfortunately I don't have any servers for me to test it for you, therefore I'm not able to let you know the outcome.
I have been doing this the last 2 months. You just have to plan on an extended downtime for the firmware installs. We tell users about 15 to 20 minutes extra but this will depend on how many updates there are. It has been working pretty good except for the systems that have issues installing the updates but this isn't an OME problem....
Thank you @TXBruce for confirming that it did work. With this firmware patch up strategy, it will really save time. I hope dell will have a white paper or a publication about this approach in patching a dell's firmware alongside with the host operating system updates that includes a restart.
DELL-Joey C
Moderator
•
4.1K Posts
0
April 17th, 2020 02:00
Hi,
Are you referring to OMEnterprise? Also, are you referring to OME's Stage for next server reboot option? Page 37.
https://dell.to/3enfz02
covid-19
1 Rookie
•
9 Posts
0
April 17th, 2020 04:00
Hi @DELL-Joey C ,
Yes, I am referring to OME stage for next server reboot option. We are using the latest version of OME.
Every other month we are patching Windows security update and it needs a downtime.
I am thinking, if I stage the component one by one, say starting from iDrac LLC firmware update, stage it to all our stand alone remote servers just awaiting for the next reboot to be installed. (Of course, we would target only per Dell server model associated with specific catalogue). Then by the time the Windows update rolls out, firmware updates that has been stage successfully will eventually be installed once the host is being rebooted.
Instead of having a separate downtime for Windows security updates and firmware update, could we do this strategy, having only one downtime. What do you think?
DELL-Joey C
Moderator
•
4.1K Posts
0
April 19th, 2020 19:00
Hi,
I'm not sure if the option Stage for next server reboot check box is available if you stage components without baseline settings. But you can give it a try on the next downtime, or if you have any offline servers that you can try on. Unfortunately I don't have any servers for me to test it for you, therefore I'm not able to let you know the outcome.
https://dell.to/2zfBqqh
TXBruce
1 Rookie
•
14 Posts
1
April 23rd, 2020 07:00
I have been doing this the last 2 months. You just have to plan on an extended downtime for the firmware installs. We tell users about 15 to 20 minutes extra but this will depend on how many updates there are.
It has been working pretty good except for the systems that have issues installing the updates but this isn't an OME problem....
covid-19
1 Rookie
•
9 Posts
0
April 23rd, 2020 16:00
Thank you @TXBruce for confirming that it did work. With this firmware patch up strategy, it will really save time. I hope dell will have a white paper or a publication about this approach in patching a dell's firmware alongside with the host operating system updates that includes a restart.