Microsoft SCCM Integration
Microsoft SCCM (System Center Configuration Manager) integrates with Big Picture to deploy software when tenant policy is set to MANAGED_BY_IT mode. This integration enables IT teams to control deployment timing and methods while maintaining vendor-controlled release governance.
Overview
Section titled “Overview”SCCM integration provides artifacts and metadata for SCCM deployment. Big Picture continues to govern releases and update policies, while SCCM handles deployment scheduling and execution using standard SCCM deployment methods.
Prerequisites
Section titled “Prerequisites”- Tenant policy — Tenant policy set to
MANAGED_BY_ITmode - SCCM configuration — SCCM infrastructure configured for software deployment
- API access — Service account with
license:readandmirrors:readscopes - Network access — SCCM can access Big Picture API and artifact URLs
Integration Flow
Section titled “Integration Flow”- Tenant policy — Vendor sets tenant policy to MANAGED_BY_IT
- Release publishing — Vendor publishes releases through Big Picture
- Metadata query — SCCM queries Big Picture for available releases
- Application packaging — SCCM packages artifacts as applications
- Deployment — SCCM deploys applications using standard deployment methods
Use Cases
Section titled “Use Cases”Enterprise IT-Managed Deployment
Section titled “Enterprise IT-Managed Deployment”Enterprise customers require IT-controlled deployment for security and compliance. SCCM integration enables IT teams to deploy vendor software through familiar tools.
Regulated Environments
Section titled “Regulated Environments”Regulated environments require strict deployment controls. SCCM integration enables IT to manage deployments while maintaining vendor-controlled release governance.
Existing SCCM Infrastructure
Section titled “Existing SCCM Infrastructure”Organizations with existing SCCM infrastructure can integrate Big Picture without changing deployment workflows.
Integration Points
Section titled “Integration Points”- Update decisions API — Query available releases and artifacts
- Artifact metadata — Retrieve artifact URLs, checksums, and platform information
- Application packaging — Package artifacts for SCCM deployment
- Mirror support — Support for self-hosted artifact mirrors
Configuration
Section titled “Configuration”Tenant Policy
Section titled “Tenant Policy”Configure tenant policy to enable MANAGED_BY_IT mode:
curl -X PUT "${BP_BASE_URL}/v1/tenants/${TENANT_ID}/policy" \ -H "Authorization: Bearer $BP_API_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "update_action": "MANAGED_BY_IT" }'SCCM Application Packaging
Section titled “SCCM Application Packaging”Package Big Picture artifacts as SCCM applications:
- Download artifact from Big Picture
- Create SCCM application package
- Configure installation and uninstallation commands
- Distribute to SCCM distribution points
Next Steps
Section titled “Next Steps”Detailed step-by-step guides for SCCM integration are planned. These guides will include:
- Complete SCCM application packaging procedures
- Automated metadata query and packaging workflows
- Mirror configuration for regulated environments
- Deployment testing and validation
For now, see the Endpoint Management Tools overview for general integration patterns.
Related Documentation
Section titled “Related Documentation”- Endpoint Management Tools — General endpoint management integration
- Comparisons: Big Picture vs SCCM — SCCM comparison
- Workflows: Managing Update Policies — Update policy configuration