CMDB
A CMDB (Configuration Management Database) records the components of an IT system, their attributes and the links between them, to know what a failure or a change will affect.
Updated on 14 November 2026
Definition of a CMDB
A CMDB (Configuration Management Database) is the database that describes a company's IT system: each component, its attributes and, above all, the links between components. Its purpose: to know, before acting, what a failure or a change will affect.
Each recorded component is called a configuration item, or CI: a computer, a piece of software, a peripheral, a licence, a site, a department.
For the workstation fleet, LongLife is a ready-to-use CMDB: its agent builds and updates the database on its own, with no manual entry.
A real-world example
An SME has to update its accounting software on a Tuesday at 2 pm. Without a CMDB, the IT technician wonders who will be affected. With the LongLife CMDB, he sees at a glance that:
- the software is installed on 12 devices, all in the accounting department;
- 2 of these devices have only 8 GB of memory and an almost full disk;
- one of them had two blue screens this week.
He moves the update to 7 pm, warns the department, and plans work on the two fragile devices beforehand. That is the whole point of a CMDB: moving from a list of machines to a view of links and risks.
CMDB, inventory, ITAM: the differences
| Concept | Question it answers | What LongLife gives you |
|---|---|---|
| Inventory | What do we own? | All devices, their hardware, software and peripherals |
| CMDB | What is linked to what? | Each device linked to its site, department, software, peripherals and history |
| ITAM (IT asset management) | How much does it cost, and until when? | Licences owned, installed and actually used, end of support, cost of decisions |
| Device health | What state is each device in, right now? | Score per device, continuous incident detectors, recommended action |
A CMDB is only worth something if its data is accurate. Filled in by hand, it is out of date within weeks. That is why the only reliable CMDB is one an agent feeds on its own.
LongLife, the automatic CMDB for your device fleet
LongLife installs an agent on each device. From installation, your CMDB fills itself and stays up to date:
- each device and its configuration: hardware, operating system, installed software and peripherals;
- the links: device users, site, department or group, installed software, licences actually used;
- the history: hardware changes spotted automatically and matched with the work recorded in the maintenance log;
- the real state: health score, security posture, Windows end of support, incidents flagged by detectors that analyse your fleet continuously;
- the decision: keep, upgrade or replace, with the cost and CO₂e of each option, and remote action by signed script;
- the output: inventory export to CSV or PDF, filtered by site, department, operating system or status.
Where a classic CMDB stops at describing the fleet, LongLife also tells you what is going wrong and what to do. It works on its own, or alongside a ticketing tool such as GLPI.
The free plan covers up to 15 devices. To see your own fleet in LongLife, book a meeting, or first estimate the savings with the simulator. To go further, read our guide to IT asset management.
Sources
- AXELOS, ITIL 4, "Service configuration management" practice: axelos.com
- Microsoft, querying system information on Windows: learn.microsoft.com
Frequently asked questions
What does CMDB stand for?
CMDB stands for Configuration Management Database. It is a concept from ITIL, the best-practice framework for IT service management.
What is the difference between a CMDB and an inventory?
An inventory lists the equipment and its attributes. A CMDB adds the links between items (this device belongs to this department, this software is installed on these devices, this printer is connected to this device) to measure the impact of a failure or a change.
How can I keep a CMDB up to date without filling it in by hand?
By having it fed by an agent installed on each device. This is what LongLife does by default: every device keeps its hardware, software, peripherals and status up to date, with no manual entry.
Is there an open source CMDB?
Yes, iTop (from the French vendor Combodo) and GLPI offer CMDB features, which you fill in and maintain. LongLife builds the CMDB of your device fleet automatically, and its free plan covers up to 15 devices.
Read also
ITAM
ITAM (IT Asset Management) tracks every piece of equipment and every licence from purchase to end of life, with its cost, contracts and key dates, to spend less and decide at the right time.
TCO
TCO (Total Cost of Ownership) adds up all a device costs over its life, not just its price: deployment, support, failures, energy, lost time, end of life.
See the real state of your fleet
LongLife measures the health of your Windows devices every day and recommends keeping, upgrading or replacing them, with the cost and CO₂e of each option.