TLS 1.2 now Supported by SystemCenter 2016

Worth taking note. Particularly anyone struggling to fit SCSM outbound email to Office 365 into your security model.


Orchestrator Web Console and Service Fail to Start after 2016 UR1

Back in 2013 Microsoft discovered a bug in the upgrade process from Microsoft System Center 2012 Orchestrator to Microsoft System Center 2012 R2 Orchestrator.  More information can be found here.

This exact same problem can occur when Update Rollup 1 is applied to Microsoft System Center 2016 Orchestrator.

The web console displays this warning:

Error Executing the current operation
Arguments: NotFound

Running the following two SQL statements against the Orchestrator database will fix it:

WARNING – Run these statements at your own risk.  Take all precautionary measures necessary!

GRANT EXECUTE ON object::[Microsoft.SystemCenter.Orchestrator].[GetSecurityToken] TO [Microsoft.SystemCenter.Orchestrator.Operators]
GRANT SELECT ON object::[Microsoft.SystemCenter.Orchestrator.Internal].[Settings] TO [Microsoft.SystemCenter.Orchestrator.Operators]

Runbooks Missing from the Service Manager Console

Sometimes when you create a Runbook in Orchestrator and then synchronise the Orchestrator connector the Runbook doesn’t appear in the Runbooks view in the Service Manager Console.  This is because the Orchestrator authorisation cache hasn’t updated yet to allow the connector access to the folder / Runbook.

Run the following SQL script against the Orchestrator database to resolve the issue:

TRUNCATE TABLE [Microsoft.SystemCenter.Orchestrator.Internal].AuthorizationCache