I don't think it would be too difficult with PowerShell. I use PowerShell to
run the command on my build and capture and select the strings I want for
inventory purposes. You just have to parse a little more text and go from
there. I think the most difficult part would be determining which heading you
are under, {current} {default} etc.
write-output "--------------------------------------------------"
write-output "Verify startup options"
write-output "--------------------------------------------------"
$recovery = bcdedit /enum
if (($recovery | select-string recoveryenabled) -like "recoveryenabled*no") {
write-output "SUCCESS: Recovery is disabled!`n"
} else {
write-warning "Recovery is still enabled!"
write-output "`n"
}
if (($recovery | select-string bootstatuspolicy) -eq "IgnoreAllFailures") {
write-output "SUCCESS: Failures ignored!`n"
} else {
write-warning "Failures not ignored!"
write-output "`n"
}
Daniel Ratliff
From: [email protected] [mailto:[email protected]] On
Behalf Of Jason Wallace
Sent: Tuesday, December 17, 2013 12:41 PM
To: [email protected]
Subject: RE: [mssms] UEFI systems - multiple Windows Boot Loader entries
Hi there Aaron
Thanks for the note. No, this really is just on the test systems which we have
but I'd like to leave the deployment tidy if I can
Jason
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Aaron Czechowski
Sent: 17 December 2013 18:26
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] UEFI systems - multiple Windows Boot Loader entries
Hi Jason -
I'm unfortunately not too knowledgeable on that myself. I know a support
engineer was looking into the same thing, but also got hung up with how to
automate it. Is this something you see frequently on deployed end-user systems,
or is it just during testing?
Aaron
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Jason Wallace
Sent: Tuesday, December 17, 2013 8:52 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] UEFI systems - multiple Windows Boot Loader entries
Hi there Aaron - that is kind of where I am looking right now. We could of
course query the BIOS using manufacturer code but as BCDEDIT is generic then it
would seem to make sense to use this tool. The problem then of course is that
any solution seems to revolve around creating a text file, parsing it and then
doing something with the result. It would be nice to find some more
intelligent way of working with this data.
I know that someone did mention that boot methods change on Surface devices and
I wonder what form that takes? We have had some systems that seemed to boot
back into Legacy but these were HP desktops with scores (yes, really) of
Windows Boot Loader references.
Jason
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Aaron Czechowski
Sent: 17 December 2013 17:36
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] UEFI systems - multiple Windows Boot Loader entries
It can occur with a Hyper-V Gen2 VM or Surface as well. Some investigation
occurred and I think the outcome was an issue with Windows setup. One customer
raised performance concerns, but I think that's anecdotal and not proven to be
related. I think the general belief is that this should not cause any serious
issues. Outside of a test environment where a specific system is refreshed
multiple times, I would not expect to see this done more than once or twice on
a given system.
As you said below, easy enough to script in the task sequence, but I think the
challenge is determining which ones to whack.
Aaron
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Jason Wallace
Sent: Tuesday, December 17, 2013 7:50 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] UEFI systems - multiple Windows Boot Loader entries
:)
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Niall Brady
Sent: 17 December 2013 15:14
To: [email protected]<mailto:[email protected]>
Subject: Re: [mssms] UEFI systems - multiple Windows Boot Loader entries
i just havnt got round to it yet, feel free to be the one
On Tue, Dec 17, 2013 at 3:05 PM, Jason Wallace
<[email protected]<mailto:[email protected]>> wrote:
And there was me hoping that you'd say "Oh, that's easy - go here . . . " :)
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Niall Brady
Sent: 17 December 2013 14:57
To: [email protected]<mailto:[email protected]>
Subject: Re: [mssms] UEFI systems - multiple Windows Boot Loader entries
if you do come up with a solution Jason make sure to blog it please
On Tue, Dec 17, 2013 at 2:50 PM, Jason Wallace
<[email protected]<mailto:[email protected]>> wrote:
Thanks Niall & Rob
Both of those are fab. Now to work out how to automate that for a task sequence
Jason
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Niall Brady
Sent: 17 December 2013 14:43
To: [email protected]<mailto:[email protected]>
Subject: Re: [mssms] UEFI systems - multiple Windows Boot Loader entries
how about
http://jeff.squarecontrol.com/archives/184
On Tue, Dec 17, 2013 at 1:33 PM, Robert Marshall
<[email protected]<mailto:[email protected]>> wrote:
BCDEDIT /DELETE ?
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Jason Wallace
Sent: 17 December 2013 08:48
To: [email protected]<mailto:[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
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.
