Skip to main content

Change management

Change management prepares, approves and tracks every modification to the IT system, so that an update does not break what was working.

Updated on 14 November 2026

Definition of change management

Change management (called "change enablement" in ITIL 4) governs any modification to the IT system: Windows update, new software, setting change, hardware replacement. The goal: make the change succeed without breaking what was working.

It rests on three questions: what will be affected, who approves, and how to check that everything went well. The first one requires an up-to-date CMDB.

For the device fleet, LongLife answers all three: its automatic CMDB shows the impact, its signed scripts enforce approval, and its device-by-device report checks the result.

A real-world example

An SME wants to remove an old PDF reader from all its devices. In LongLife, the IT technician sees that it is installed on 46 devices, including 3 in the legal department that still use it every day. He excludes these 3 devices, runs the uninstall script on a pilot group of 5 devices, then on the other 38, once a second administrator has approved it. The report confirms: 43 devices processed, no failures.

The three types of change

TypeExampleWhat LongLife gives you
StandardStartup programs cleanupSigned script from the catalogue, ready to run
NormalRemoving software from a departmentDevices concerned (software, site, department), approval, report
EmergencyPatch for a flaw being exploitedUpdate status of each device, lagging devices visible at a glance

Know what is installed on a device

Before a change, check on the device which software is installed, in which version, and which Windows updates it received last: Settings > Apps > Installed apps and the Windows Update history give both. On one device, it is doable. To know which devices across the whole fleet have a given piece of software, you need the LongLife CMDB.

LongLife, changes without nasty surprises

  • Measure the impact: each device with its installed software, site, department and group, and the licences actually used with AppBox;
  • approve: a catalogue of signed scripts, written and tested by OPP!, that grows with every update, a second administrator who approves bulk actions, confirmation or postponement possible by the user;
  • track: report for each device, history in the health log;
  • check the effect: health score, incidents and DEX score before and after.

The free plan covers up to 15 devices. Book a meeting to see your fleet in LongLife, or estimate the gains with the simulator. For a large-scale change, read our method for moving from Windows 10 to Windows 11.

Sources

Frequently asked questions

What is change management in IT?

It is the practice that governs any modification to the IT system (update, new software, setting change) to assess its risk, approve it, carry it out and check the result.

What are the types of change in ITIL?

Standard changes (routine, low risk, pre-approved), normal changes (assessed and approved case by case) and emergency changes (to be carried out quickly, for example to fix a flaw being exploited).

How can I measure the impact of a change before making it?

By knowing which devices, software, sites and departments are concerned. That is the role of a CMDB. LongLife builds it automatically for your device fleet.

How can I prevent a large-scale change from breaking devices?

By starting with a pilot group, having large operations approved by a second person and tracking the result device by device. With LongLife, a second administrator approves bulk actions.

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.