What Niall describes is exactly what we are seeing.
There is no HP uniqueness to this apart from the fact that all of our desktops are HP and all of the laptops Lenovo. UEFI is only enabled on the HP systems. In this case the scenario is: . Deploying Win7 x64 . Using WinPX x64 boot image . Some systems are marked as UEFI. On these we are able to deploy Windows . When we rebuild (as in lab systems) we see multiple entries in the Boot Loader . Windows still works and normally a user would be unaware . In order to resolve the issue simply following the instructions to clear out duplicates and reimport (referenced below) resolves the issue. . The importable BCD now appears to be portable so it looks like it's simply a case of packaging and targeting a system with a BCD I do have an (un)related issue WRT to importing the HP WinPE x64 drivers into the boot image however in that they error in the DISM process so at the moment we are deploying to UEFI/IDE and UEFI/AHCI. I also have another issue where when we partition to UEFI/GPT AND check the checkbox to "make this the bootable disk" the build completes but the boot loader cannot access the drive while id we leave the check-box unchecked and set the Task Sequence Variable it works. Hope that helps Jason From: [email protected] [mailto:[email protected]] On Behalf Of Niall Brady Sent: 17 December 2013 16:14 To: [email protected] Subject: Re: [mssms] UEFI systems - multiple Windows Boot Loader entries this issue occurs only on UEFI systems that are imaged with a UEFI capable OS and UEFI capable task sequence, when the new image is laid down, a new entry is added to the BCD store resulting in one or more entries on bootup, if you are imaging a test system 10 times, you'll have 10 entries On Tue, Dec 17, 2013 at 4:01 PM, Trevor Sullivan <[email protected]> wrote: So, can someone start from the beginning and explain the situation / scenario? . Are you using MDT, ConfigMgr, or both together? . Which OS are you deploying? . Under what circumstances do multiple boot loader entries show up? . Does it happen on UEFI, legacy BIOS, or both? . What other configuration parameters are worth calling out? Cheers, Trevor Sullivan From: [email protected] [mailto:[email protected]] On Behalf Of Kent, Mark Sent: Tuesday, December 17, 2013 8:54 AM To: [email protected] Subject: RE: [mssms] UEFI systems - multiple Windows Boot Loader entries Same on Dell Mark Kent (MCP) Sr. Desktop Systems Engineer Computing & Technology Services - SUNY Buffalo State From: [email protected] [mailto:[email protected]] On Behalf Of Niall Brady Sent: Tuesday, December 17, 2013 9:43 AM To: [email protected] Subject: Re: [mssms] UEFI systems - multiple Windows Boot Loader entries not just HP, i've seen it on lenovo On Tue, Dec 17, 2013 at 3:40 PM, Trevor Sullivan <[email protected]> wrote: Jason, Can you provide some background on this issue? What makes this issue unique to HP systems? This is news to me, and I am interested in learning. Cheers, Trevor Sullivan From: [email protected] [mailto:[email protected]] On Behalf Of Jason Wallace Sent: Tuesday, December 17, 2013 2:48 AM To: [email protected] Subject: [mssms] UEFI systems - multiple Windows Boot Loader entries Hello folks Noticed that on our HP UEFI based systems in the lab now have multiple entries for Windows Boot Manager as we rebuild them. I know this is a HP related issue rather than CM but any suggestions for removing these entries please? The usual suspects of reload defaults and disable & enable UEFI do not help Jason
