CMDB and Asset Management

Armis Integration

This article provides a guide on integrating Armis with Halo for the management of Sites and Assets. It details how to connect to Armis by entering credentials and testing configurations. The guide explains importing sites and assets, setting site and asset rules, and configuring field mappings. It also covers asset type configuration, determining asset types, and synchronizing devices with the Halo Integrator. The Halo Integrator can be set to automatically sync devices and sites, ensuring up-to-date asset management.

Assetbots Integration

AWS Integration

Cisco Meraki Integration

This article provides a comprehensive guide on integrating Cisco Meraki with Halo. It details steps for enabling the integration, connecting using an API key, and configuring imports for customers and assets. The guide also covers setting up alerting through webhooks, allowing events in Cisco Meraki to automatically log tickets in Halo. Additionally, the article explains asset field mappings, determining asset types, import scheduling, and processing webhooks either by default methods or through the Event Management module for enhanced control and security.

Device42 Integration

Domotz Integration

Eracent Integration

This article provides a comprehensive guide on integrating Eracent with Halo for importing assets. It covers steps such as connecting to Eracent, configuring site and user mappings, and managing asset imports. The integration allows for asset import from Eracent and attempts to match associated users and software to Halo users. It details configuration of asset types and miscellaneous settings for syncing, like matching imported software to customer licenses and asset status updates. The integration supports multiple Eracent URLs and allows for scheduled syncing through the Halo integrator.

Halo Asset Discovery (Lansweeper Cloud Integration)

The article provides a comprehensive guide to integrating Lansweeper Cloud with Halo Asset Discovery. It outlines the requirements for connecting the two platforms and details each step of the integration process, including authorization, site mappings, and field mappings. The guide also covers optional configurations like user matching and asset type logic. Import procedures for both REST and Export APIs are illustrated, and the setup for the Halo Integrator is discussed. The piece is tailored for organizations using these services to manage and import assets securely.

Intune Integration

This article provides a comprehensive guide on integrating Microsoft Intune with Halo's asset management system. It covers initial Azure setup, including registration and configuration of an Azure application, and configuration within Halo. The guide details how to map fields, import settings, manage synchronization, and handle asset types and users. It also discusses authentication methods and provides specific configurations for field mappings, asset imports, and the use of Halo Integrator for scheduled syncing. This integration helps improve IT support and asset lifecycle management by ensuring accurate, up-to-date device information.

Iru Integration (Kandji)

Jamf Integration

Juniper Mist Integration

Kaseya VSA X Integration

The article provides a detailed guide on integrating Kaseya VSA X with Halo, covering aspects such as customer and asset imports, alert webhooks, and syncing with the Halo Integrator. It includes step-by-step instructions for connecting to Kaseya VSA X, creating and configuring tokens for API access, and setting up customer and site mappings. It also details how to handle asset imports by configuring asset types, fields, and synchronization settings. Additionally, it explains the process for enabling alert webhooks to log tickets in Halo and the use of the Halo Integrator for automatic synchronization.

Lansweeper Integration

The article provides a guide for integrating on-premise Lansweeper instances with Halo to manage and import assets. It covers key aspects such as pre-requisites, enabling the module, SQL connection details, and mapping fields between Lansweeper and Halo. The integration requires converting Lansweeper’s SQL database from Compact to Standard format before proceeding. The Halo Integrator tool is necessary for the import process, detailing how to set up SQL queries and map key fields like asset identifiers and asset types. Advanced configurations, including user-site matching and password storage options, are also discussed.

LapSafe Integration

This article provides a comprehensive guide to integrating LapSafe with Halo, covering setup, configuration, and usage. The LapSafe integration is designed to manage locker codes for drop-off, collection, and swaps, which can be communicated via email to users. The guide includes step-by-step instructions for enabling the integration, configuring tenant details, defaults, webhooks, and creating actions for various LapSafe operations. Additionally, it explains using LapSafe within the Halo platform to manage requests, actions, and ensure that assets are matched to correct bays to minimize errors.

Liongard Integration

The article provides a detailed guide on integrating Liongard with Halo. It covers setting up the connection, configuring customer and asset imports, and syncing updates between the two platforms. Users can import Liongard environments as customers and systems as assets in Halo, either manually or automatically. The guide also explains how to manage field mappings, configure asset types, and enable automatic imports. Customer updates can be synced to Liongard, and outgoing logs can be viewed for troubleshooting. The overall integration helps maintain consistent data between Liongard and Halo systems.

ManageEngine Endpoint Central Integration

This article is a comprehensive guide to setting up the ManageEngine Endpoint Central integration with Halo. It includes instructions on connecting to Endpoint Central, mapping sites and assets, and configuring miscellaneous settings for effective synchronization and data import. The integration allows for automated importing of asset data from Endpoint Central into Halo, which can be configured to synchronize on a regular schedule once the Halo integrator is enabled. The guide also offers detailed steps for both cloud-hosted and on-premise setups, asset and site rule configurations, and other settings to optimize asset management.

Omnissa Workspace One (VM Workspace One) Integration

Prometheus Integration

Qualys Integration

Raynet Integration

Reconciliation - Order of Precedence for CMDB/Asset Integrations

ScalePad Integration

SCCM Integration

This guide explains the integration of SCCM with Halo, which involves importing assets from the SCCM SQL database into Halo. It includes steps for enabling the integration module, configuring SQL connection details, and setting key fields and field mappings. Advanced configuration options allow control over asset assignment and updates. The integration requires the Halo Integrator application, with options for password storage in Halo or Azure Key Vault. Recommendations are provided for using different integrators and securing access to integrations.

SentinelOne Integration

This article provides a detailed guide on integrating SentinelOne with the Halo platform. The integration enables importing customers, sites, and endpoints from SentinelOne into Halo and supports alert syncing, where alerts in SentinelOne can create and resolve tickets in Halo. Users can connect multiple SentinelOne instances to a single Halo instance after configuring the integration module in Halo with appropriate URLs and API tokens. The article covers the mapping of SentinelOne accounts and sites to Halo customers, importing assets, and setting up asset types. It also explains how to schedule asset imports and configure alert/threat syncing. Finally, outbound requests to SentinelOne are logged for review.

Snipe-IT Integration

Snow Integration

The article explains how to integrate Snow's on-premise instances with Halo to manage assets, including customers, devices, and software licenses. It describes the process of connecting to Snow, mapping and importing customers and assets, determining asset types using various methods, and field mappings for data import. It also covers importing software licenses and setting up automatic updates using the Halo Integrator. The integration involves ensuring proper configuration settings for site and user matching, asset type determination, and syncing of data between Snow and Halo.

SyncroMSP Integration

The SyncroMSP Integration with Halo enables the import of customer and asset data from SyncroMSP, automatically syncing updates and supporting alert management. Users can connect the integration by enabling the module, configuring connection settings with an application URL and API key, and importing customers and assets. Customers and assets are matched and mapped between systems. Automatic synchronization can be set up for ongoing updates. The integration also allows for alerting, where alerts in SyncroMSP create tickets in Halo and are managed across both systems via webhooks.

Tanium Integration

Tenable Integration

Virima Integration

The guide explains the process for the Virima integration into Halo, enabling asset imports from Virima. It covers enabling the integration, connecting to Virima, and configuring site and user mappings. The guide provides details on importing assets, including field and asset type mappings, and setting up miscellaneous integration settings like status and deactivation. Syncing of asset updates can be automated via the Halo integrator, and an asset’s ViVID diagram is available within Halo post-import. The focus is on enabling efficient management of assets transferred from Virima to Halo.

WatchGuard Integration

Xensam Integration