VSMUG 2020-10 | Best Practices for Dell, HP, and Lenovo Drivers in SCCM and v3 Catalog Features 

Great video some good info. I undertstand you can "separate" particular models (Dell for example) into Categories, but how can you deploy the drivers for specific models out from a SUG to the particular models? How does configmgr know which drivers "belong" to the specific model types?

Just a couple of notes: 1) Correction regarding the statement that Dell requires an agent, but Lenovo does not. This is actually not accurate. In the Lenovo catalog there will be an item called the Lenovo Update Catalog Agent (also called LUC Agent). This is required for Lenovo systems to properly detect whether the Lenovo drivers/updates are installed. We had an issue with version 1005 of the LUC Agent where upgrading the OS from an older version of Windows 10 to 1909 broke the LUC agent, but still showed as LUC agent installed. So all Lenovo updates were failing to detect and would re-install themselves every deployment evaluation (often causing a reboot). That bug was supposedly fixed in LUC agent 1006 (current version in the catalog); though I haven't performed a Windows 10 upgrade on a Lenovo to verify yet. 2) There is a bug in ConfigMgr 1910 which, after selecting specific models via the v3 partner catalog (Dell client, HP client, Lenovo client), ConfigMgr resets to default (all models) once per week. There is a hotfix available for download from Microsoft. I don't know if it shows up in the console. This one bit us too... After I'd cleared out 17,000 updates from WSUS for Dell and Lenovo, synced just the models we needed then a week later ended up with 17,000 updates again. After upgrading to 2006 we haven't had that problem.: support.microsoft.com/en-us/help/4552430/third-party-update-category-synchronization-resets-to-default-in-confi

If you select too many products in the Wizard, and you go back and remove those you don't need, does it remove them from the catalog? EDIT: Nevermind - perhaps I should read even one comment before I realize the whole comment section is on this subject.

Thank you for this great video, it helped me alot! But for some reasons the category selection does not have any effect for me: I only selected one model, but the console shows me over 6000 Dell Updates now. It seems, that the category selection is not working.

really hope this fixes the issue I have with adding the HP catalog corrupting the DB

We have recently upgraded our CM to 2006. I hope this would help me to cleanup and publish the third-party updates.

I wish I saw this a month ago. I already added way too many Dell categories. I went to run the script you created but it gives me a bunch of errors about the & not being allowed. "The ampersand (&) character is not allowed. The & operator is reserved for future use; wrap an ampersand in double quotation marks ("&") to pass it as part of a string."

Hello Justin, Andrew and all, we recently moved WSUS to another server and while there was no issue for the MS updates, the existing flock of 3rd party updates have their Source Path pointing to the old server. I opened a case with Microsoft and if I understand correctly they want me to remove 3rd party updates and go then setup again. Have you seen this? Is there not a SQL Query I could run to change the server name (I moved the content folders when I moved the WSUS server - followed your other video).

Is the cleanup categories script available for download? I've been searching a way to get those updates cleaned along with their metadata but cannot find it anywhere...

I am the first one to see this....