SCCM SCUP 2017 How to Publish 3rd Party App Patches

I have published a post about installation and configuration of SCUP 2017 preview version. You can have a look at that post before going through this post. More details SCUP 2017 Preview Installation and Configuration Video Guide. SCUP installation process is straight forward. We have different workspaces in SCUP console similar to SCCM. In this post we will see using SCCM SCUP 2017 How to Publish 3rd Party App Patches.

The first step is to import 3rd Party Application Catalog to SCUP 2017. Following are out of box Partner Software Update Catalog available with SCUP 2017 preview version. Adobe Acrobat X, Adobe Acrobat 11, Adobe Reader X, Dell Business Client, Dell Server, Fujitsu PRIMERGY, HP Client and HPE ProLiant. This is also explained in the video here.

SCCM CB Settings before publishing SCUP 2017 App Updates

We need to add 3rd party applications into SCCM SUP products like Abode, Dell, Fujitsu and HP. Navigate through SCCM Settings – Configure Site Components – Software Update Point – Products – Adobe Systems. Inc. – Abode Acrobat.

SCCM SCUP 2017 How to Publish 3rd Party App Patches

SCUP 2017 Publish 3rd Party Apps Updates to SCCM 

Now we are ready to publish the 3rd part app updates to SCCM. Right click on all the updates from SCUP and publish to SCCM CB.

Select Automatic option while deploying the 3rd party app updates to SCCM. Automatic  option is available only when SCCM integration is selected in SCUP. Click Automatic to allow updates publisher to query SCCM to determine whether the selected software updates are published with full content or only metadata.

In this mode, software updates are only published when they meet the client request count and package source size thresholds are specified on SCCM. If neither threshold is met, only software update definition(metadata) is published.

SCCM SCUP 2017 How to Publish 3rd Party App Patches

We also need Sign all software updates with a new publishing certificate when published software updates have not changed but their certificate has changed.

SCCM Software Update Sync after Publishing 3rd Party Apps 

SCCM All Software Update Sync to have the newly added Acrobat 11 and other app product updates in SCCM console.

From SCUP console, we have published one new update. So total 3rd party update count is 5. SCCM should have 5 Acrobat updates after the SYNC.

SCCM SCUP 2017 How to Publish 3rd Party App Patches

References :-

SCCM + SCUP Wiki –

System Center Updates Publisher June 2017 Preview is now available

System Center Updates Publisher 

Sharing is caring!

4 thoughts on “SCCM SCUP 2017 How to Publish 3rd Party App Patches”

  1. From an Enterprise level, is SCUP reliable and stable? What are some of the challenges when implemented?

    #3MS Consulting, LLC

  2. Hi, Anoop, Thanks for your reply, is it good using the SCUP to upgrade the BIOS over the Task sequence based approach from SCCM?


Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.