HaloPSA

HaloPSA Guides

Documentation to assist with the setup and configuration of the HaloPSA platform

Guides > SCOM Integration

SCOM Integration

In this guide we will cover:

- Enabling the Integration

- SCOM Configuration

- Halo Configuration

- Resolving Alerts in SCOM



Related Guides:


Enabling the Integration

To enable the SCOM integration, navigate to Configuration > Integrations > Asset Management and Alerting, and enable the module using the plus icon in the top right hand corner of the menu icon. Once the module has been enabled, click the menu icon to begin configuring it. 


SCOM Configuration

For the integration to function successfully, your SCOM alert templates must be altered. On the message template, add the following line of text to the top of template body:


Alert ID: {$Data/Context/DataItem/AlertId$} 


Adding this allows Halo to store the ID of alerts against any tickets that are raised via an alert email from SCOM. Secondly, if you are using the SCCM integration to import your assets and would like to link tickets created via alerts to their corresponding assets, add the following line of text to your template under the above line:


Device Name: {$Data/Context/DataItem/ManagedEntityDisplayName$} 


Halo uses the SCOM API to resolve alerts automatically when their linked ticket is resolved. This functionality uses NTLM authentication, which should already be enabled on your SCOM server. 


To confirm this, open IIS, select your web server node and click into authentication. Ensure that Windows Authentication is enabled, then right click Windows Authentication and select providers. If NTLM is not in the list of available providers, then add it from the list of available providers. 


Fig 1. List of providers.


Halo Configuration

When opening the module, the first set of instructions briefly cover modifying your SCOM alert templates as mentioned in the previous section. Below this, you will see three configuration options. 


Fig 2. Setup.


The first option is the from address, which should be the email address from which alerts will be sent from SCOM to Halo. 


The second option allows you to choose which ticket type alerts from SCOM should be created as.


The third option is used for asset matching. If you have modified your SCOM template to include the device name, then you should choose which asset field stores this value for your assets in Halo. This allows Halo to link the correct asset to a ticket when created via an alert received from SCOM.


By modifying these fields, an email rule has been created for you to help capture and process the alerts from SCOM. If you would like to view the rule in more detail, then this can be done by navigating to Configuration > Email > Email Rules.


Resolving Alerts in SCOM

To automatically resolve alerts in SCOM, the Halo integrator must be run from a location that can access the SCOM API. It is recommended to deploy this on the SCOM server itself.


To authenticate with the SCOM API, the Halo integrator requires your server name, domain, and a windows username and password. This user must have access to SCOM, and have the ability to resolve alerts manually in the SCOM application. Populate the four available fields in the Halo UI to complete this configuration step.


Fig 3. SCOM connection.


Underneath these fields, you can download the Halo Integrator and enable it for the SCOM integration. Once downloaded and enabled, open the Halo Integrator and open the SCOM integration tab. To ensure that your configuration is correct, run the configuration check that is available on the tab. If all configuration checks in the list return a green tick, then you are ready to begin running the Halo integrator to close SCOM alerts automatically.

Popular Guides