Move your bios update to inside the os?

-----Original Message-----
From: Niall Brady [[email protected]<mailto:[email protected]>]
Sent: Friday, May 08, 2015 04:40 PM Eastern Standard Time
To: [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, 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.

Reply via email to