SCCM SCUP 2017 How to Publish 3rd Party App Patches ConfigMgr | Configuration Manager Endpoint Manager

SCCM SCUP 2017 How to Publish 3rd Party App Patches ConfigMgr | Configuration Manager Endpoint Manager? I have published a post about the installation and configuration of the 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

The SCUP installation process is straightforward. We have different workspaces in the SCUP console, similar to SCCM. In this post, we will see using SCCM SCUP 2017 How to Publish 3rd Party App Patches.

Patch My PC

The first step is to import 3rd Party Application Catalog to SCUP 2017. Following are out-of-box Partner Software Update Catalogs 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 to 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 ConfigMgr | Configuration Manager Endpoint Manager
SCCM SCUP 2017 How to Publish 3rd Party App Patches ConfigMgr | Configuration Manager Endpoint Manager

SCUP 2017 Publish 3rd Party Apps Updates to SCCM 

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

Select the Automatic option while deploying the 3rd party app updates to SCCM. The 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. Only the software update definition(metadata) is published if neither threshold is met.

SCCM SCUP 2017 How to Publish 3rd Party App Patches ConfigMgr | Configuration Manager Endpoint Manager
SCCM SCUP 2017 How to Publish 3rd Party App Patches ConfigMgr | Configuration Manager Endpoint Manager

We also need to 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 the SCCM console.

From the SCUP console, we have published one new update. So the 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 ConfigMgr | Configuration Manager Endpoint Manager
SCCM SCUP 2017 How to Publish 3rd Party App Patches ConfigMgr | Configuration Manager Endpoint Manager

References

SCCM + SCUP Wiki – https://blogs.technet.microsoft.com/jasonlewis/

System Center Updates Publisher June 2017 Preview is now available https://blogs.technet.microsoft.com/enterprisemobility/2017/07/03/system-center-updates-publisher-june-2017-preview-is-now-available/

System Center Updates Publisher https://docs.microsoft.com/en-us/sccm/sum/tools/updates-publisher/ 

Author

Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc……………

4 thoughts on “SCCM SCUP 2017 How to Publish 3rd Party App Patches ConfigMgr | Configuration Manager Endpoint Manager”

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

    #3MS Consulting, LLC

    Reply
  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?

    Reply

Leave a Comment

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