In the beginning of June I wrote a post about how to enable Third-Party Software Updates in SCCM Technical Preview 1806 without using SCUP. This week another release of SCCM Technical Preview hit the streets. 1806 in a second edition, also called 1806.2.
This release further iterates on support for Third-Party Software Updates, and now enables us to add custom catalogs such as Adobe. In this post I will walk you through how to do just that, and show you how to add the Adobe catalog for Acrobat Reader DC to Configuration Manager and thus allowing us to deploy updates for Adobe natively without using SCUP.
I’m going to assume that third-party updates are configured and working in your end already. If not, you should start with my previous post right here: https://imab.dk/enable-third-party-software-updates-in-configuration-manager-technical-preview-1806/
To get this started, right click on Third-Party Software Update Catalog in the Software Library work space of the Configuration Manager console. See below picture:
- Fill out the details for the custom catalog. In this scenario, I have filled out with following details:
- Download URL: https://armmf.adobe.com/arm-manifests/win/SCUP/ReaderCatalog-2017.cab
- Publisher: Adobe
- Name: Adobe Reader Classic
- Description: Adobe Reader Classic custom catalog
- Finish the wizard ending up with below picture selecting Close
- Next step is to subscribe to the newly added Adobe catalog. Do so by right clicking on it and selecting Subscribe to Catalog
- Complete the subscription process following my below pictures. I have taken snips of each steps and highlighted the required actions. Note: This is exactly the same process as when subscribing to the built-in HP (Hewlett Packard) catalog.
- After finishing off the subscription, select to sync the new update catalog on Sync now
- Monitor following server side log file: <ConfigMgr InstallDir>\Logs\SMS_ISVUPDATES_SYNCAGENT.log. Once the sync has completed, you will see following entries in the log:
- Next, when the syncing in above is done, enable the new product on the properties of your Software Update Point in Configuration Manager
Do another synchronization of Software Updates and monitor <ConfigMgr InstallDir>\Logs\wsyncmgr.log and wait for your Adobe updates to show up in the All Software Updates node
- Tadaaa. Adobe Software Updates right there in your Configuration Manager console for you to deploy without using SCUP or any other third-party product
And that’s a wrap for this specific scenario in System Center Configuration Manager Technical Preview 1806.2.
I hope this helpful and informative 🙂