yeah that's fine for legacy but it won't work for 64bit UEFI devices, they won't boot with an x86 boot image.
On Sat, May 9, 2015 at 10:53 PM, Keith Garner (hotmail) < [email protected]> wrote: > If I recall correctly, you should be able to install an x64 image from x86 > WinPE, dism /apply-image, /add-package, and /apply-unattend should be > bitwise agnostic. > > > > Is there a specific problem you are seeing? > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Daniel Ratliff > *Sent:* Saturday, May 9, 2015 11:15 AM > > *To:* '[email protected]'; '[email protected]' > *Subject:* RE: [MDT-OSD] Winpe bitness and OS Deployments > > > > We can't even do it in WinPE with Lenovo. > > -----Original Message----- > *From: *Underwood, Bob [[email protected]] > *Sent: *Saturday, May 09, 2015 11:30 AM Eastern Standard Time > *To: *[email protected] > *Subject: *RE: [MDT-OSD] Winpe bitness and OS Deployments > > > We’ve been asking Dell to support 64-bit WinPE for BIOS flashing for years > now, and not made any headway. You can do it before the OS is applied on > HP devices, but we had to move it to the middle of the process for Dell > machines. (We moved to 64-bit media a couple of years ago to support UEFI > and Windows 8.) > > > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of* Miller, Todd > *Sent:* Friday, May 8, 2015 5:12 PM > *To:* [email protected] > *Subject:* RE: [MDT-OSD] Winpe bitness and OS Deployments > > > > The BIOS updates might be required for Bitlocker, and I would like to be > able to pre-enable bitlocker before the OS is laid down to take advantage > of the time savings. > > > > *From:*[email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of* Daniel Ratliff > *Sent:* Friday, May 08, 2015 3:48 PM > *To:* '[email protected]'; '[email protected]' > *Subject:* RE: [MDT-OSD] Winpe bitness and OS Deployments > > > > Move your bios update to inside the os? > > -----Original Message----- > *From: *Niall Brady [[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]> > 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. > > > ------------------------------ > > 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. > ------------------------------ > > [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 > > > 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. >
