Third-party update catalogs for SCCM, kept current.
Patchr Studio helps Windows infrastructure teams publish signed third-party application updates for Microsoft Configuration Manager. Subscribe once in SCCM, then let the catalog flow handle the update metadata and installer content.
Two catalog products for SCCM
Start with a shared Standard Catalog, or add a Private Catalog when you need customer-specific Auto and Uploaded catalog flows.
Standard Catalog
AvailableA shared Patchr-managed catalog of tested updates for common third-party applications, currently Chrome and Firefox.
- Managed by Patchr Studio
- Google Chrome and Mozilla Firefox
- Older versions are expired as new versions publish
- Signed CAB catalog
Private Catalog
AvailableA customer-specific product with two separate SCCM catalogs: Private Auto for tracked source URLs and Private Uploaded for manually supplied installers.
- Private Auto Catalog: recurring updates from source URLs
- Private Uploaded Catalog: manual MSI/EXE installer uploads
- Two SCCM subscription URLs: auto.cab and custom.cab
- Signed private CAB catalogs
Built for endpoint teams
Everything you need to keep third-party apps patched through SCCM without inventing another patching pipeline.
Signed CAB catalogs
Every catalog is signed so Configuration Manager can verify authenticity before importing update metadata.
Native SCCM workflow
Add a catalog subscription URL under Third-Party Software Updates. No extra client agent is required.
Tested update metadata
Updates are built with applicability rules, installer metadata and content references SCCM can consume.
Automated publishing
Standard and Private Auto catalogs can publish new versions when upstream sources change.
Customer-specific private URLs
Private Catalog customers get their own Auto and Uploaded catalog URLs for SCCM subscriptions.
Operational notifications
Planned notifications cover new updates, certificate renewals, inactive catalogs and failed publish runs.
How it works
- STEP 01Choose catalog
Use the shared Standard Catalog or add a customer-specific Private Catalog.
- STEP 02Add in SCCM
Subscribe to the CAB URL under Third-Party Software Update Catalogs.
- STEP 03Sync
Approve the catalog certificate and sync updates into the Configuration Manager console.
- STEP 04Deploy
Stage, publish and deploy selected updates to your device collections.
Beyond catalogs
Patchr Studio starts with SCCM third-party update catalogs. Over time, the plan is to add Windows server patch orchestration for maintenance windows, groups, scripts and reboot coordination.
This is roadmap work, not sold today. Current product work remains focused on reliable Standard and Private Catalog publishing.
- Server groups and rings
- Maintenance windows
- Pre-checks and post-checks
- Reboot coordination
- Patch compliance reporting
- SCCM integration
Planned direction. Scope, timing and availability may change.
Ready to patch third-party apps from SCCM?
Compare Standard Catalog and Private Catalog, then choose the model that fits your environment.