Being able to remotely power on a lab, building or even a single remote computer is a huge time saver!
Configuring boot options means only allowing approved devices to be booted from.
I would never recommend flashing a BIOS on a laptop with a low battery. Type the name of the flash utility followed by /forceit /forcetype.
But first – let’s see what we need to configure and how we can do it. If you have ever had a user configure a hard drive or startup password, you certainly understand why you should set a BIOS password.
Configuring Wake on LAN is another option that should be universally configured.
In our environment, you can only boot off of the hard drive or the NIC.
This keeps users from booting to a OS on a thumb drive or using a password cracker CD against our administrative accounts.
For those who use a different OS, the update procedure requires some extra steps.
First of all, copy the update file to a bootable DOS USB drive.
This week I had that very problem and wondered if I could perhaps deploy the BIOS EXE file via a Win PE environment and bypass the “installed” Windows need totally.
The “trick” seems to be that you have to use an x86 Win PE OS architecture build, rather than a x64 Win PE flavor. If you already have a working Win PE build and want to confirm (maybe you didn’t build it yourself) just run the following command in your loaded Win PE environment from a command prompt: Sadly, the Dell LTI bootable flash drive I had was running a x64 version.
And more importantly kept in mind the overall process needed when multiple versions of a BIOS Update may be required (from A01 to Axx).