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 Lenovo systems this is pretty simple – 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 Namespace: root/wmi. In order to get this information into ConfigMgr, we need to add the classes to the Default Client Settings Hardware Inventory.
- Open the Default Client Settings, select Hardware Inventory and click the Set Classes button.
- On the Hardware Inventory Classes window, click the Add button.
- On the Add Hardware Inventory Class window, click the Connect button.
- If the system that is running the ConfigMgr Console is a Lenovo, leave the pre-populated computer name. Otherwise type the computer name of a Lenovo system that is current on the network. For the WMI namespace field, enter: root\wmi and check the Recursive box. Enter credentials if connecting to a remote system and click the Connect button.
- On the Add Hardware Inventory Class window, select the following class: Lenovo_BiosSetting 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.
- 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 Lenovo_BiosSetting and click OK.
- On the Default Settings window, click OK.
- Next, create a Custom Client Device Settings, give it the name Workstation Client Settings, select Hardware Inventory (or use a previously created one).
- Click on Hardware Inventory in the left pane and click Set Classes.
- Select Lenovo_BiosSetting and the following fields should be selected: Active CurrentSetting (InstanceName gets selected by default) and click OK. These are the fields that have useful information that we can use for reporting.
- On the Create Custom Client Device Settings window, adjust the desired Hardware inventory schedule and click OK.
- Deploy the newly created Workstation Client Settings out to a collection that contains Lenovo workstation systems. I have one called All Workstation Clients.
- On a targeted Lenovo 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 an entry being inventoried for the newly defined namespace.
- 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 new class and corresponding values have been added.
- Unlike Dell and HP, Lenovo is a bit limited on the information that is provided (sorry Lenovo you get a F in this category). Both Dell and HP show current values and possible values in different fields. Lenovo only lumps the current setting and value in the same field. In order to determine if a machine is UEFI capable you need to look for the SecureBoot setting. This setting was not available on an older T410 (which does not support UEFI), but it is available on a newer T450.
Hopefully you found this post useful and helps you to gather and report on Lenovo specific settings using System Center Configuration Manager.
Originally posted on https://miketerrill.net/
5 thoughts on “How to Inventory Lenovo BIOS and UEFI Settings with ConfigMgr”
Any way to get this from Dell?
I do have something for Dell coming – I have the first part written, just need to finish the second part and then I will publish both of them. Basically, first you need to deploy the Dell Command | Monitor so that the WMI classes and properties get created and populated. Then you can extend the CM hardware inventory to collect the following:
Properties: AttributeName, CurrentValue, IsReadOnly, PossibleValues, PossibleValuesDescription
I hope this is enough to get you pointed in the right direction. Stay tuned for the coming blog posts.
Hey Mike, you got a typo on step 12. HP not Lenovo. Take care!
Anyway to do this for Surface Pro?
Unfortunately, not that I can find.