System Center 1801: Orchestrator Integration with Operations manager
Applies to
This guide applies to System Center Operations Manager 1801
Requirements
- System Center Orchestrator 1801.
- System Center Operations Manager 1801.
- Integration Pack for System Center 2016 Operations Manager (download here).
- .NET Framework 3.5.
Integrating SCORCH with SCOM
Let’s start by opening the **Runbook Designer **
Navigate to the Options menu in the upper right corner, then click SC 2016 Operations Manager.
A Microsoft System Center Operations Manager Connections window will open.
Since we have no connections from earlier, we will add a new one by clicking Add.
A new Connection window will open up.
Fill in a name for our connection, the SCOM server information and credentials that have access to our SCOM server.
Once we have filled in everything we can test the connection by clicking Test Connection.
If we get an error or a crash it means that we don’t have the .NET Framework 3.5 feature installed.
This requires us to have the .NET Framework 3.5 feature installed, see the bottom of this post on how to install it.
If our test connection was successful, click OK to close it.
We have now successfully created a connection between Orchestrator and Operations Manager, click Finish.
Now we are ready to start using our Integration Pack for System Center 2016 Operations Manager, enjoy!
Installing .NET Framework 3.5
Open up the Server Manager and head to the upper left corner, click Manageand then click Add Roles and Features.
A new Add Roles and Features wizard will open up, click Next to continue.
Next choose the installation type, in this case it’s a role-based or feature-based installation so leave the default value and click Next to continue.
Next choose the server we want to install the feature on, by default it’s our localhost, click Next to continue.
In the following window we will get a list of all the roles available, since we want to install a feature which is on the next step just click Next to continue.
In the features list, check the .NET Framework 3.5 Features box and then click Next to continue.
This feature requires additional installation content, which can be found from a Windows Server image, mount up a Windows image to our server and then choose Specify an alternate source path.
In the Path field select the drive that have our Windows image mounted and then add Sources\SxS\ behind it, for example like this: **Z:\Sources\SxS\**and then click OK.
We are now ready to install the .NET Framework 3.5 features, click Install to start the installation.
Once the installation is complete click Close to finish the Roles and Features wizard.
