SCUP 2017 Preview Installation and Configuration Video Guide | System Center Updates Publisher | SCCM

SCUP 2017 Preview Installation and Configuration Video Guide | System Center Updates Publisher | SCCM? Microsoft recently released the preview version of System Center Updates Publisher (SCUP)2017. This SCUP preview version adds support for Windows 10 and Windows Server 2016.

SCUP is a stand-alone tool that enables 3rd party applications (non-Microsoft apps) or LOB application developers to manage custom updates.

The SCUP can be integrated with WSUS and SCCM. This post will go through SCUP 2017 preview installation and configuration Video Guide.

More details about How to Publish 3rd Party Abode Acrobat Patches via SCCM SCUP 2017 here

Patch My PC

Install SCUP 2017 on Server 2016

The SCUP installation process is straightforward, as you can see in the video embedded in this post. We have different workspaces in the SCUP console, similar to SCCM.

Those SCUP workspaces are Updates Workspace, Publications Workspace, Rules Workspace, and Catalogs Workspace. You can navigate to “Update Workspace – Overview” and add updated catalogs from partners like Adobe.

SCUP 2017 Preview Installation and Configuration Video Guide | System Center Updates Publisher | SCCM
SCUP 2017 Preview Installation and Configuration Video Guide | System Center Updates Publisher | SCCM

Import 3rd Party Application Catalog to SCUP 2017

Add partner software updates catalogs gives us an option to download/Import 3rd party app catalogs like Adobe Acrobat 11 Updates. This initiates the Acrobat11_Catalog.cab file download. As part of the process, we also need to accept the security validation of the catalog from a vendor like Adobe System. 

Several updates are available in a single catalog or cab file like Acrobat11_Catalog.cab.  There are 20 updates available for Adobe Acrobat 11 update catalog, similar to Acrobat 11.0.18 Update, and Acrobat 11.0.20 Update. And all these updates are imported to SCUP.

Adaptiva

There are options to edit/customize 3rd party application updates, which are imported into SCUP. The package information tab has all the details about the location from where the download of the actual source file like AcrobatUpd11001.msp will happen.

We can also specify the installation command line etc… for each update. There are several options to customize each update. Following are the main customization options of each update. The package, Information, Optional Info, Prerequisite, Supersedence, Applicability, Installed, etc…

SCUP 2017 Preview Installation and Configuration Video Guide | System Center Updates Publisher | SCCM

SCUP 2017 integration with SCCM and WSUS

SCUP can be integrated with WSUS and SCCM. One of the prerequisites for this integration is connectivity between SCUP and WSUS (+ SCCM). This connectivity must publish 3rd party patch updates to WSUS and then to SCCM.

There is a check box option in the SCUP console to enable publishing updates capability to an update server (WSUS server). And you need to create a Self Signed certificate for WSUS connectivity, as you explained in the above video. A similar option is there to enable configuration manager (SCCM) integration with SCUP 2017.

SCUP 2017 Preview Installation and Configuration Video Guide | System Center Updates Publisher | SCCM
SCUP 2017 Preview Installation and Configuration Video Guide | System Center Updates Publisher | SCCM

The configuration options and workspaces are not changed in the SCUP 2017 preview version (when you compare it with previous versions of SCUP). I recommend installing WSUS and then installing the SUP component from the SCCM console before connecting the SCUP with WSUS. 

As you see in the above screen capture, the test connection succeeded. However, no signing certificate was detected for the update server. You will not be able to publish content to the update server without first registering a signing certificate.

SCUP 2017 Certificate Export and Import Activities

We need to export the certificate of WSUS from MMC and import it to the locations mentioned below. We must add the signing certificate used for publishing to the following certificate stores on the computers that run SCUP and WSUS: Trusted Publishers and Trusted Root Certificate Authorities.

The settings for this connection are not saved until we click OK on the Options dialog box.

The WSUS and SCCM connection tests were successful after importing the certificates to MMC. Now we are ready to publish the updates to WSUS. Publish the updates to WSUS and SCCM via SCUP.

SCUP 2017 Preview Installation and Configuration_Cert requirements
SCUP 2017 Preview Installation and Configuration Video Guide | System Center Updates Publisher | SCCM

Reference

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……………

6 thoughts on “SCUP 2017 Preview Installation and Configuration Video Guide | System Center Updates Publisher | SCCM”

  1. Hi – Good video. Will be deploying SCUP 2017 within the lab this weekend.

    Do, I need to deploy a package with WSUS cert to all system within the network for SCUP 2017 to work properly?

    In the past with SCUP 2011, I did deploy a package titled SCUP cert – for copying the WSUS cert to all workstations at their respective locations (Trusted Publishers and Trusted Root Certificate Authorities).

    Reply
  2. hello, i followed step by step but when i publish an app to a client machine it does not appear.
    I get it to publish and download in sccm.
    Any logs where i can see an error of why the deployment from sccm to client won’t work?

    Reply
  3. Anoop
    I am only able to see Dell Drivers and Applications in the SCCM Software Update Properties Products Tab.
    Is there something I am missing? Is SCUP 2017 required?

    Reply

Leave a Comment

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