Home » Drive Download automation » Getting Win10 drivers to enterprise systems

Upgrading windows 7 or 8 OS to windows 10, upgrade process certainly does a good job along with the retention of current data and applications. When it comes to drivers, those were working fine with earlier OS, surprises keep coming up unless a separate process ensures drivers are also upgraded to windows 10 specific version. Windows update can help doing that. However, in case of enterprise environment with system configured towards SCCM SUP as the windows update point, things go out of luck as newer version SCCM servers no longer holds driver update catalogues. This brings the need to address driver related issues like abrupt systems shutdown, BOE etc. as part of windows 10 migration.

Asking users to visit vendor support portal and fetch the required drivers, certainly an option I would not suggest. Instead making them available in an intranet portal with way to download them effortlessly would sure would help. I succeeded doing the same for Lenovo and HP system. In case of Lenovo, the ThinkVantage Update Retriever tool would allow downloading drivers for predefined system model collections. Here is the field to define the models in toll

Instead of entering them manually one by one, a text file saved with the extension “.ur” in the format of <first four character of machine type>#<operating system>#<Model Description for reference> can be used to import all the required models

Sample .ur file content

2325#Windows 10#Thinkpad X230
20DS#Windows 10#TP-L450
20AS#Windows 10#TP-L440
20AM#Windows 10#TP-X240
2466#Windows 10#TP-L430
10CT#Windows 10#TC-M79
10JA#Windows 10#TC-M79

Post import of the file above

Once defined, update retriever tool would download the update repository list and then the updated into defined Repository location as bellow.

Downloading all of them to a single folder saves space as many of them would be applicable to multiple system. However, to share with user it creates a problem as that need to be presented in model specific folder structure. That way user can visit to their model specific folder and download the updates. It does provide export option but that with each updates expanded to their individual files contains, something that can be used for INF file injection requirement but not for downloading over a web browser. Fortunately for the updates it retrieves, it creates a master database XML file at the root of the repository folder. Each update has their own detailed XML file and is linked to the master database XML.

Through a PowerShell script, these XML files can be processed and updates can be copied to their respective model specific folder. In addition, download all text and download all PowerShell script can be prepared as part of this process. One idea could be to link them from the repository folder instead of creating duplicates, to save disk space. Instead, Dedup enabled on D drive takes care of the disk space saving and making it simple this way and also helps visualizing the updates by model name. In my case here, all the model specific folders are created under D:\Driver\Lenovo and same is exposed through IIS with directory browsing enabled for user and installation engineers to download them, either individually or all of them using the PowerShell script in the folder.

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *

*
*