SCORCH Runbooks SCCM: Fixing Missing Runbook Visibility

If you’ve created and checked in a new System Center Orchestrator runbook, but it isn’t showing up in the systems meant to consume it (Configuration Manager, MDT, or Service Manager), this is typically an authorisation/permissions cache that hasn’t refreshed to pick up the new runbook.

What to Try

• Restart the Orchestrator Management Service on the Orchestrator management server — this is the most common fix, since it forces a fresh read of runbook permissions rather than relying on the cached state.
• Confirm the runbook (and the folder it lives in) has the correct role-based security permissions assigned in the Runbook Designer — a runbook without explicit permissions assigned to the account/service consuming it won’t appear even after a cache refresh.
• In the consuming system (for example, the SCCM/MDT “Invoke Orchestrator Runbook” task sequence step), refresh or re-browse the runbook list rather than relying on a previously cached list from before the runbook existed.

If you’re tempted to fix this by editing the Orchestrator database directly via SQL, don’t do that without following Microsoft’s own documented support procedure for your exact Orchestrator version — the authorisation cache tables aren’t a supported direct-edit surface, and an incorrect change can corrupt runbook permissions across your whole environment. A service restart resolves this in the large majority of cases without needing to touch the database at all.

Still Current on System Center 2025

This fix remains accurate on the current System Center 2025 release of Orchestrator — the role-based runbook permission model (Windows groups mapped to runbook folder permissions via the Runbook Designer/Deployment Manager) hasn’t changed architecturally, so restarting the Orchestrator Management Service and checking those permissions is still the right first move. Nothing in System Center 2025’s update rollups has altered this specific behaviour; UR1’s changes (SQL Server 2025, .NET 8, TLS 1.3 support) are platform-level, not permissions-model changes.

Resources

• Microsoft
• SQL
• query