Enabling EFI/Boot password

New Policy>> EFI Password Payload.

Great .. how can I get the list of machines that have Firmware password set ?

Make an extension attribute with this:

#!/bin/sh

#Get Status
firmwareStatus=$(firmwarepasswd -check)

#Pull out final word
status=$(echo "$firmwareStatus" | awk '/Enabled:/ {print $NF}')

echo "<result>$status</result>"

Possible outputs are Yes and No ^

Thanks a million

any updated version of check a script that would work with Big Sur on intel machines?

@MacJunior The EA I posted above still works in Big Sur on Intel Macs.

true, when I execute the script on a machine has a firmware password it shows me the status "Yes" but I when add it to an extension attribute and create a smart group to show me the macs with EFI password nothing shows up.
Seems I'm doing something wrong here.

@MacJunior safe to assume you are waiting for the next recon/inventory to come in? If you run recon/inventory on a machine, is it showing up in your Computer Record?

Hi @DBrowning I tried setting up an extension attribute as you provided up here but seems like it is not working, attaching the screenshot. same result in catalina and bigsur. Nothing won't populate even after jamf recon.

EDIT: After waiting a while and after a Recon it actually populated correctly.

I executed "jamf recon" from terminal and waited a bit, rebooted and still the the smart group shows me nothing !

Anybody managed to fix it ? still can't see Macs that have FV enabled !

Try
echo "<result>$status</result>"

Still nothing, does it work for you @mschroder ?? if yes could you share the extension attribute page and the smart group ?

Well, you have a 'sudo' in a place where it makes no sense. DBrowning has the complete and correct script in his post. Please note that if you run this outside of Jamf you need to run it with sudo privileges. When from the MDM it already has sudo privileges.

Once you fixed the EA check you get the proper result in the inventory for the device on which you tested. When that is OK check the smart group, you might have problems there as well.

You are correct @mschroder I missed your point that when you run a script via MDM it doesn't need sudo privileges cuz it's already have them.

Thanks