Lenovo Think Deploy Blog

This post is expanding on someotherguy's KB article on how to make the F11 functionality work again if you're deploying a custom Windows 10 image in your environment. As of this post, SCCM Current Branch 1702 will be covered. (Note: This is only applicable to Windows 10 configured in UEFI mode) With Think products, pressing the F11 key at boot will launch the recovery utilities. This is available if the system's operating system is preloaded from Lenovo. However, most large enterprise customers re-image the systems with a custom image. Once this happens, F11 will no longer work. As mentioned in someotherguy's KB, an .efi file must be added to the boot folder in the System partition. Here are the steps to accomplish this: 1. Download the LenovoBT.zip file. Extract the contents to a source directory on your site server. 2. In your console, create a new Package that will contain the .efi file. Do not create a program. Distribute the Package to your Dist

Introduction to DriverGrabber DriverGrabber is a "no install" utility that is aimed at simplifying the task of finding drivers and utilities for Lenovo PC products which an administrator needs to package for delivery through their software deployment solution.  By specifying a Machine Type and an operating system you get a list of available updates which can be selected for downloading. This takes much less time than navigating through the Lenovo support web site. Beyond just automating the downloading and extracting of packages, DriverGrabber also shows details such as Version, Release date, Extract command, and Silent Install command.  There is even an option to get MD5, SHA-1 and SHA-2 hash values to help verify complete downloads.  Packages can be selected by clicking the row header.  Hold the Ctrl key down to select multiple packages.  At the bottom of the window specify a download location and then choose to download only or download and extract.  A .CSV file with de

Lenovo's ThinInstaller utilizes 2 Certificates to verify the signatures of packages during deployment. Currently the client machine must have an active internet connection in order to access the certificate necessary for that verification. If the client machines do not have an active internet connection then the certificates need to be installed into the appropriate local certificate store of the client machines prior to running ThinInstaller. If ThinInstaller cannot verify the signatures of certain packages, you will see errors in the logs that contain " Signature Verification Failed ". This is useful if your deployments are done on a closed network environment, lab or closed deployment subnet etc. This document will outline how to download the certificates and deploy them to your client machines during your OSD deployments as a task sequence step using MDT and SCCM. The certificates are available currently as a downloadable zip file here . The zip file shou