Halo asset management keeps one record per device and per software licence, from purchase to disposal, linked to the people who use it and the tickets raised about it. SMC Consulting's ITIL v4 certified consultants set up the HaloITSM asset module, connect it to Intune, Lansweeper or Jamf so the data stays current, and tie it to your CMDB, contracts and audits.
In ITIL 4, IT asset management plans and manages the full lifecycle of IT assets, to get the most value from them, control costs and support decisions about buying, reusing and retiring them. In HaloITSM it is not a separate product: the asset module is part of the same platform and the same licence as the service desk, so an agent sees the user's laptop, its warranty and its last incidents on the ticket.
IT asset management is one of the practices described in our practical guide to ITSM; HaloITSM is the tool we recommend most often. Looking for ITAM as a service, whatever your tool? See IT asset management services.
HaloITSM is the IT asset management software in this set-up; Lansweeper or Intune feed it with discovered devices.
Laptops, phones, servers, network devices and peripherals, each moving through states such as ordered, in stock, deployed, in repair and retired.
Suppliers, contracts and warranty dates on the asset, with alerts before a renewal window closes.
Installed software and licence entitlements side by side, with over- or under-licensed gaps flagged.
Each asset is tied to its user, location and the incidents and requests raised about it.
A live demo with a sample of your inventory imported, or a free trial: 30 days, 15 of them guided by SMC Consulting.
HaloITSM has no discovery agent of its own: the inventory comes from the tools you already run. We pick one authoritative source per asset class, so two tools never fight over the same record.
Managed Windows laptops, phones and tablets with their users; the natural source in a Microsoft 365 environment.
Agentless discovery of everything on the network, servers and network devices included; webhooks push changes to HaloITSM as they happen.
Macs, iPhones and iPads managed in Jamf, imported with their owners and kept in sync.
For estates still managed on premises: devices and installed software imported on a schedule.
Users, departments and locations, so every asset has an owner who still works here.
Purchase orders, invoices and contracts imported or entered once, so cost and warranty sit on the asset.
An asset becomes a configuration item when a service depends on it; in HaloITSM both use the same record, so the CMDB is not a second inventory.
Device to user, software to device, CI to service: the links that let an agent see who is affected and a change manager see what a change touches.
Incidents, requests and changes are logged against the asset, so its history tells you when to repair, replace or retire it.
Five steps, in Belgium, Luxembourg and France.
Not sure where your asset management stands today? Book my free ITSM audit: 30 minutes with a senior consultant. Still choosing a tool? Our comparison of the 10 best ITSM tools sets HaloITSM against the alternatives.
Where your inventory lives today, who maintains it, and what the asset data must answer: cost, support, audits.
Asset types, mandatory fields, lifecycle states and owners agreed, kept to what you will maintain.
Intune, Lansweeper, Jamf or Configuration Manager connected; a baseline load, duplicates reconciled.
Assets on incidents and requests, warranty and contract fields, dashboards for refresh and compliance.
Monthly accuracy checks, owners for each asset class, and a review at six months.
Who has what, where it is and who owns it, exported from one place when an auditor or an insurer asks.
Which software runs where, against what you bought, so a vendor audit or a renewal starts from facts.
An up-to-date asset inventory and the incidents linked to it: the evidence NIS2 asks for.
Who pay for an asset module they barely use and still keep the inventory in Excel.
Who want the service desk and the asset inventory in one tool from day one.
Who already discover their estate and want that data where tickets are handled.
Not on HaloITSM, or need help running the practice itself? Our IT asset management service covers any tool: inventory, lifecycle, licences and the governance around them.
Yes. HaloITSM has one price per agent with every module included, asset management and the CMDB among them; see HaloITSM pricing. Our advice is independent. If you choose HaloITSM, we can also supply the licences as its certified partner, and we tell you so up front.
Yes. Intune provides managed devices and their users; Lansweeper provides agentless discovery of the whole network and pushes changes to HaloITSM through webhooks. See the HaloITSM and Lansweeper integration.
ITAM manages what you own: cost, contracts, warranty, licences, lifecycle. The CMDB manages what your services depend on and how. In HaloITSM both use the same records; see the CMDB in HaloITSM.
Not always. If Intune or Jamf already cover your devices, they can be enough. HaloITSM has no discovery agent of its own, so Lansweeper is worth adding when you need servers, network devices and unmanaged equipment in the inventory too.
Yes. Installed software and licence entitlements are recorded side by side, and over- or under-licensed gaps are flagged. The quality of the result depends on the software inventory feeding it, which is why we connect a discovery source first.
It depends on the number of sources, the asset types in scope and the state of your current inventory. Connecting one source and importing a clean baseline is usually the first milestone. We date the next milestones once the sources are known.
Book a live demo with a sample of your own devices. You can also start a free trial: 30 days, 15 of them guided by SMC Consulting.
Learn how the ServiceNow MCP server connects AI agents to governed ITSM workflows, Action Fabric and secure enterprise automation, plus readiness steps for 2026.
Read more →
Learn how a HaloITSM Lansweeper integration connects discovery data to HaloITSM, enabling cleaner CMDB records, faster triage, and better change decisions.
Read more →
A practical ServiceNow migration cutover plan helps reduce risk, protect service continuity, validate integrations and support confident ITSM modernisation.
Read more →
