Today it’s more important than ever to stay current, meaning that you ensure that you’re running the latest versions of the applications you deploy in your organization. Why use ConfigMgr and third-party software updates catalogs This feature was first released in the ConfigMgr Technical Preview version 1806, however this blog post covers the Current Branch release of ConfigMgr. In this blog post we’ll go through the requirements for configuring this new feature including all the required steps necessary to get you up and running.

This means that you don’t have to use for instance System Center Update Publisher (SCUP) to handle the publishing of meta data into ConfigMgr.

Starting with ConfigMgr Current Branch 1806, you can now enable and deploy Third-party Software Updates from a partner catalog from within ConfigMgr using the existing software update management process. By enabling this feature, it reduces the infrastructure foot print for managing Third-party Software Updates by incorporating it directly into the product.

Patchmypc catalog