The Dell System Center Updates Publisher (SCUP) Catalogs automate the patch process of system updates for Dell servers and workstations in a Microsoft ConfigMgr or Microsoft System Center Essentials (SCE) environment. The catalog files contain detailed information to determine which updates are required for Dell servers and workstations, and how to apply them. It can be used in conjunction with the software update management functionality of Microsoft ConfigMgr (and update deployment process in SCE) to provide automated BIOS, firmware, driver, and Dell application updates.
README docs have been updated to reflect changes in Partner Developer Kit (PDK) catalog and also SCUP catalog. Please find the links related to README's in Quicklinks section.
NOTE: The Business Client Updates Catalog for SCUP is now called the Dell Command | Update Catalog and is a part of the Dell Client Command Suite. A new page has been created HERE
OpenManage Inventory Agent for Windows Workstations
Client Updates SCCM Catalog Download
Dive into the following pages to get SCUP and Dell Updates up and running:
Whitepaper - Deploying Dell Updates with ConfigMgr 2012 using the Dell Business Client Updates Catalog
Dell Installation Guide for Custom Updates (.pdf, 6 MB) Dell System Center Website SCUP 4.0 Installation FilesSCUP Online DocumentationTechnet Software Updates ForumThird-party Custom Catalogs for Configuration Manager 2007 and System Center Essentials 2007 SCUP wiki page on http://www.myitforum.com.Dell Video - Dell Updates Catalog and ConfigMgr (9 MB, 8 min, 30 sec)
It appears you're now placing the Client catalog at ftp.dell.com/.../DellSDPCatalogPC.cab
Is this intended or is the FTP server folder structure messed up?
getting the following with the latest catalogue. does the file exist for anyone else?
ISA Server: extended error message :
200 Type set to I.
200 PORT command successful.
550 The system cannot find the file specified.
Why does the SCUP Catalogue have old bios updates?
Optiplex 755 SCUP is A12 but the latest Bios is A20
Optiplex 760 SCUP is A12 but the latest Bios is A13
most of the optiplex units are behind what the latest bios is.
It seems that DellSDPCatalog.cab & DellSDPCatalogPC.cab contains latest updates only.
Do you maintain archive of these cab file specific to older release (older version of updates)?
Conflicts between Client & Server Update Catalog. Need resolved please.
Seagate 15k drive firmware
Update ID: f426f85b-021c-411d-bcc6-2bc72a753653
Dell PowerVault RE1000 Firmware
Update ID: bbaaa91e-7dcb-4d2e-a259-3de0fcf1e4a8
Hitachi HD Firmware
Update ID: 5dbd4ffc-7fdb-42e9-8d35-fc4b8ced91d3
Seagate SATA Firmware
Update ID: be00ec85-c3d8-4bfe-aad6-6fd133fee74e
Fujitsu SAS Drive Firmware
Update ID: ead5b672-f784-43f9-a7c9-36db7a1d5aa7
In all cases the Client Update Catalog is newer than the server update catalog. If the Clients and Servers need different Firmware versions each update should have a unique ID and different filters.
It might be to much to ask for but it would be nice to have catalogs for "Legacy" systems that have the latest updates for those legacy systems. Some organizations might still need to pull in those updates and publish them but they are not included in the current Dell Update Catalog.
Having a "Generation 9" and "Generation 8" catalog that could be imported would be great.
My Customer use SCCM 17.02 and SCUP 2011 on win10.
Client is Optiplex 5050
Problem1 – 2 x drivers do not install via SCCM :
The following two drivers are published in the Dell catalog but they do not install via SCCM. These two drivers do not appear in the SCCM soft center as if SCCM decided that they were not applicable on this Optiplex.
Other drivers Ok
When customer install these two drivers directly it is Ok.
Driver 1 >> Intel Management Engine Components Installer (4J8MX)
Driver2 >> Realtek High Definition Audio Driver (P71YY)
Problem2 : driver not available in SCUP.
The driver Intel HD Graphics 510 / 530 / 630 (CMGP0) is not available in SCUP when the previous one is available.
Do we have an explanation ?
Thanks in advance for your cooperation.
Part of the latest update bundle fails to publish update 2DDG2.