Following the article I wrote on capturing BIOS information in your environment which can be found here, I packaged BIOS packages via the traditional route in SCCM for a customer.

One of the findings that the customer was experiencing is that users would often forget a BIOS upgrade was about to be performed and would fail since they would not connect a power supply or their battery would not be above a certain percentage (With Dell it is 11%). That said, even if they would have a power supply connected, they would often forget that the install was in progress and would unplug the power and would walk away which would eventually fail the BIOS install. Even though BIOS install usually contains a check within the OS and another when out of it, I decided to make it easier on the user by educating them by using a GUI. Who would blame them if they were not really reading the preconditions defined in Software Center and just clicking through just like every other application.

With this concern, I decided to create a UI which would display the requirements in a GUI but also bold enough to not loose their attention. Trust me, educating users clearly can save IT administrators a lot of work. Secondly, I wanted to make sure that the UI could not be closed by using the regular ‘close button’ as often users would ignore that window and close it saying they were working on something else and did not remember to run it again. At this point I know what your thinking – “Why not push via enforcement?”. The BIOS install unlike other application comes with a caveat that a reboot is mandatory and not letting users save their work is not a choice in our case. With this solution, I have tried to achieve persistence of the installation yet notifying the users gently that they have not met the pre-conditions of a mandatory upgrade. Keep in mind this is a one off stay current exercise.

The image below is customization based on individual needs but its a screenshot of what I created in Photoshop.

Screenshot:

Script: