Solution: open a ticket with Microsoft for the private hot fix to correct the “License Expired” problem with Orchestrator.
Keep reading for more the details about my experience with the issue.
We ran into a strange problem with the Orchestrator Runbook Service (ORUNBOOK) in production. Each night the service would halt and wouldn’t restart unless we authenticated with an elevated-permissions account. This turned out to be an SPN issue (working with Microsoft now on SPN best practices for System Center and will publish that soon).
Once the SPN issue was corrected, the process would stall. The service was running and the event log only showed authentication problems. The Event log of the Orchestration Console displayed the “Orchestrator Runbook Service on a Runbook Server has stopped running.”
My administrator noted that he was receiving a “Licensed Expired” alert when he used the Runbook Designer on our production server. The link below details the problem and how to fix it.
We installed the hot fix and we’re good to go.