<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;
}
.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;
}
.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 SCCM Integration?</strong></p><p><strong>- Enabling the Module </strong></p><p><strong>- SQL Details</strong></p><p><strong>- Key Fields</strong></p><p><strong>- Field Mappings</strong></p><p><strong>- Advanced Configuration</strong></p><p><strong>- Halo Integrator</strong></p><p><br></p><p><br></p><p><strong><span style="font-size: 14pt;">What is the SCCM Integration?</span></strong></p><p>The SCCM integration can be used to import assets into Halo from the SCCM SQL database.</p><p><br></p><p><strong><span style="font-size: 14pt;">Enabling the Module</span></strong></p><p>To enable the SCCM integration in Halo, go to Configuration > Integrations, and enable the module using the '+' icon. Once the module has been enabled, click the menu icon for the module to begin configuring it.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6Ijc2M2ZjYjk1LTBmZjgtNDc3OS04ZmM4LTNlNTlmNDRkOGVlYyJ9.EEitIgl5VqN_FHscAvRyIIngwnqIqbS4jKZH2MrSuzs" class="fr-fic fr-fil fr-dib" width="323" height="148"></p><p><strong><span style="font-size: 10pt;">Fig 1. Enable integration module</span></strong></p><p><br></p><p>As the SCCM integration is effectively an import from one SQL database to another, access to the SCCM database is required. This means there is no import facility within the web application itself, and instead, the <a data-fr-linked="true" href="https://usehalo.com/halopsa/guides/1062" id="isPasted" target="_blank" rel="noopener noreferrer">Halo Integrator application</a> must be downloaded. More details will be given regarding the Halo Integrator later in this guide.</p><p><br></p><p><strong><span style="font-size: 14pt;">SQL Details</span></strong></p><p>You will need to start by setting the SQL connection details for the integration. </p><p><br></p><p>Both SCCM and Halo have a SQL database. This integration is an import from one SQL database into another, and the Halo Integrator will need details of how to connect to your SCCM database. Under the SQL Connection header, you will need to specify connection details for your SQL Server, and also the query that should be run against the SCCM database for the import.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImRmNmQzNTI2LTkwYjItNDUyNS1iODNmLWE5NmI3YTVlZjljNiJ9.z2QYLOvnEhrhj0GVwJhubwQAmO4VDStP2-BNnhoKM0A" class="fr-fic fr-fil fr-dib" width="1103" style="width: 1105px; height: 654.137px;" height="654"></p><p><strong><span style="font-size: 10pt;">Fig 2. Configuring the SQL connection</span></strong></p><p><br></p><p>An example query is provided in the 'SQL Query' field however you will need to adjust this to ensure this returns the exact assets you would like to import. The query will also need to return the:</p><ul><li>Site the asset is stored under</li><li>User assigned to the asset</li><li>Asset field which contains information on the asset's type</li><li>Asset field used as the unique identifier for the asset (e.g. serial number)</li><li>Any other asset fields you would like to be imported </li></ul><p><br></p><p><strong>Password Storage Method -</strong> This determines how your password for your SQL database will be stored. You can choose for this to be stored in Halo or the <a data-fr-linked="true" href="https://usehalo.com/haloitsm/guides/1715" id="isPasted" target="_blank" rel="noopener noreferrer">Azure Key Vault</a>. If you are looking to use Azure Key Vault ensure you have this integration setup. More information on the password storage options can be found in the 'Halo integrator' section of this guide. </p><p><br></p><p><strong>Timeout -</strong> Here you can set the time (in seconds) the SQL query is given to complete, if it still has not completed after this time it will timeout. We advise against setting this unnecessarily high as it will cause delays to other functions.</p><p><br></p><p>The Integrator will attempt to import any record that is returned via the SQL query. Later in the integration setup, you have the option to map fields from the SCCM database to Asset fields in Halo. You should ensure that any information you would like importing into Halo is selected in this SQL query.</p><p><br></p><p><strong><span style="font-size: 14pt;">Key Fields</span></strong></p><p>Next, you will need to set the key fields for the import. You will need to specify which column in your query returns each key piece of asset information Halo needs. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImMwYjlkZjcyLTRkNjctNDYxMy1hYjk5LTliYjEzYmJhNGRhNCJ9.HTKdqL2CXzjFO_GQxOwjtKsGjCZ6xje78TkEEJi8aoE" class="fr-fic fr-fil fr-dib" width="1515" style="width: 1517px; height: 419.927px;" height="420"></p><p><strong><span style="font-size: 10pt;">Fig 3. Key fields</span></strong></p><p><br></p><p><strong>Asset ID -</strong> Here, enter the column from your dataset which contains the Asset's unique identifier, if you have given the column an alias you can enter the alias name here. This will be used as the unique identifier for the asset.</p><p id="isPasted"><strong>Asset Type -</strong> Here, enter the column from your dataset which contains the Asset's type, if you have given the column an alias you can enter the alias name here. All assets in Halo must have a type, therefore the query must return a field that contains information about the asset's type. This will be used to assign the assets a type when they are created in Halo. </p><p id="isPasted"><br></p><p><strong><em>Note: If you do not wish to select an actual Asset Type field in your SCCM query, or you wish to import all Assets into the same Asset Type, you can hardcode a value in your query. For example, '</em></strong><em>select ‘SCCM Assets’ as [AssetType] from Table</em><strong><em>' In this example, AssetType would be your Asset Type key field. This would set all assets to the asset type SCCM Assets (if it exists).</em></strong></p><p><br></p><p><strong>Site Name -</strong> Here, enter the column from your dataset which contains the site the asset is under, if you have given the column an alias you can enter the alias name here. This will be used to assign the asset to a site in Halo, therefore the query should return the name of the site, if this site name cannot be matched to an existing site in Halo, the asset will be assigned to the default site. </p><p><strong>Default Site -</strong> Here, choose the site you would like assets to be created under if they cannot be matched to a site using the column specified in the 'Site Name' field. </p><p><br></p><p><strong>User ID -</strong> Here, enter the column from your dataset which contains the unique identifier for the user of the asset, if you have given the column an alias you can enter the alias name here. This column should return either the username, email address, or windows username of the User. This will be used to assign the assets a user when they are created in Halo. The unique identifier being used for the user can be chosen in the 'User Matching Field'.</p><p id="isPasted"><strong>User Matching Field -</strong> Here choose which field is being used to match users in SCCM to users in Halo. This should be the unique identifier of users and should be returned by your SQL query. </p><p><br></p><p><strong><span style="font-size: 14pt;">Field Mappings</span></strong></p><p>It is possible to map additional fields that are returned in your SCCM query to Halo Asset fields. You must ensure that any fields you wish to map are returned in your query. To add a new mapping, press the plus icon in the top right corner of the table.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjMwOGMxYzhmLTkxZjItNGRjYS04Y2MxLTc2ZWJjMzBlYTk0ZCJ9.GT4nlqChjoFr6L07_PwIeJxgdvY4uiey3jKMzNm0hxs" class="fr-fic fr-fil fr-dib" width="1488" style="width: 1490px; height: 523.41px;" height="523"></p><p><strong><span style="font-size: 10pt;">Fig 4. Field mappings</span></strong></p><p><br></p><p>First specify the name of the field as it is returned in your SQL query. Then you must choose which field you would like to map the SCCM field to in Halo. There are some system fields available, along with the option of *Asset Field*. If this option is chosen, when importing, a field will be created with a name equal to the SCCM query field name and the data will be added to this new field. If a field already exists with that field name, or after it has been created, the data from the SCCM field will be mapped into the Halo field.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjQ1MTQ4YzMyLTk5YzYtNGVhMS04ZDU3LWMzMzEwNzlmM2Q4ZSJ9.PRatexmn2ZR7jy1zOTHdPbOVbF0-9GPDugaVisz_ydA" class="fr-fic fr-fil fr-dib" width="623" style="width: 625px; height: 463.178px;" height="463"></p><p><strong><span style="font-size: 10pt;">Fig 5. New field mapping</span></strong></p><p><br></p><p>The table is populated with some mappings by default, if using the default mappings ensure the columns returned by your query are named in line with the default mappings, otherwise remove these mappings and add your own.</p><p><br></p><p><strong><em>Note: You can also create mappings for the fields used in Key Fields if you wish. For example, you will not be able to see the value of the Asset’s unique ID field unless you also map it to another Halo field.</em></strong></p><p style="margin-left: 20px;"><br></p><p style="margin-left: 20px;"><strong>Mapping Relationship Types</strong></p><p style="margin-left: 20px;">The relationship type between parent, child, and sibling assets can be mapped. To do this choose the "Parent/Child/Sibling Asset Relationship Types" field when creating a mapping.</p><p style="margin-left: 20px;"><strong><em><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjI5OWNhZjg4LTY0MGUtNDk2MC1hMGJlLWNlYWMwZTFlZWU4OCJ9.0OBlWVuya8PTTBadIWZykgAoHX1AAicCsl1147nNh6A" class="fr-fic fr-fil fr-dib" width="646" style="width: 648px; height: 381.447px;" height="381"></em></strong></p><p style="margin-left: 20px;"><strong><span style="font-size: 10pt;">Fig 6. Map Parent/Child/Sibling Asset Relationship Types</span></strong></p><p style="margin-left: 20px;"><strong><em><br></em></strong></p><p style="margin-left: 20px;">In the SCCM Field you will need to enter the field (column) that returns a comma separated list of relationship names. Each relationship type in the list will be applied to the related Assets in order. If the field only contains one relationship, all related Assets will have this relationship applied.</p><p><br></p><p><strong>Asset Matching Field -</strong> Here select the Halo field that is used to match existing asset. This should be the field that is returned by the column specified in the Asset ID field. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjY1MDI1MWZkLTc4NTUtNDY0MS04OGQxLTE0OGIxNjMxMzY1YiJ9.o4E4jEqettg54Hey_v54dvu1DRwzQxt9TNhbHk2XOUM" class="fr-fic fr-fil fr-dib" width="689" height="178"></p><p><strong><span style="font-size: 10pt;">Fig 7. Asset matching field and value exclusions</span></strong></p><p><br></p><p id="isPasted"><strong>Asset Matching Value Exclusions -</strong> Here you can set assets to not be matched using the matching field if the matching field contains a certain value. For example, if two assets have the matching field set to be 'None' they would match even though they are separate assets. By adding the value 'none' to the matching value exclusions list you can ensure the assets are not matched using this field. </p><p><br></p><p><strong><span style="font-size: 14pt;">Advanced Configuration</span></strong></p><p>There are some additional advanced options available for this integration.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjkzY2Q2YzgyLThiMzItNDdmNy1iMTYzLWJhNGE4ODgyMzE5MiJ9.K74uSL16LhPkNgSF2YvRf4L2RJcODFY1nxLUZb-xAhc" class="fr-fic fr-fil fr-dib" width="641" height="388"></p><p><strong><span style="font-size: 10pt;">Fig 8. Advanced configuration options.</span></strong></p><p><br></p><p><strong>Assign Assets to their User's Site if a User is successfully matched -</strong> When enabled, assets will be assigned to a site based on the user they are matched to. This will override any other site matching. </p><p><br></p><p><strong>Do not update an Asset's Site if the Asset already exists (overrides the above setting) -</strong> When enabled, if an import is updating existing assets, their site will not be updated. Newly imported assets will still have their site set on import. This will override the above setting if enabled.</p><p><br></p><p><strong>Do not remove existing Users from an Asset if a valid User is not found -</strong> When enabled, if an asset is updated using an import and it cannot be matched to a valid user, if the asset already has a user assigned this user will remain assigned to the asset. When disabled the user would be unassigned from the asset.</p><p><br></p><p><strong>Do not create new Asset records (update only) -</strong> Enable this if you would only like the import to update existing assets, you would not like it to create new asset records. </p><p><br></p><p><strong>Ignore mandatory field checks -</strong> When enabled assets can still be imported (created) without having any mandatory fields populated through the import. This should only be enabled if the mandatory fields have a default set and you would like them populated with this value on import. In addition, if enabled asset field cannot be created by a SCCM import, SCCM field must be mapped to existing fields in Halo. </p><p><br></p><p><strong>Match imported software to Customer licences based on name - </strong>When enabled, assets will be attempted to be matched to customer licences if the name of the asset matches the licence name. Used when software licences are being imported as assets. </p><p><br></p><p><strong>Do not update Asset Types - </strong>When enabled, the asset type of an asset will not be updated to a different type during an import. Used when you would not like asset types to change once set in Halo. </p><p><br></p><p><strong><span style="font-size: 14pt;">Halo Integrator</span></strong></p><p>To run the import for SCCM, the Halo Integrator application <a data-fr-linked="true" href="https://usehalo.com/haloitsm/guides/1062" id="isPasted" target="_blank" rel="noopener noreferrer">Halo Integrator application</a> must be downloaded. </p><p><br></p><p><strong><span style="font-size: 12pt;">Which Integrator to use?</span></strong></p><p>One of two integrators can be downloaded to run this application:</p><ul><li><a data-fr-linked="true" href="https://usehalo.com/haloitsm/guides/1766" id="isPasted" target="_blank" rel="noopener noreferrer">Halo DB integrator</a></li><li>Locally hosted Halo integrator</li></ul><p>The Halo DB integrator must be used if you are hosting your own instance of Halo. You may also choose to use the Halo DB integrator if you would not like your password to be accessible via the API.</p><p><br></p><p>The locally hosted integrator can be used if your Halo instance is hosted by us (in the cloud), using this integrator can make setup easier if you already have this integrator setup for other integrations. Keep in mind using this integrator may result in your password being accessible via the API, however this will depend on your password storage method chosen. </p><p><br></p><p>If Azure Key vault is being used as the password storage method, the password will not be accessible via the API regardless of the integrator selected. </p><p><br></p><p><strong><span style="font-size: 12pt;">Enable the Integrator</span></strong></p><p>Once the integrator is setup for the SCCM integration, make sure that the integration is enabled for the Halo Integrator and choose which integrator you are using. When enabled, two additional fields will display, showing the last successful run time, and the last error (if there was one). This will alert you to any potential issues with the import if you are running the import on a recurring schedule.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjYxMDE2NzVmLTM4NDMtNGIxYy1hYzg2LTM3NWFjNTc5YjZjYyJ9.B-PSe_XP0osFzCk0mICEskpbA79eE-W4BsiG911ZGZA" class="fr-fic fr-fil fr-dib" width="1008" style="width: 1010px; height: 269.651px;" height="270"></p><p><strong><span style="font-size: 10pt;">Fig 9. Enabling the Halo Integrator.</span></strong></p><p><br></p><p>Once you have chosen your integrator you will need to choose the method you would like to use for password storage in the 'Password Storage Method' field. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjNhNGIzMzM2LWFiMWItNGFhYS1iNDgzLWM3NzM3NGFmOGIyYyJ9.Q-qXeCaebaXnZfg7EUpfpenbdZ7O0mE_WDHU03e2TPo" class="fr-fic fr-fil fr-dib" width="398" style="width: 400px; height: 346.957px;" height="347"></p><p><strong><span style="font-size: 10pt;">Fig 10. Password storage method</span></strong></p><p><br></p><p><strong>Halo</strong>- When this method is chosen your password will be stored by Halo, it will be accessible via Halo's API if the Halo Integrator is chosen as the integrator too. If using the Halo DB integrator your password will not be accessible via the API. </p><p><strong>Azure Key Vault</strong> - When this method is chosen your password will be stored by Azure key Vault, it will not be accessible via Halo's API if the Halo Integrator is chosen as the integrator too. If you would like to use this method of storage you will need to configure a key vault in the Azure Key Vault integration. For information on setting up the Azure Key Vault integration, check out our guide: <a data-fr-linked="true" href="https://usehalo.com/haloitsm/guides/1715" id="isPasted" target="_blank" rel="noopener noreferrer">Azure Key Vault</a>. Once you have configured a Key Vault in Halo you will be able to choose which Key Vault to store the password in. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjA0MjFiMTA5LTQ5M2EtNDg2ZS04Y2E5LWE2YzU1NWRmMTkwMiJ9.byoaeMQUnqjDMQH2AXbhLr5u56WGT8I0l3Auz_8wd6g" class="fr-fic fr-fil fr-dib" width="321" height="166"></p><p><strong><span style="font-size: 10pt;">Fig 11. Choose Key vault to store password in</span></strong></p><p><br></p><p><strong>Recommended:</strong></p><p>If you are using the '(locally hosted) Halo integrator' to schedule imports we recommend using Azure Key Vault as the password storage method as this will ensure your password is not accessible via the API. If using the Halo DB integrator you can use Azure Key Vault to store passwords for increased security, however, even when Halo is used as the password storage method the password will not 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 12. 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.eyJpZCI6ImVlZWY0MGNmLWYxNzAtNDE1Ny1iYWJmLTU3MTU0NmI1YTc4MCJ9.EEVryVMP2PTdQjCMYAVWff0Qh5AsFn0ey2yp6M05d1Y" class="fr-fic fr-fil fr-dib" width="503" style="width: 505px; height: 357.071px;" height="357"></p><p><strong><span style="font-size: 10pt;">Fig 13. 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>
