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.