A CMDB kept current by sync, not by hand

OVERVIEW
What is a CMDB?
A configuration management database (CMDB) records the things IT supports and how they relate: which devices a person holds, which applications they use, which services depend on what, and which tickets touch each one. Most CMDBs fail on upkeep. Reconciled by hand each quarter, they are out of date before anyone reads them. What is a CMDB? covers the concept in depth.
Harmony fills its CMDB from sync instead. Devices come from MDM, security status from EDR, people and departments from the identity provider and HRIS, network gear from Cisco Meraki and Juniper Mist, and peripherals from discovery on the endpoint. When a device appears in both a manual import and an MDM, the MDM record wins.
The relationship map links requests, agents, assets, applications, contracts, people and services. Start from anyone or anything: an employee shows their laptops, monitors and peripherals, their applications, their manager and the tickets they raised.
CAPABILITIES
A CMDB your service desk can rely on
Relationship map
Requests, agents, assets, applications, contracts, people and services, linked and explorable from any starting point.
Business services
Define services and link the applications behind them.
Synced configuration items
Model, serial, OS, CPU, storage, battery health, disk encryption, MDM and compliance status, EDR status and last seen for every device.
People context
Each asset joined to its holder and their department, with the former assignee kept when it changes hands.
Parent and child assets
Peripherals linked to the device they connect to, inheriting its owner.
Activity log
Every change recorded with its source: a user action, system event, MDM sync, automation or discovery.
Source precedence
MDM data supersedes manually imported records, so an import never overwrites what a device reports about itself.
CSV import
Up to 1,000 rows per file for assets no connected system reports.
HOW IT WORKS
How the CMDB stays current
A device enrolls or changes hands, an EDR agent goes missing, or an employee joins, moves or leaves.
- 1
Connect the sources
MDM, EDR, identity, HR and network systems sync into Harmony, so nothing is typed in by hand.
- 2
Link the records
Assets join to people, people to applications and tickets, and applications to services and contracts.
- 3
Keep it current
Every sync updates the record and writes the change, with its source, to the activity log.
- 4
Act on gaps
Agents find unassigned devices, employees without a device, missing EDR and unencrypted disks, and open the work before anyone files a ticket.
A CMDB that is rebuilt from source all the time, so the agents and the team can trust it.
Mammoth Brands answers device questions without the device
Because the CMDB pulls from Intune, Kandji, CrowdStrike and Microsoft Entra ID, the agent answers questions the Mammoth Brands team previously couldn't answer without the machine in hand. Marce Ayala's advice to IT leaders: insist on a CMDB that works out of the box and integrates with the major platforms - IdP, MDM, EDR.
“The bot was able to step in and say, hey, I see that your battery actually needs to be replaced. And that's information that we wouldn't have unless we actually got the machine, ran a diagnostic, took a look at it.”
RELATED INTEGRATIONS
Configuration data from every system that has it
Identity and HR
Network
FAQ
Software that records the configuration items IT supports, such as devices, applications, services and people, and how they relate, so incidents, changes and requests start from an accurate picture.
Ready to build your agentic service desk?
See agents resolving your own tickets in a 30-minute session. No slides.