LENOVO DRIVER UPDATE CHECKER INSTALL

ThinInstaller and System Update have bugs, I've seen it refuse to install BIOS updates silently despite it being possible, reboot despite not selecting reboot packages, fail to install updates because of typos in the command syntax etc.

ThinInstaller logs are very hard to parse text files so it's nearly impossible to tell whether an update run was successful.

With this module you get to Get-LSUpdate | Where-Object and can build any filter logic you want - ThinInstaller only allows by reboot type and by severity

ThinInstaller doesn't give you the same level of filtering and control.

You still have to maintain a repository - add new computer models as they're released, eventually clean out old ones, regularly update the packages etc - so it's not zero effort.

Hi, no worries I'm aware of ThinInstaller and Update Retriever - I evaluated that method before deciding I had to create this. Please share your feedback, I am actively using this and looking to improve, xml files (possibly more in the future) from /* ! If you do work in IT and use a WebProxy to filter your traffic you will need to allow downloads including.

LENOVO DRIVER UPDATE CHECKER DRIVERS

What I do now is deploy new machines with WDS + MDT, then let PDQ-Deploy install some base software and run this module to get all drivers and UEFI patched up - no housekeeping required, all updates are always the latest fetched directly from Lenovo.

LENOVO DRIVER UPDATE CHECKER MANUAL

The official Lenovo System Update tool has a CLI, but it's buggy, unreliable, produces very hard to parse log files, installs a service that runs as SYSTEM, uses the proxy settings of the currently logged in user with no manual override, runs graphical update wizards and waits for NEXT when you told it to be silent, etc etc - believe me, I've tried it.

Even if you somehow automate the process of getting drivers for new computer models and importing them into MDT, you still have no way of keeping those machines updated once they're out in the field.

Manually pre-downloading drivers for every model and adding them to MDT is a pain.

Lenovos SCCM packages are out of date and only available for some models.

I hope this will be as helpful for some of you as it has been for me - no matter which option for driver deployment you choose, none is perfect:

Since I know my /r/sysadmin friends - yes you can run it remotely with PDQ Deploy!.

Accounts for and works around some bugs and mistakes in the official tool.

Ability to download updates in parallel.

Web-Proxy support (Use -Proxy parameter).

Supports not only business computers but consumer (e.g.

Allows for fully silent and unattended updates.

Run locally or through PowerShell Remoting on another machine.

Does driver, BIOS/UEFI and firmware updates.

My new module - LSUClient - is a PowerShell reimplementation of the Lenovo System Update program and it has allowed me to easily and fully automate driver deployment to new machines as well as continuously keeping them up to date with 0 effort.

Research Triangle Powershell User Group remote-capableДЄs I've been hinting at I had something in the works for everyone who owns or works with Lenovo computers - like myself!.

Philadelphia PowerShell User Group remote-capable.

Madison Power Users Group remote-capable.

Denver Microsoft Enterprise Management User Group.

NET, POSH is a full-featured task automation framework for distributed Microsoft platforms and solutions. Windows PowerShell (POSH) is a command-line shell and associated scripting language created by Microsoft.

LENOVO DRIVER UPDATE CHECKER HOW TO

Submission Guidelines | Link Flair - How To

Lenovo driver update checker