How to Inventory HP BIOS and UEFI Settings with ConfigMgr

HP logo

When starting any operating system deployment project, it is a good idea to know what systems are in your environment so that you can determine which of these systems need to support the new OS. Some systems may need to be replaced, where as others might only need a BIOS UEFI update. It is also a good idea to standardize on the BIOS UEFI settings for each supported model in the environment. This ensures that consistent settings are used so that certain systems management features function correctly (for example, like wake-on-lan).

Now that Windows 10 is here, now is the time to standardize on native UEFI as the default boot mode. When making this switch, it is also important to enable Secure Boot at the same time. But, before you can do that, you need to determine not only what is in your environment, but how each system is configured.

You can inventory these hardware specific settings with System Center Configuration Manager. For the HP systems this is pretty simple and on newer models – this information is already stored in WMI and does not require anything to be installed on the clients for it to be enabled. The information is all stored in the HP Namespace: root/hp/instrumentedBIOS. In order to get this information into ConfigMgr, we need to add the classes to the Default Client Settings Hardware Inventory.

  1. Open the Default Client Settings, select Hardware Inventory and click the Set Classes button.
    01 Default Client Settings
  2. On the Hardware Inventory Classes window, click the Add button.
    02 Hardware Inventory Classes
  3. On the Add Hardware Inventory Class window, click the Connect button.
    03 Add Hardware Inventory Class
  4. If the system that is running the ConfigMgr Console is a HP, leave the pre-populated computer name. Otherwise type the computer name of a HP system that is current on the network. For the WMI namespace field, enter: root\hp\instrumentedBIOS and check the Recursive box. Enter credentials if connecting to a remote system and click the Connect button.
    04 Connect to Windows Management Instrumentation
  5. On the Add Hardware Inventory Class window, select the following two classes: HPBIOS_BIOSEnumeration and HPBIOS_BIOSOrderedList and click OK. This enables us to inventory BIOS UEFI settings (current and possible) and also the device boot order for Legacy Boot and UEFI Boot.
    05 Add Hardware Inventory Class
  6. Back on the Hardware Inventory Classes window, I recommend un-selecting the class for the Default Client Settings (in fact I recommend trimming the Default Client Hardware Inventory Classes down to just a few and target only the necessary classes via Custom Client Setting). We will add them to a Custom Client Settings designed for Workstations. Unselect HPBIOS_BIOSEnumeration and HPBIOS_BIOSOrderedList and click OK.
    06 Hardware Inventory Classes
  7. On the Default Settings window, click OK.
    07 Default Settings
  8. Next, create a Custom Client Device Settings, give it the name Workstation Client Settings, select Hardware Inventory.
    08 Create Custom Client Device Settings
  9. Click on Hardware Inventory in the left pane and click Set Classes.
    09 Create Custom Client Device Settings
  10. Expand HPBIOS_BIOSEnumeration and select the following fields: CurrentValue, DisplayInUI, IsReadOnly, Name, PossibleValues, Value (InstanceName gets selected by default). These are the fields that have useful information that we can use for reporting.
    10 Hardware Inventory Classes
  11. Next, expand HPBIOS_BIOSOrderedList and select the following fields: Name, Value (InstanceName gets selected by default) and click OK.
    11 Hardware Inventory Classes
  12. On the Create Custom Client Device Settings window, adjust the desired Hardware inventory schedule and click OK.
    12 Create Custom Client Device Settings
  13. Deploy the newly created Workstation Client Settings out to a collection that contains HP workstation systems. I have one called All Workstation Clients.
    13 Workstation Client Settings
  14. On a targeted HP system, kick off a Machine Policy Retrieval & Evaluation Cycle and then a Hardware Inventory Cycle. In the InventoryAgent.log on the client, you should find two entries being inventoried for the newly defined namespace.
    14 InventoryAgent log
    15 InventoryAgent log
  15. Back in the ConfigMgr Console, use the Resource Explorer and open up the Hardware inventory for the system that was used in the previous step. Here you will see that the two new classes and corresponding values have been added.
    16 Resource Explorer
    17 Resource Explorer
  16. This information can now be used to show which systems are UEFI capable for your Windows 10 project.
    18 UEFI capable

Hopefully you found this post useful and in an upcoming post I will show you how to modify HP BIOS UEFI settings using System Center Configuration Manager.

Originally posted on https://miketerrill.net/

The Power of Power BI

I wanted a great way to present some Operating System data combined with Secure Boot States and BIOS break downs but was drawing a blank with Report Builder. Then I discovered a really powerful tool called Power BI. It not only lets you create great looking reports, but it also allows them to be interactive.

I started off by creating a nice looking donut with the different operating system versions using Power BI Desktop:

01 Operating Systems donut

Next, I added a pie chart for the Secure Boot State (see my previous post on Inventory Secure Boot State and UEFI with ConfigMgr on how to inventory this data with ConfigMgr):

02 Secure Boot State

Now for the interactive part – when I click on Microsoft Windows 7 Enterprise, the Secure Boot State shows that all of them are running BIOS (notice the dual color portion of the BIOS part of the chart):

03 Windows 7 - BIOS

Clicking on Microsoft Windows 10 Enterprise shows that all of those systems currently have Secure Boot State enabled:

04 Windows 10 Secure Boot On

Whereas on my Microsoft Windows 10 Enterprise 2015 LTSB system I have it turned off (since I only have one system and it is the only one reporting that Secure Boot is disabled the entire pie area darkened vs. only part of it when you have more than one system meeting that criteria):

05 Windows 10 LTSB Secure Boot Off

And with my two Microsoft Windows 8.1 Enterprise systems, one has Secure Boot enabled and the other running is still running BIOS:

06 Windows 8.1 Secure On and BIOS

As you can see, this is a powerful new way to look at data. Get started today by heading over to powerbi.microsoft.com and be sure to check out Ronnie Jakobsen’s post, of Coretech, on Hardware overview with Power BI.

Originally posted on http://miketerrill.net

Windows 10 Enterprise LTSB to CB/B

In this video I will show you that it is possible to go from Windows 10 Enterprise 2015 LTSB to Windows 10 Enterprise CB or CBB. This process is simply an in-place upgrade – much like going from Windows 10 1507 (July 2015 release – build 10240) to Windows 10 1511 (November 2015 Update – build 10586), where the apps and user data is preserved.