Same here! We’ve had to update BIOS many times over the years to fix specific problems that were seen in the environment. One recent example was on new Dell laptops causing critical failures with a specific McAfee product. It’s better to have a standard process in place to keep things as current as possible… and hopefully avoid some of the problems in the first place.
From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Monday, May 11, 2015 12:50 PM To: [email protected] Subject: RE: [MDT-OSD] Winpe bitness and OS Deployments Lenovo shop here, have had to do BIOS updates on the Twist, Yoga, L440, and T540p to resolve issues with PXE, sound, and HDD issues. All of these are in the past 2 years. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Joshua Delaughter Sent: Monday, May 11, 2015 1:46 PM To: [email protected]<mailto:[email protected]> Subject: Re: [MDT-OSD] Winpe bitness and OS Deployments I'm the opposite, but I see how that can be risky. For example though, the Latitude E6430s have a bug with UEFI and secure boot on a docking station, in which the video doesn't show up until the login screen. This means bitlocker, or system passwords would sit there waiting, and the user didn't even know. The latest BIOS for that model fixes it. I also noticed the E6440 does the same thing. So there could be other fixes that I might not need at that time, but they're still problems none the less, so is rather have the fixed rev than to face possible problems later on. Sent from my iPhone On May 11, 2015, at 12:27 PM, David Landry <[email protected]<mailto:[email protected]>> wrote: I agree …. Why update the BIOS? I did that back in the old days (3.1,95,98, NT, maybe 2000). But I “never” update the BIOS now a days unless there is some functionality that is needed …. Which never happens. BIOS out of the box is fine 99.9% of the time From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Niall Brady Sent: Friday, May 08, 2015 4:38 PM To: [email protected]<mailto:[email protected]> Subject: Re: [MDT-OSD] Winpe bitness and OS Deployments why update the bios at all, unless it's needed, is it ? On Fri, May 8, 2015 at 10:29 PM, Miller, Todd <[email protected]<mailto:[email protected]>> wrote: I used to use 32bit WinPE to deploy both 64bit and 32bit OSes. But something happened a few months back where I had to switch so that the bitness of WinPE matched the OS being deployed. I think it was caused by driver injection problems, but I can’t remember exactly. I feel like I read the advice on DeploymentResearch.com<http://DeploymentResearch.com>, but I can’t find the post now. Anyway, matching the bitness fixed my problem. Now I am in a little trouble with this because I would like to update the BIOS on Dell computers during OS Deployment and it looks like Dell only has 32 bit versions of the BIOS updates available. I think I cannot run a 32bit executable to update BIOS while I am booted into a 64bit WinPE version. I could briefly boot into a 32bit WinPE boot disk while updating the BIOS and then continue on in WinPE 64bit, but the only two options for rebooting are into the Full OS or into the WinPE boot disk assigned to the Task Sequence. Is there a way for me to reboot into a specified WinPE image, update the BIOS, and then reboot back into the WinPE that is assigned to the task sequence? Is there a way out of this problem? One thing I can think of would be to do the BIOS update as a prehook before the real Task Sequence starts… ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________ The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. [CONFIDENTIALITY AND PRIVACY NOTICE] Information transmitted by this email is proprietary to Medtronic and is intended for use only by the individual or entity to which it is addressed, and may contain information that is private, privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please delete this mail from your records. To view this notice in other languages you can either select the following link or manually copy and paste the link into the address bar of a web browser: http://emaildisclaimer.medtronic.com
