SCORCH runbooks not showing in SCCM or SCSM

system center

When you create a new System Center Orchestrator Runbook and you have checked it in ready to use, you may not see it in systems that will want to use it, like Configuration Manager, Microsoft Deployment Toolkit or Service Manager.

This is due to authorisation cache not updating and as so, not showing the newly created runbook.

Guide

To fix this, you will need to open up Microsoft SQL Management Console and run the following SQL query on your Orchestrator database:

Truncate Table [Microsoft.SystemCenter.Orchestrator.Internal].AuthorizationCache
EXEC [Microsoft.SystemCenter.Orchestrator.Maintenance].EnqueueRecurrentTask ‘ClearAuthorizationCache’

Once you have run this, you should then head back to where you want to use the runbook and you should now be able to see it!

Remember if you are using something like Service Manager, you will need to run the connector synchronisation again after running the SQL query on the database.

Comments

If you have any questions or feedback on this post, please feel free to leave us a message below in the comments section.

Free Subscription!Subscribe to our site to receive updates via email!

Enter your email address below and click the Subscribe button to receive email notifications about new and exciting downloads available through our website at https://www.techygeekshome.com

You will also receive notifications about new technical guides, latest news and MSI installer downloads that are available through our blog here at https://blog.techygeekshome.info 

We will not spam you and we will not pass on any of your details to anyone else. We tend to post new content once or twice a week.

Join 232 other subscribers

You can unsubscribe any time you like.

About A.J. Armstrong

Founder of TechyGeeksHome and Head Editor for over eight years! IT expert in multiple areas for over 20 years. Sharing experience and knowledge whenever possible! Making IT Happen.

View all posts by A.J. Armstrong