03-14-2019 04:30 PM - edited 03-14-2019 05:01 PM
Someone from Lenovo correct me if I'm wrong, but my guess is they are facing *difficulties* less because of not having enough room in the XML schema to fit models in the title, or because of "the way updates execute" (How different can an .msi or .exe be when it's just updating software/drivers? and this is a SELF IMPOSED limitation if it's that different, because it doesn't NEED to be that way)
The difficulty is almost guarenteed to be more because they have their own product they want you to buy called "Lenovo Patch" that integrates with SCCM for the same purpose.
I mean you expect me to believe that Lenovo can create a software that does all this, and have it integrated into SCCM, but they can't figure out XML schema?
No... They would rather sell that product, than offer companies software and security updates for free...
Who cares if those same companies keep Lenovo in business by purchasing hundreds of thousands/millions of dollars worth of equpment from Lenovo...
Dell and HP have went ahead and established that they care about their customers security and time by prioritizing the SCCM catalog... and they did that quickly...
So Lenovo... is it that your engineers are "challenged" by XML?
(if so that REALLY Speaks to the quality of your engineers if HP/Dell, and the much smaller PatchMyPC can beat you to it this badly)
Or is it a money thing?
Apologies if I'm coming off a bit bitter... but when it comes to patching/managing Lenovo systems... Lenovo seems to only want you to use proprietary solutions... and then they don't seem to put much into the free solutions... oh but if you pay for their extra product? it works great...
03-14-2019 08:47 PM
We released an updated catalog a day or so ago. We are constantly updating the catalog with new content.
As @parkerjnc mentioned, there are some limitations we have to adhere to, but the amount of content in the catalog will be growing over time to include more models and more content for existing models.
03-15-2019 06:15 AM
The link is still the same - https://download.lenovo.com/luc/v2/LenovoUpdatesCatalog2v2.cab
03-15-2019 07:00 AM
03-18-2019 12:10 AM - edited 03-18-2019 07:47 AM
I have just imported the updated catalog. Here are my observations
A few suggestions
03-27-2019 08:57 AM
Everyone: The catalog was updated again. Not a very large number of updates, but some important BIOS upgrades. So I will start removing my custom SCUP updates and replace them with official Lenovo SCUP updates.
Good work Lenovo! Thanks
03-27-2019 03:50 PM
Is there a formal doc for settings this up with in SCCM? Following the Microsoft doc works fine (done this with PMP and Ivanti in the past), and I get Meta Data for only 16 updates, and all but 1 are older than December 2018 and only 3 are evaluating as Required (none are actual drivers). Looking at wsyncmgr.log shows the Updates in the bottom table being Successfully Synced (not skipped), so it's puling new data from the .cab.
I'm not sure where I'm going wrong. I have this catalog Subscribed to 2 separate ConfigMgr Sites (1810 on Server 2012r2 and 1810+KB4488598 on Server 2016) and both are publishing the same metadata.
Catalog data from console:
|Publisher||Name||Last Sync Status||Dscription||Download URL||Last Sync Time||Subscribed|
|Lenovo||Lenovo Updates Catalog||Success||Lenovo Updates Catalog||https://download.lenovo.com/luc/v2/LenovoUpdatesCatalog2v2.cab||3/27/2019 22:06||Yes|
|Title||ArticleID||Date Released or Revised||Required||Installed||Percent Complete|
|Lenovo Updates Catalog Agent 1005||lucagent1005||3/11/2019 19:58||0||0||0|
|Lenovo Power Management Driver - 7/8/8.1/10  - 1.67.14.07||n20ku13w_x64||12/16/2018 18:00||0||0||0|
|Lenovo Power Management Driver - 7/8/8.1/10  - 1.67.14.07||n20ku13w_x32||12/15/2018 18:00||0||0||0|
|Flash BIOS Update for Lenovo M625q - 7/10  - 1.28||m1wjy28usa||11/13/2018 18:00||0||0||0|
|Lenovo Fingerprint Manager - 7 [32,64] - 4.5.336||n1xgc01w||10/11/2018 19:00||0||0||0|
|Lenovo application interface - 10  - 18.104.22.168||k1acp07us17||5/24/2018 19:00||0||0||0|
|Lenovo Touch Fingerprint Software - 7  - 1.00.19||n1mgc05w_64||5/21/2018 19:00||0||0||0|
|Lenovo Touch Fingerprint Software - 7  - 1.00.19||n1mgc05w_32||4/24/2018 19:00||0||0||0|
|Lenovo Dynamic Power Reduction Driver - 10  - 22.214.171.124||n1zpc04w||3/5/2018 18:00||0||0||0|
|Lenovo Fingerprint Manager Pro - 7/8/8.1  - 8.01.87||lz4goca2_64||12/24/2017 18:00||25||2||95|
|Lenovo Fingerprint Manager Pro - 7/8/8.1  - 8.01.87||lz4goca2_32||12/24/2017 18:00||0||0||0|
|Lenovo Communications Utility - 7 [32,64] - 126.96.36.199||grcu24ww||9/13/2017 19:00||0||10||96|
|Sierra Wireless Lenovo Mobile Broadband Driver Package (EM7455)- 7 [32,64]/8.1  - 7.40.4684.0105||n1vwo04w||6/11/2017 19:00||0||0||0|
|Lenovo Scaling Utility - 7/10 [32,64]/8.1  - 3.22||n14us42w||4/24/2017 19:00||102||44||93|
|Lenovo Fingerprint Manager Pro - 7  - 4.5.336.0||n1xgd01w_764||4/11/2017 19:00||0||0||0|
|Lenovo Dynamic Power Reduction Utility - 7/8/8.1/10 [32,64] - 188.8.131.52||n1mg709w||3/2/2017 18:00||0||0||0|
03-29-2019 12:12 AM
If we try to publish an update we get the error
in the SMS_ISVUPDATES_SYNCAGENT.log