Orchestrator Not Showing Folders: Fixing Missing Runbooks

This is a recurring issue we’ve run into more than once: newly created folders and runbooks in System Center Orchestrator not appearing in the places that consume them — including the SCCM/MDT “Execute Runbook” task sequence step, and sometimes the Orchestrator Web Console itself.

What’s Going On

This is typically the same underlying cause as stale runbooks not appearing elsewhere: Orchestrator’s authorisation/permissions cache hasn’t picked up the newly created object yet, so consuming systems querying that cache simply don’t see it.

What to Check

• Restart the Orchestrator Management Service to force a fresh authorisation read.
• Confirm the new folder/runbook has explicit role-based security permissions assigned — newly created objects sometimes don’t inherit permissions the way you’d expect, which can make them effectively invisible to accounts that would otherwise see everything in a parent folder.
• Re-browse rather than relying on a cached list in whatever tool is trying to consume the runbook (task sequence editor, Web Console), since those can cache their own view of available runbooks separately from Orchestrator’s own cache.

If a service restart and permissions check don’t resolve it, it’s worth checking the Orchestrator Management Service’s event log for specific authorisation errors rather than guessing further.

Still Current in 2026 (Updated for 2026)

System Center Orchestrator remains an actively developed, current System Center 2025 component — it hasn’t been deprecated or folded into anything else. It’s individually documented as “System Center 2025 Orchestrator,” with mainstream support running to 8 January 2030 and extended support to 9 January 2035. Update Rollup 1 (December 2025) added SQL Server 2025 support on top of the System Center 2025 baseline (.NET 8, TLS 1.3, encrypted-by-default SQL connections, gMSA support), so this is genuinely a live product receiving feature investment, not just security patches. There’s no current Microsoft guidance found steering existing on-prem Orchestrator customers toward Azure Automation or Power Automate — if you’ve already got runbooks built around Orchestrator, it remains a fully supported platform for them.

Resources

• guide
• query