Install Connection Center

Cookdown Connection Center is made up of two or more components, a SCOM management pack, and one or more target destinations to push alerts into. During the installation process, you will install our SCOM management pack and a corresponding component to the destination you wish to push your alerts to. The requirements for these destinations do vary so each one has its own installation guide.

Pre-Requisites

Before you get stuck in, you should make sure that you have the following items:

  1. SCOM admin credentials (to install our SCOM Management Pack)

  2. A valid Cookdown product license key

Install the Management Packs

There are two management packs to install into SCOM:

  • Cookdown Connection Center

  • Cookdown Licensing (you may already have this from other Cookdown products - but make sure that it is up to date)

Both Management Packs are installed like any other management pack and can be installed following the standard Microsoft import documentation. Many of the Cookdown user interface components are loaded when the console does, so you will need to close and re-open the SCOM console.

Back to top

Licensing Connection Center

Once installed you will need to license Connection Center in SCOM. If you do not have a license code or an offline license file, please contact hello@cookdown.com to get one.

When selecting one of the Connection Center menu items in the SCOM Administration pane, you will be presented with a ‘Cookdown Licensing' action in the 'Tasks’ pane to the right:

Selecting this action will start off the Licensing process.

Licensing online

  1. Paste your license key into the provided 'License Key' text box

  2. Press the 'Apply License' button

  3. You will then be presented with the status of your license or advised to take corrective action

Back to top

Licensing offline

  1. Select the 'No direct internet connection?' link towards the bottom of the licensing window

  2. Paste the contents of your license file into the provided text box (formatting does not matter)

  3. Press the 'Apply License' button

  4. Accept the success message or take corrective action suggested

You will then be presented with the status of your license:

Back to top

Configure SCOM Authentication/Run-As

Connection center uses standard SCOM Run As Accounts and Profiles. Whilst you will have to create a Run-As Account, we provide you with a Run-as Profile for your destination system out of the box.

Create Run-As Account

  1. In the SCOM Console open the Administration pane then expand Run As Configuration

  2. Right-click ‘Accounts' and select 'Create Run As Account…’

  3. Under ‘General Properties', set the type of Run as account to ‘Basic Authentication'. Give it an appropriate display name and description

  4. Under credentials enter the credentials required to connect to your destination system

  5. Select the distribution security model you would like to use. We have written this guide assuming that you will use the 'More Secure' option

  6. Check the summary and click 'Create' once you are happy with the Run As Account

Back to top

Distribute Run As Account

If you selected the 'More Secure' option in the previous section you will need to distribute the new Run As Account:

  1. From the SCOM Administration Pane, expand ‘Run As Configuration', and select 'Accounts’

  2. Find the Run As Account created in the previous section

  3. Right-click on this, select ‘Properties’, then select the 'Distribution' tab

  4. From the ‘Selected Computers' section, press the 'Add’ button

  5. Select your chosen distribution method (we recommend adding the ‘Cookdown Connection Center Resource Pool’) and then OK your way back out

Whilst you can of course distribute this in any way you see fit, we recommend using our Resource pool as this will automatically distribute these credentials to the relevant Management Servers.

Back to top

Configure Run As Profile

  1. From the SCOM Administration Pane, expand ‘Run As Configuration', and select 'Profiles’

  2. Find the relevant Run As Profile for example the 'Cookdown: Connection Center ServiceNow Account'

  3. Right-click on this and select 'Properties'

  4. Skip through the wizard until you reach the ‘Run As Accounts' page and click the 'Add…’ button

  5. Select the 'Run As Account' created earlier

  6. Ensure that ‘All targeted objects’ is selected before clicking 'OK'

  7. Finally press 'Save'

There are a number of different Run-As Profiles included by default, make sure that you select the correct one for your target system.

You can also choose to create and use your own Run-As Profiles, however, these must be stored in a sealed Management Pack to be considered for use by Connection Center. The only exception to this is the Proxy Authentication Run-As Profile, which must be used for Proxy Authentication, but can be scoped as required.

Back to top

Optionally: Modify the Resource Pool Membership

By default, the 'Cookdown Connection Center Resource Pool' is set to automatic membership and contains all of the Management Servers in your Management Group. This has a number of advantages including the same level of high availability that your Management Group is capable of providing, as well as the automatic configuration of any newly commissioned or decommissioned Management Servers. However, should you need to manage this list manually you can do this as follows:

Making a Resource pool have manual membership is a one-way process. The only way to make this automatic again is to remove and then re-import our management pack.

  1. From the SCOM Administration Pane, select 'Resource Pools'

  2. In the list find and select 'Cookdown Connection Center Resource Pool'

  3. Right-click on this, select ‘Manual Membership’, and select 'Yes’ at the warning message

  4. Right-click on this again, select 'Properties'

  5. Next through the wizard until you reach the 'Pool Membership' page

  6. Use the ‘Add’ or 'Remove' buttons to add or remove Management Servers respectively

  7. Press ‘Next' until you are able to press 'Save’

Back to top

Install Tool-specific Components

The following guides can be used to install the required components into the corresponding destination. If you are not responsible for these tools, you can pass them over to a colleague and they will walk them through the required steps in their entirety.

Back to top

After You Finish

At this stage, you should now have all of the relevant components installed for your environment.

Assuming that the tool-specific components are already in place, usually, the next step would be to Configure Outbound Notifications.