12-02-2019 08:49 AM
Thanks. In your professional opinion, what is the best way to get the bios/driver updates for all 3 models on a monthly patch cycle that works with the Microsoft patch Tuesday cycle?
Corey
12-02-2019 09:35 AM
Every environment is different, so this is a tough question. Some customers want to deploy the updates to the environment en masse, others want to test and know the types of interactions their environment may encounter.
That said, I would reccomend using SmartFilters and Composite SmartFilters to get the list of updates to obtain for your models. I would then recommend publishing the updates to a Software Update Group (SUG) using a scheduled task. I recommend using a Phased Deployment to deploy to a controlled test group of devices where the updates would be needed. Then follow the Phased Deployment approach from the Test group to a Pilot group to Production at intervals/thresholds where you feel comfortable.
The updates should have minimal impact, but this strategy should give you the ability to locate any environmental specific hurdles you may encounter.
TLawson
12-02-2019 09:37 AM
I was asking in relation to the inability to pull updates from Lenovo Patch. What other options do we have?
Thank you,
Corey
12-02-2019 12:26 PM - edited 12-02-2019 01:50 PM
There are a few tools you can use to supplement Lenovo Patch if you'd like. You can have a look at the Driver and Software Matrix for IT Admins. You would need to package up the updates and deploy them to the applicable systems. Additionally, you can review Lenovo System Update, Update Retriever, and ThinInstaller. You can use Update Retriever to create a repository of updates and use ThinInstaller or System Update to apply the updates to the device.
TLawson
Edit: Link to SU/UR/TI