Problem with installing Orchestrator and SCOM on the same server

I came across many environments installed the system center Orchestrator server on the SCOM server, since their main use of the Orchestrator server messaging is for the SCOM server, by using System Center integration Pack for OM called with activity 'Monitor Alert'  and install it on him anyway,

Indeed ongoing work properly and delivered messages, but when doing Restart to the server, the Runbooks work with the SCOM and use its Activities are aborted, and you must to run them manually.

The explanation for this is, because during the startup of the server , the service of the Orchestrator 'Orchestrator Runbook Service' rising along with the services of the SCOM, and boot the Runbooks performed before carried out Connectoin to DB of the SCOM then the Monitor Alert Activity for example, is trying to communicate to the SCOM and get the answer Aborted,

You can see this by making Stopping to Services - Data Access and Runbook Service and make a start only for the Runbook Service when approached to Runbook Designer view of processes related to SCOM arrested,
In fact the simplest solution that can be done by setting Dependencies on the Runbook Service in SCOM Services. And thus will initially Start of Data Access,
In practice since Operation Start to Data Access and immediately afterwards start to Runbook Service without waiting to perform the actual Connection, still received Aborted after restart.

Therefore need to make a distinction between the Orchestrator and the SCOM server for each application.
A temporary solution that can be done is:
Manage Startup Services server by script, and because when the service is in Automatic mode is immediately rises during the Boot, define a script to move it during the Shutdown to Manual mode, and in startup setting the order of the start of the Services includes waiting twenty seconds of booting the Services of SCOM in the boot of the orchestartor Services to have enough time to create a Connection to DB, and back the Services to Automatic mode.

this can be done by using group policy in computer settings running Script in Startup and Shutdown:

# for Shutdown Script create batch file with Commands to change the services mode to manual in Shutdown process:

sc config "OMSDK" start=Demand

sc config "cshost" start=Demand

sc config "Healthservice" start=Demand

sc config "orunbook" start=Demand

# for Startup Script create batch file with the commands for Startup process to order the services starting, and change the Mode to Automatic

sc start OMSDK

sc start cshost

sc start healthservice

timeout 20

sc start orunbook

sc config "OMSDK" start=Demand

sc config "cshost" start=Demand

sc config "Healthservice" start=Demand

sc config "orunbook" start=Demand

then after restart the server, the runbooks continue to running.