<style>p { margin: 0; }span.fr-emoticon.fr-emoticon-img { background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle; } span.fr-emoticon { font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0; } blockquote { border-left: solid 2px #5e35b1; color: #5e35b1; margin-left:0; padding-left:5px;}blockquote blockquote{ border-color: #00bcd4; color: #00bcd4;}blockquote blockquote blockquote{ border-color: #43a047; color: #43a047;} table.grid{ border-collapse: collapse;} table.grid td, table.grid th { border: 1px solid #ddd;} .fr-fic.fr-dib{ display: block; margin: 5px auto;}.fr-fic.fr-dib.fr-fir{ text-align: right; margin: 5px 0 5px auto;}.fr-fic.fr-dib.fr-fil{ text-align: left; margin: 5px auto 5px 0;}.fr-fic.fr-dii{ float: none; margin: 5px auto;}.fr-fic.fr-dii.fr-fil{ float: left; margin: 5px auto;}.fr-fic.fr-dii.fr-fir{ float: right; margin: 5px auto;}img.fr-dib.fr-fir { margin-right: 0; text-align: right;}img.fr-dib.fr-fil { margin-left: 0; text-align: left;}img.fr-dib { margin: 5px auto; display: block; float: none;}img.fr-bordered { box-sizing: content-box; border: solid 5px #CCC;}img.fr-shadow { box-shadow: 10px 10px 5px 0px #cccccc;}img.fr-rounded { border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;}</style><style>
p {
margin: 0;
}
span.fr-emoticon.fr-emoticon-img {
background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle;
}
span.fr-emoticon {
font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0;
}
blockquote {
border-left: solid 2px #5e35b1; color: #5e35b1; margin-left: 0; padding-left: 5px;
}
blockquote blockquote {
border-color: #00bcd4; color: #00bcd4;
}
blockquote blockquote blockquote {
border-color: #43a047; color: #43a047;
}
table.grid {
border-collapse: collapse;
}
table.grid td,
table.grid th {
border: 1px solid #ddd;
}
.fr-fic.fr-dib {
display: block; margin: 5px auto;
}
.fr-fic.fr-dib.fr-fir {
text-align: right; margin: 5px 0 5px auto;
}
.fr-fic.fr-dib.fr-fil {
text-align: left; margin: 5px auto 5px 0;
}
.fr-fic.fr-dii {
float: none; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fil {
float: left; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fir {
float: right; margin: 5px auto;
}
img.fr-dib.fr-fir {
margin-right: 0; text-align: right;
}
img.fr-dib.fr-fil {
margin-left: 0; text-align: left;
}
img.fr-dib {
margin: 5px auto; display: block; float: none;
}
img.fr-bordered {
box-sizing: content-box; border: solid 5px #CCC;
}
img.fr-shadow {
box-shadow: 10px 10px 5px 0px #cccccc;
}
img.fr-rounded {
border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;
}
</style><style>
p {
margin: 0;
}
span.fr-emoticon.fr-emoticon-img {
background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle;
}
span.fr-emoticon {
font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0;
}
blockquote {
border-left: solid 2px #5e35b1; color: #5e35b1; margin-left: 0; padding-left: 5px;
}
blockquote blockquote {
border-color: #00bcd4; color: #00bcd4;
}
blockquote blockquote blockquote {
border-color: #43a047; color: #43a047;
}
table.grid {
border-collapse: collapse;
}
table.grid td,
table.grid th {
border: 1px solid #ddd;
}
.fr-fic.fr-dib {
display: block; margin: 5px auto;
}
.fr-fic.fr-dib.fr-fir {
text-align: right; margin: 5px 0 5px auto;
}
.fr-fic.fr-dib.fr-fil {
text-align: left; margin: 5px auto 5px 0;
}
</style><p><strong>In this guide we will cover:</strong></p><p><strong>- What is the SCOM Integration?</strong></p><p><strong>- Enabling the Integration</strong></p><p><strong>- SCOM Configuration</strong></p><p><strong>- Halo Configuration</strong></p><p><strong>- Resolving Alerts in SCOM</strong></p><p><br></p><p><br></p><p><strong>Related Guides:</strong></p><ul><li><a href="https://usehalo.com/haloitsm/guides/1910" target="_blank" rel="noopener noreferrer"><strong>Email Rules</strong></a></li><li><a href="https://usehalo.com/haloitsm/guides/1060" target="_blank" rel="noopener noreferrer"><strong>SCCM Integration</strong></a></li></ul><p><br></p><p><strong><span style="font-size: 14pt;">What is the SCOM Integration?<br></span></strong></p><p>SCOM can be integrated with Halo to create and resolve alerts.</p><p><br></p><p><strong><span style="font-size: 14pt;">Enabling the Integration</span></strong></p><p>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. </p><p><br></p><p><strong><span style="font-size: 14pt;">SCOM Configuration</span></strong></p><p>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:</p><p><br></p><p style="text-align: left;"><em>Alert ID: {$Data/Context/DataItem/AlertId$} </em></p><p style="text-align: center;"><br></p><p>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:</p><p><br></p><p style="text-align: left;"><em>Device Name: {$Data/Context/DataItem/ManagedEntityDisplayName$} </em></p><p style="text-align: center;"><br></p><p>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. </p><p><br></p><p>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. </p><p><br></p><p><img src="http://halo.haloservicedesk.com/api/attachment/image/e179fa79-e1c5-44f3-a6cc-d503ac3b8ca2" class="fr-fic fr-fil fr-dib" width="432" height="359"></p><p><strong><span style="font-size: 10pt;">Fig 1. List of providers.</span></strong></p><p><br></p><p><strong><span style="font-size: 14pt;">Halo Configuration</span></strong></p><p>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. </p><p><br></p><p><img src="http://halo.haloservicedesk.com/api/attachment/image/cfd74331-3a1c-4e36-b516-b0cd645afe9a" class="fr-fic fr-fil fr-dib" width="1089" height="265"></p><p><strong><span style="font-size: 10pt;">Fig 2. Setup.</span></strong></p><p><br></p><p>The first option is the from address, which should be the email address from which alerts will be sent from SCOM to Halo. </p><p><br></p><p>The second option allows you to choose which ticket type alerts from SCOM should be created as.</p><p><br></p><p>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.</p><p><br></p><p>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.</p><p><br></p><p><strong><span style="font-size: 14pt;">Resolving Alerts in SCOM</span></strong></p><p>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.</p><p><br></p><p>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.</p><p><br></p><p><img src="http://halo.haloservicedesk.com/api/attachment/image/60902088-42ea-4fb6-bed1-a5c93e827052" class="fr-fic fr-fil fr-dib" width="1086" height="154"></p><p><strong><span style="font-size: 10pt;">Fig 3. SCOM connection.</span></strong></p><p><br></p><p>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.</p><p><br></p><p><strong><span style="font-size: 14pt;">Halo Integrator<br></span></strong></p><p>You will have a choice of integrators that can be used to schedule this import, allowing you to choose between using the Halo integrator application (hosted by you) or the Halo DB integrator (hosted by you). The primary difference between these choices is how your password will be exposed. The Halo integrator application will access your Halo database, including obtaining your password, through the API, which means the password for the integration will need to be accessible via the API. Whereas the Halo DB integrator has the Halo API built into it and connects directly to your database. For more information on the Halo integrator application and the Halo DB integrator check out <a data-fr-linked="true" href="https://usehalo.com/haloitsm/guides/1766" id="isPasted" target="_blank" rel="noopener noreferrer">Halo DB integrator</a>.</p><p><br></p><p>Your choice of integrator will impact how the password used for the integration is exposed, whether it is accessible via the API or not, but this will also be determined by your chosen password storage method. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjdhMzYyY2NiLTJiNzQtNGQ2OS05Y2ZiLWVkZGU1YWM3NTFhOCJ9.XNO1uAlxkSWP-Lxq2YkSDJ7Vw-COtNF6Dxj8WvPvfb4" class="fr-fic fr-fil fr-dib" width="746" style="width: 748px; height: 252.522px;" height="253"></p><p><strong><span style="font-size: 10pt;">Fig 4. Integrator selection</span></strong></p><p><br></p><p>When the 'Halo Integrator' is selected you will still be able to use a Halo DB integrator to schedule imports in addition to this integrator. However, if you have selected 'Halo DB integrator', the Halo integrator will not be able to run for this integration. </p><p><br></p><p><strong><em>Note: On-Prem customers will not be able to use the Halo Integrator. </em></strong></p><p><br></p><p><strong>Recommended:</strong></p><p>We recommend using the Halo DB integrator to schedule imports for SCOM as currently passwords can only be stored in Halo, therefore if using the Halo integrator this will be accessible via the API. </p><p><br></p><p>If you have multiple Halo integrator applications you may wish to restrict which of these have access to this integration. By default all client IDs will be able to access On-Prem integrations, however, this can be disabled, allowing you to whitelist which client IDs can access the integration. </p><p><br></p><p>To do this head to configuration > advanced settings > disable 'Allow all client IDs to access all On-Prem integrations which use the Halo Integrator'. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjgwYWNkYzI3LWU0MTgtNDc4Yi1iZWYyLWFiZjJkOTQ0MjJkNyJ9.4zjGpPnlULtd5qHmVf7Ra1lQFP51W0oZ8hrGobnU2sA" class="fr-fic fr-fil fr-dib" width="783" style="width: 785px; height: 214.673px;" height="215"></p><p><strong><span style="font-size: 10pt;">Fig 5. Allow all client IDs to access all On-Prem integrations which use the Halo Integrator</span></strong></p><p><br></p><p>Now, on the integration setup page in Halo, you will have an option to add in the client IDs you would like to whitelist for this integration. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6Ijg1Yjg0NTM3LWFlNWMtNDc3Ny1iZDYzLWNmYzkyNWRlNmJiNiJ9.FEjH7wZmRsKYIjjFV1oYnh0aItTu4ciIfSR9y1wL6Ho" class="fr-fic fr-fil fr-dib" width="644" style="width: 646px; height: 431.538px;" height="432"></p><p><strong><span style="font-size: 10pt;">Fig 6. Allowed client IDs for integration</span></strong></p><p><br></p><p>Here, enter the client IDs for the applications set up to authorise the connection between your Halo instance and your Halo Integrator. Only the integrators authorised using these client IDs will be able to access this integration. </p>
