There are various scenarios where one might want to quickly generate a local repository of Lenovo updates that can be consumed by Thin Installer or System Update in a scripted manner. This article will describe a PowerShell script that can be leveraged to create a repository for a specified machine type and OS. A scenario where this script might be used will also be described.
As of today, there's still a limitation within the Intune portal to easily find the friendly name of a Lenovo system, i.e. ThinkPad T14 Gen 3. Instead, you're left with the Machine Type Model (21AH).
I'm sure there's a small group of people, if any, that have memorized what every MTM translates to for its respective friendly name.
To make this a bit easier, and with the help of Damien Van Robaeys' blog post, we can use the Graph API to populate the device notes property of an Intune device by matching the Model (aka MTM) to its friendly name.
This post will walk through deploying a Remediation script that will collect data from specific Lenovo WMI classes using the HTTP Data Collector API. As a result, the data will be sent to a Log Analytics Workspace in Azure Monitor.
Continuously growing log files generated by the Qualcomm X55 WWAN service. These logs are located under %ProgramData%\Qualcomm® Snapdragon™ X55 5G Modem\SVClog
For the unaware, Lenovo provides a Windows Utility to Read and Write Asset ID Information, specifically for ThinkPad. With this utility, you are able to set asset ID data such as an Owner Name, Owner Location, Asset Number and several other pieces of information.
The future of package management for Windows is Windows Package Manager. This simplifies the installation and management of applications using the winget tool.
In some scenarios, there may be the desire to leverage the Lenovo Updates Catalog to apply applicable updates during an OS deployment task sequence. This article will cover how this might be achieved.
This is a PowerShell based solution that will query the ConfigMgr database for Lenovo branded products and create a Device Collection based off the friendly name, i.e. ThinkPad T14 Gen 2. Each device will then be moved to its respective collection.
This is a follow up to a previous article that walked through hosting an on-prem Update Retriever repository in an Azure Blob Storage.
If you've started leveraging cloud storage for your driver repository, this solution may be of interest to you if you're at a roadblock with how to deploy BIOS updates to your endpoints.
The main focus of this article is a rather hot topic: Silently installing BIOS and firmware updates.
There are numerous articles out in the community that walk through how to configure BIOS settings through Intune. The majority of them being PowerShell solutions.
This post will provide an alternate method for configuring BIOS settings using our official Think BIOS Config HTA that was introduced back in 2016. This solution can also be leveraged as part of an Autopilot deployment.