This in my opinion sounds like setting yourself up for headaches. If it were me, I'd put a test in the beginning of the task sequence that checks the BIOs version and fail out cleanly if it isn't at a good version. Then have a "utility" task sequence that the desktop techs can run that is 32bit and can be used to update the BIOs. Then kick off the build again.
That's just me. Mike From: [email protected] [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Wednesday, August 17, 2016 1:01 PM To: [email protected] Subject: [MDT-OSD] Modify boot image assigned to TS on the fly? Currently I am not able to update BIOS until I am in the full OS since Dell BIOS update is a 32bit application. There was talk in forums about releasing 64bit versions of BIOS update tools, but 7 years has passed with no action. Usually, updating BIOS is OK to do after the OS is loaded, but there are times when an out-of-date BIOS is a block to the installation of Windows and in those cases it would be great to deploy an updated BIOS before we reboot into the full OS. So after the task sequence starts I'd like to be able to stage different WinPE image depending on whether I want to reboot into 32bit WinPE or 64bit WinPE. It would be cool to specify the WinPE boot disk to stage in the reboot step rather than have it be locked in for the whole Task Sequence. Does anyone know of a way to change the boot image assigned to a task sequence on the fly, and let it get restaged by the Reboot step? Do you think the work being done with nested Task Sequences might eventually help? Will it allow the nested TS to have a different WinPE boot disk assigned to it and restage WinPE before reboot steps in the nested TS if the clild TS has a different WinPE boot disk assigned to it than the parent TS? ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy all copies of the original message and attachments thereto. Email sent to or from UI Health Care may be retained as required by law or regulation. Thank you. ________________________________ ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
