Dell Firmware updates - Yellow Bricks. Holy smoke! This thread started off with a BIOS update that lead to a FIRMWARE update that lead to a SUU update that lead to the UEFI update that lead to an i. DRAC update that lead to hell and highwater at every turn. ![]() Get support for your Dell product with free diagnostic tests, drivers, downloads, how-to articles, videos, FAQs and community forums. Or speak with a Dell technical. How a Hyper-V VM boots up will dictate a lot, especially if optical media are interchanged. IT pro Rick Vanover shows a few ways to manage boot order for Hyper-V. 24 Responses to “How To Make An Unattend.xml Sysprep File” Mark Says: January 20th, 2011 at 10:45 am. You probably should mask your product key. I confess to having five R7. BIOS and FIRMWARE. The experience to get to there from here was the nightmare incarnate referenced (and footnoted) above. Then I shifted gears and found a BDP utility somewhere and as all things Dell promising the world, I managed to download it and make it work on a Win. It gives the option of creating a bootable USB or CD from the . ISO packaged in the ZIP file. Sounds simple eh? Well, when Dell says CD, it means CD. While it may write to a DVD, it won’t work the same. That was just for starters, leaving me to hunt around for a CD- RW I could erase and re- use. Yikes! Then, pressing F- 1. OPTICAL DRIVE as boot device, I found it worked just as quickly and seamlessly as anyone will remember using 3 1/2 floppies. Strange as it may sound, a colleague suggested I borrow his USB Floppy just for this occasion. I declined of course because all of my 3 1/2 floppy material is indeed Museum- Grade and therefore it is too difficult to decide which one I will discover will fail after all these years to re- use. Back to the BDP. It was written for BIOS 6. The obvious problem rose up when Dell released 6. I haven’t seen the BDP for this version… yet. However, that is and should not be the case. The BDP unfortunately writes Dell’s secrets to a CD (not DVD or successful at least with my old burner etc) that cannot be read. In fact, all you see is the NOTEPAD title and descriptor and while this threw me a curve, it was not one that was unhittable. The first problem I had with the BDP was that it wrote to the CD, but contained no data. Seems the braintrust sprung a leak while making the make- image and copied only the files in the BIOS subdirectory. Missing the BIOS file, this of course meant the BDP CD v. Using the command prompt in Win. I managed to copy the files to the BIOS sub- directory and then use the GUI to make another CD (v. This worked like a charm. The F- 1. 1, Optical options chosen found the Optical drive, opened the BIOS utility and executed the program without a hitch. Now then, wouldn’t it be so nice to create a folder in the BDP utility to permit loading any or all of the firmware; even only BIOS if necessary, AND permit the editing of the Autoexec and/or other DOS- like menu files which would permit mouse selection of the appropriate BIOS at Pause after BOOT! I mean they are already 8/9ths of the way there, why stop now? So many secrets, so little time. Since the CD image requires physical access to the server and it takes over five minutes to shut down, restart, update and reboot, it seems more than reasonable that this is indeed a secure enough method to protect the secrets held in the bowels of my testbeds. At the same time, why not update the BIOS itself to permit USB boot, since it is possible after jumping through a number of flaming hoops. Lastly, realizing the game- plan was/is to make money and accelerate the obsolescence to that end (which doesn’t make sense to the poorest of IT minions; UNFAIR actually) it seems by the volume of complaint messages that Dell would have made a killing selling the BDP for $1/ per person per instance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
September 2018
Categories |