David - not sure if you ever figured this out, but here you go: https://miketerrill.net/2016/01/31/how-to-inventory-hp-bios-and-uefi-settings-with-configmgr/
-Mike From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Monday, January 4, 2016 7:20 AM To: [email protected]; Patch Management Mailing List ([email protected]) <[email protected]> Subject: [mssms] RE: BIOS MOF and settings in SCCM 2012 R2 If it's an existing WMI class created by the vendor, there's no MOF needed. Just add the class to your hardware inventory in your client settings. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of David McSpadden Sent: Monday, January 4, 2016 7:55 AM To: [email protected]<mailto:[email protected]>; Patch Management Mailing List ([email protected]<mailto:[email protected]>) <[email protected]<mailto:[email protected]>> Subject: [mssms] BIOS MOF and settings in SCCM 2012 R2 Running this on each machine in a ps script gets me the value I need to see that the BIOS boot order has been changed to HD first then CD then USB. I would like to know if a MOF for HP_BIOSSetting has been created already and if so how do I query SCCM 2012 R2 to get a report of the workstations settings for this key? I need to show that all have the correct boot order and BIOS password set. From: David McSpadden Sent: Friday, January 1, 2016 10:45 PM To: David McSpadden <[email protected]<mailto:[email protected]>> Subject: Bios Get-WmiObject -Namespace root/hp/instrumentedBIOS -Class hp_biosSetting | Where-Object {$_.Name -eq 'Legacy Boot Order'} This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email.
