Update & Upgrade Problems

Deploy Adobe Acrobat and Reader Security Updates with SCCM

Camila MilosovichCamila Milosovich Nov 19, 2026 868 views

Question details

An organization needs to distribute Adobe Acrobat and Reader security updates to managed devices using SCCM.

Deploy Adobe Acrobat and Reader Security Updates with SCCM
Product
Adobe Acrobat, Adobe Acrobat Reader, and Microsoft SCCM
Device & OS
not provided
Scenario
An administrator wants to publish Adobe security updates from Adobe's SCUP catalog and deploy them through SCCM.
Observed behavior
Adobe security updates are available for synchronization and deployment to the applicable managed devices.
Before you start

Confirm that your SCCM software update point and WSUS are configured, and that you have permissions to publish and deploy updates. Check Adobe's current deployment documentation for catalog availability and requirements before using SCUP.

Solution 1Recommended

Publish Adobe updates with SCUP and deploy them through SCCM

Use Adobe's SCUP catalog to make applicable Acrobat and Reader security updates available for SCCM deployment.

This workflow requires a working SCUP and WSUS publishing configuration, including a trusted code-signing certificate on managed clients. Catalog and product support may change, so verify the current requirements in Adobe's deployment documentation.

1
Check Adobe's catalog instructions

Open https://www.adobe.com/devnet-docs/acrobatetk/tools/DesktopDeployment/sccm.html and check the current catalog location, supported products, and publishing instructions.

2
Import the Adobe catalog

In System Center Updates Publisher, open Catalogs and add the Acrobat and Reader catalog using the location provided by Adobe. Import the catalog and review the available updates.

3
Configure publishing and trust

In SCUP, configure the update server and publishing certificate. Ensure managed clients trust the certificate and allow signed updates from an intranet Microsoft update service through the applicable client policy.

4
Publish the required updates

In SCUP, select the applicable Acrobat and Reader security updates and choose Publish. Publish the full update content when it is needed for deployment.

5
Synchronize and deploy in SCCM

In the SCCM console, go to Software Library > Software Updates and synchronize software updates. Find the published Adobe updates under All Software Updates, then download and deploy them to the appropriate device collection.

6
Monitor the deployment

Open Monitoring > Deployments in the SCCM console to review compliance and errors. Confirm that the updates are applicable and installing on the targeted devices.

Publish Adobe updates with SCUP and deploy them through SCCM
Verify current support: SCUP and catalog availability depend on the versions and services in use. If the documented catalog or publishing method is unavailable, consult Adobe's current enterprise deployment guidance before proceeding.
Free Microsoft Office alternative

Use WPS Office for PDF and Office Documents

WPS Office is a free, lightweight alternative with a familiar interface for working with PDFs and Office documents. Its format compatibility helps teams migrate documents seamlessly, but it does not publish or deploy Adobe security updates through SCCM.

Open and work with PDF files in WPS Office.Compatible with Microsoft Office formats including DOCX, XLSX, and PPTX.Use a familiar interface for everyday document tasks.Move existing Office documents into a lightweight, free office suite.
microsoft office alternative - wps office

Frequently Asked Questions

Where can I find Adobe's SCCM deployment guidance?

See Adobe's enterprise deployment documentation at https://www.adobe.com/devnet-docs/acrobatetk/tools/DesktopDeployment/sccm.html for catalog and update-publishing guidance.

Why aren't published Adobe updates visible in SCCM?

Check that SCUP published the updates to the correct WSUS server, then synchronize updates from Software Library > Software Updates in the SCCM console. Also check the software update point configuration and synchronization status.

Do managed devices need to trust a publishing certificate?

Yes. For locally published signed updates, managed clients must trust the appropriate publishing certificate and have the policy enabled to allow signed updates from an intranet Microsoft update service.

Where can I check whether the deployment succeeded?

In the SCCM console, open Monitoring > Deployments and select the update deployment to review compliance and error details for the targeted collection.