System Center Updates Publisher adds support for new OSes
First published on CLOUDBLOGS on Mar 21, 2018
Hello everyone, we are happy to let you know that an updated version of System Center Updates Publisher (SCUP) is now available and can be
. SCUP enables independent software vendors or line-of-business application developers to manage custom updates. Using SCUP, you can:
Import updates from external catalogs (non-Microsoft update catalogs).
Modify update definitions including applicability, and deployment metadata.
Export updates to external catalogs.
Publish updates to an update server.
This release of SCUP adds support for Windows 10 and Windows Server 2016. For detailed information about supported operating systems and prerequisites, see the
Install Updates Publisher
topic. While the core functionality in this release remains the same as SCUP 2011, the update catalog format has been enhanced to provide a better experience for users when consuming large update catalogs. Improvements include:
Indexing for quicker imports of previously imported catalogs
- Catalog producers can now index their catalogs. This will allow users to more quickly import large catalogs containing few new updates.
Inclusion of signing certificates within updates catalogs
– Catalog producers can now include signing certificates with their updates catalogs. This enables users to add the certificates to the trusted publishers list during import so that approval prompts will not block publish operations.
Note: While the prior catalog format is still supported, catalog producers will need to add information to their existing catalogs to take advantage of these improvements.
- Updates published to a WSUS server will by default have the signature time-stamped. Note, this functionality requires internet access. If you have upgraded from preview 1 this will not be automatically enabled. To enable or disable this functionality or configure the timestamp server that is used, see the
We also made several accessibility improvements in this release.