Any love for Lenovo based builds anyone? On Thu, Jun 23, 2016, 6:56 AM Mattias Benninge <[email protected]> wrote:
> Awesome work Mike! Will definitely try this when I get some spare time! We > havnt started our Win7-Win10 Project yet so I'm sure this will help a lot > and we use Dell! > /Matt > > Regards > Mattias Benninge > http://myitforum.com/myitforumwp/author/matbe/ > > > On Wed, Jun 22, 2016 at 10:59 PM, Mike.Beckel <[email protected]> > wrote: > >> Here’s how we’re approaching BIOS2UEFI when migrating to Windows 10 >> >> >> >> http://mikebeckel.com/Win10-BIOS2UEFI-In-A-Single-TaskSequence/ >> >> >> >> -Mike >> >> >> > *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Michael Niehaus >> *Sent:* Friday, June 10, 2016 3:31 PM >> *To:* [email protected] >> > >> *Subject:* RE: [BULK] Re: [MDT-OSD] Change to UEFI >> > >> >> And yes, on the UEFI vs. BIOS item, how the system is booted determines >> which step executes. >> >> >> >> Thanks, >> >> -Michael >> >> >> >> *From:* [email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *Daniel Ratliff >> *Sent:* Friday, June 10, 2016 9:56 AM >> >> *To:* [email protected] >> *Subject:* RE: [BULK] Re: [MDT-OSD] Change to UEFI >> >> >> >> Pretty sure with Win10 you don’t need UMDF or KMDF anymore, its native, >> or atleast doesn’t require a separate package loaded into the OS. >> >> >> >> *Daniel Ratliff* >> >> >> > *From:* [email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *David Landry >> *Sent:* Friday, June 10, 2016 12:40 PM >> *To:* [email protected] >> > >> *Subject:* RE: [BULK] Re: [MDT-OSD] Change to UEFI >> > >> >> I am now just starting to switch over to UEFI for all our systems. It is >> my understanding that these two (screen shot below) settings, >> >> >> >> >> >> which are automatically included in any new MDT 2013 Task Sequence, is >> all you need to format the disk accordingly? >> >> >> >> From what I can tell, and please let me know if I am wrong, “How” you >> boot into MDT is the determining factor. Meaning a normal boot with normal >> BIOS settings (Legacy /AHCI) will get you “Format and Partition Disk >> (BIOS)” and if boot up using UEFI boot stick with BIOS settings UEFI and >> RAID On will use “Format and Partition Disk (UEFI)”? >> >> >> >> I understand what you are doing / trying to do with working the changing >> of BIOS settings into the task sequence. >> >> >> >> On a slightly different subject, With Windows 7 we use >> Umdf-1.11-Win-6.1-x64 and kmdf-1.11-Win-6.1-x64. What do we use for windows >> 10 systems? >> >> >> >> These links: >> >> >> >> >> https://msdn.microsoft.com/windows/hardware/drivers/wdf/kmdf-version-history >> >> >> https://msdn.microsoft.com/windows/hardware/drivers/wdf/umdf-version-history >> >> >> >> Indicate to use UMDF Version 2.15 or 2.17 and KMDF Version 1.15 or 1.17. >> Problem is, I cannot find either of these versions and 1.11 versions are >> not supposed to be compatible with Windows 10. Do these new versions exist >> to be downloaded? I can’t find them. >> >> >> >> >> >> >> >> *From:* [email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *Mike.Beckel >> *Sent:* Friday, June 10, 2016 10:36 AM >> *To:* [email protected] >> *Subject:* Re: [BULK] Re: [MDT-OSD] Change to UEFI >> >> >> >> It’s a format & partition. >> >> >> >> >> >> >> >> *From: *<[email protected]> on behalf of Mike Terrill < >> [email protected]> >> *Reply-To: *"[email protected]" <[email protected]> >> *Date: *Friday, June 10, 2016 at 7:29 AM >> *To: *"[email protected]" <[email protected]> >> *Subject: *RE: [BULK] Re: [MDT-OSD] Change to UEFI >> >> >> > “Overall all we were able to convert MBR to GPT and BIOS to UEFI as part >> of this process.” [Mike B] >> >> >> >> Not sure if you mean that your solution is ‘converting’ the disk vs. >> doing a ‘format & partition’, but I would steer clear of the ‘converting’ >> solutions as they are not supported by Microsoft. >> >> >> > *From:* [email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *Mike.Beckel >> *Sent:* Wednesday, June 8, 2016 12:24 PM >> *To:* [email protected] >> > >> *Subject:* RE: [BULK] Re: [MDT-OSD] Change to UEFI >> > >> >> So there’s two Mike’s and two solutions >> >> >> >> 1) Mike T from 1E presented a solution at MMS which requires 1E >> Nomad >> >> 2) Mike B (that’s me) and my team developed a solution that we’re >> working on making available on GitHub. >> >> >> >> -Mike >> >> >> >> *From:*[email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *Todd Hemsell >> *Sent:* Wednesday, June 8, 2016 1:39 PM >> *To:* [email protected] >> *Subject:* Re: [BULK] Re: [MDT-OSD] Change to UEFI >> >> >> >> are you with 1E now? >> > On Thu, Jun 2, 2016 at 3:16 PM, Keith Garner (Hotmail) < >> [email protected]> wrote: >> > Yes, Mike (and I) have a single BIOS to UEFI task sequence working right >> now. We announced, at MMS 2016, availability in Q3 2016. >> >> >> >> Please note that “single UEFI Task Sequence” is just the **first** step >> in the process to convert your Windows 7 BIOS machines to Windows 10 UEFI. >> >> I can think of about a half a dozen technical challenges (OEM Specific >> commands, Application Mapping, MBR to GPT, etc…), that need to be >> addressed, and we are currently working that End-to-End solution. >> >> >> >> -k >> >> >> >> *From:*[email protected] [mailto: >> [email protected]] *On Behalf Of *Brucker, Chris >> *Sent:* Wednesday, June 1, 2016 6:44 AM >> *To:* [email protected] >> *Subject:* RE: [BULK] Re: [MDT-OSD] Change to UEFI >> >> >> >> Sorry to reply to an older thread, but I was curious if Mike received >> permission to share the single UEFI task sequence? If not, I would be fine >> with a high-level overview of the steps that you are taking to complete it >> in one shot, hopefully I could pick it up from there. I am planning our >> Windows 10 upgrade for ~2000 Dell PC’s and would love to leverage this in a >> task sequence. So far I have only been able to duplicate what Mike Terrill >> and others in the community have done with 2 sequences. >> >> >> >> Thanks, >> >> Chris Brucker >> >> >> >> *From:*[email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *Mike.Beckel >> *Sent:* Friday, May 6, 2016 1:38 PM >> *To:* [email protected] >> >> >> *Subject:* RE: [BULK] Re: [MDT-OSD] Change to UEFI >> >> >> >> I have a little more work to do to prove that it’s rock solid, but my >> team and I just got it working with one TS on a Dell system. Overall all we >> were able to convert MBR to GPT and BIOS to UEFI as part of this process. >> >> >> >> Once I finish up validating the process across a few more models and the >> lawyers give me the go-ahead I’ll share (hopefully around MMS). >> >> >> >> -Mike >> >> >> >> *From:*[email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *Kevin Johnston >> *Sent:* Thursday, May 5, 2016 1:01 PM >> *To:* '[email protected]' <[email protected]> >> *Subject:* RE: [BULK] Re: [MDT-OSD] Change to UEFI >> >> >> >> We just started down this road. Had to create 2 task sequences, >> leveraging Mike Terrill’s blog. >> >> >> >> So currently we run the first TS, and then it reboots and then we select >> the windows 10 TS. >> >> >> >> >> https://miketerrill.net/2015/08/31/automating-dell-bios-uefi-standards-for-windows-10/ >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__miketerrill.net_2015_08_31_automating-2Ddell-2Dbios-2Duefi-2Dstandards-2Dfor-2Dwindows-2D10_&d=CwMGaQ&c=WE0At5E24laHU5j4-pDiGCY8tBHoG528XbY2mQA7QzI&r=1PQtgD4rMoHBI9wGXS5RjtJCnC_HUSxR5kLNDPYWBYc&m=06VJWht7pRgJuotIrOcd-0xRBSLJO8dB3L2noL8t-Ko&s=LR6y64AJfLi3HiVe_Kgasp6XflOU-vmCnCV4Yiq-ouc&e=> >> >> >> >> >> >> KEVIN JOHNSTON >> >> >> >> *From:*[email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *Roger Truss >> *Sent:* Thursday, May 05, 2016 11:54 AM >> *To:* [email protected] >> *Subject:* [BULK] Re: [MDT-OSD] Change to UEFI >> *Importance:* Low >> >> >> >> I am forcing my teams to manually enble what is needed, since lenovo no >> longer supports scripting secureboot. I have a powershel script to check >> for secureboot and prompt/fail accordingly. Works rather nicely too. >> >> >> >> On Thu, May 5, 2016, 9:34 AM Marcum, John <[email protected]> wrote: >> >> There’s been a ton of discussion on this subject, the common thing I’ve >> seen people say is that cannot be done in a single TS. However, I saw >> something just this week that make me think that 1e will soon make an >> announcement around this topic. >> >> >> >> >> >> >> >> >> >> >> >> *From:*[email protected] [mailto: >> [email protected]] *On Behalf Of *Keith Garner (hotmail) >> *Sent:* Wednesday, May 4, 2016 6:18 PM >> *To:* [email protected] >> *Subject:* RE: [MDT-OSD] Change to UEFI >> >> >> >> Yes, reboot, then repartition the Hard Disk to GPT. >> >> >> >> As long as you boot into WinPE on the next round in UEFI mode, MDT >> LiteTouch and SCCM OSD will handle the rest, including cleaning the disk >> for GPT for New Computer scenarios. >> >> >> >> Little ‘r’ me if you are doing refresh/wipe-and-load keith [dot] garner >> [at] 1e [dot] com >> >> >> >> >> >> *From:*[email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *Wolf, Daniel >> *Sent:* Wednesday, May 4, 2016 3:33 PM >> >> *To:*[email protected] >> *Subject:* [MDT-OSD] Change to UEFI >> >> >> >> Hello everyone, >> >> All our Dell machines are BIOS instead of UEFI. I want to change this to >> UEFI with SecureBoot when we deploy Windows 10. >> >> >> >> During the task sequence, if I use Dell’s tool to change BIOS to UEFI and >> enable SecureBoot, do I need to reboot before I install Windows? >> >> >> >> Thank you, >> >> Daniel >> >> >> ------------------------------ >> >> >> Confidentiality Notice: This e-mail is from a law firm and may be >> protected by the attorney-client or work product privileges. If you have >> received this message in error, please notify the sender by replying to >> this e-mail and then delete it from your computer. >> >> The information contained in this message from First Financial Bancorp or >> its affiliates and any attachments are confidential. It is not intended for >> transmission to, or receipt by, anyone other than the addressee(s), or a >> person authorized to deliver it to the named addressee(s). If you have >> received this message in error, you are prohibited from copying, >> distributing or using the information. Please contact the sender >> immediately by return email and delete the original message. >> >> >> ------------------------------ >> >> >> >> Legal Notice: This email is intended only for the person(s) to whom it is >> addressed. If you are not an intended recipient and have received this >> message in error, please notify the sender immediately by replying to this >> email or calling +44(0) 2083269015 (UK) or +1 866 592 4214 (USA). This >> email and any attachments may be privileged and/or confidential. The >> unauthorized use, disclosure, copying or printing of any information it >> contains is strictly prohibited. The opinions expressed in this email are >> those of the author and do not necessarily represent the views of 1E Ltd. >> Nothing in this email will operate to bind 1E to any order or other >> contract. >> > >> 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. >> >
