Skip to main content

Configuration management

Configuration management describes each component of the IT system and keeps it up to date, so you know at any time what is in place and how.

Updated on 14 November 2026

Definition of configuration management

Configuration management is the practice that records each component of the IT system, describes its configuration and keeps it up to date: which device, which processor, how much memory, which operating system, which software, which peripherals, for which department. Its data is stored in a CMDB.

Its enemy is time: a configuration recorded by hand is wrong as soon as someone adds software or changes a memory module.

LongLife solves this problem for the device fleet: its agent keeps the configuration of every device up to date, with no manual entry.

A real-world example

Management asks how many devices will be able to run the new version of the business software, which requires 16 GB of memory. By hand, it would mean going round 70 devices. In LongLife, the answer is one filter away: 41 devices have 16 GB, 22 have 8 GB and can be upgraded, 7 need replacing. The budget is worked out straight away.

What a device's configuration contains

ItemExampleWhat LongLife gives you
HardwareProcessor, memory, disks, batteryAlways up to date, with health status
Operating systemWindows version, updatesEnd of support and days remaining per device
SoftwarePublisher, version, automatic startupList per device and the licences actually used
PeripheralsUSB, Bluetooth, printersLinked to the device
SecurityAntivirus, firewall, BitLocker, UACPosture of each device
AssignmentSite, department, groupView by site and by department

Record a device's configuration

By hand, you note the device name, manufacturer, model, Windows edition and version, then keep that record in a file. One file per device, to be redone after every change: that is the limit of the manual approach. LongLife removes it.

LongLife, automatic configuration management

  • Automatic recording of every device, performance tracked continuously;
  • a CMDB that is always accurate: hardware, operating system, software, peripherals, security, site, department, history;
  • instant answers: filters by model, memory, operating system version, site;
  • the next step: a recommendation to keep, upgrade or replace, with the cost and CO₂e, and remote action through a catalogue of signed scripts, written and tested by OPP!, that grows with every update;
  • CSV exports and scheduled PDF reports for audits.

The free plan covers up to 15 devices. Book a meeting to see your fleet's configuration, or start with the simulator. To go further, read our guide to IT asset management.

Sources

Frequently asked questions

What is configuration management?

It is the practice that records the components of the IT system (devices, software, peripherals, licences), describes their configuration and keeps it up to date. Its data is stored in a CMDB.

What is the difference between configuration management and a CMDB?

Configuration management is the process, the CMDB is the database where it stores its data. Without the process, the CMDB goes out of date; without a CMDB, the process has no tool.

How can configurations be kept up to date without manual entry?

With an agent that records each device's configuration automatically. This is what LongLife does: hardware, operating system, software, peripherals and security, always up to date, with no manual entry.

Why is configuration management useful?

It speeds up troubleshooting, makes changes safer, and prepares audits and refreshes. It answers questions such as "how many devices have less than 8 GB of memory?" in seconds.

Read also

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.