How to manage a fleet of company computers in Algeria (2027): nobody knows how many machines there are or who has what, register, standard build, updates, licences, arrivals and departures, renewal by fifths

“We have about forty computers, some laptops, a few printers. Nobody knows exactly how many, or who has what. When an employee arrives, we look for a machine for three days; when they leave, we do not know what they hand back or which accounts they keep. Licences, we discover them the day a program shows a red banner. And everything breaks down in the same year. Where do we start?” With a register: one line per machine, kept up to date by a small program installed on each one. Everything else follows from it.

Symloop13 min read
Managing a fleet of computers knowing what you have, and who has itA register, a standard build, updates, licences counted, a renewal by fifthsIT FLEET · ALGERIA · 2027Managing a fleet of computersknowing what you have, and who has itA register, a standard build, updates, licences counted, arenewal by fifthsNOBODY KNOWShow many, or who has whatA REGISTERone line per machinesymloop.com

Short answer. Five things, in this order. A register: one line per machine, with its number, its user, its age, its system and the date of its last update, read automatically. A standard build per job, so that a machine is ready in two hours. Updates pushed every month. Licences counted: paid, installed, used. A renewal by fifths: with forty machines and a five-year cycle, eight a year, the oldest first. Add a procedure for arrivals and departures. The first inventory takes a week, and it says where to start.

This guide is for the manager of a company with twenty to two hundred machines that has no IT department, or one overloaded IT person, and for the founder based in France who wants a company that runs without them. The definitions quoted come from public sources: software asset management, mobile device management, the patch, disk encryption, the end of support for Windows 10. The fleet of forty machines, its breakdown and its ages are a constructed example. This guide gives no hardware prices and does not cover the rules on monitoring employees.

The first inventory: 19 machines out of 40 need an action

The figure shows forty machines on the day of the first inventory, one square per machine.

Figure 1 · Forty squares, one per machine, on the day of the first inventory. Twenty-one are in order; seven run a system that is no longer supported, five are late on updates, four have no known user, three laptops are not encrypted. Nineteen machines out of forty need an action. Fleet and breakdown are a constructed example.

What you find. The first inventory is rarely flattering. In the example, seven machines still run a system its publisher no longer supports: for Windows 10, support ended on October 14, 2025, except for machines enrolled in a paid extended security updates programme, itself limited in time. Five machines have received no fix for three months. Four have no known user: a cupboard, a former employee, a “spare” machine. Three laptops are not encrypted.

How it is read. A small program, the agent, is installed on each machine; it sends the register the model, the system, the installed software, the disk space and the date of the last update. A numbered label is stuck on the machine: the same number is in the register. By hand, in a spreadsheet, the register is only right on the day it is written. What it changes. You answer in a minute “how many machines, and who has what”, and you know which to deal with first. It is also the starting point of the upkeep described in the guide to managed IT.

«You cannot manage what you have not counted.»
01

Managing a fleet, in five layers

The accented layer is the first: the inventory.

Figure 2 · The accented layer is the first: the inventory, without which the other four work blind. The standard build makes a machine replaceable; updates and licences are followed machine by machine; security means a lost machine does not give up its data.

The standard build. For each job, accounts, sales, workshop, one configuration described once: the system, the software, the settings, the printers. A new or reinstalled machine is ready in two hours, and a broken machine is swapped for a loan machine without the employee losing the day. This assumes that working files do not live on the machine, but on a shared, backed-up space: see the guide to file sharing. Updates. A patch is data for modifying an existing software resource such as a program or a file, often to fix bugs and security vulnerabilities; pushed every month to every machine, it closes the known doors. The register flags the machines that are running late.

Licences. Software asset management is a business practice that involves managing and optimizing the purchase, deployment, maintenance, utilization and disposal of software within an organization. In practice, three numbers per program: paid, installed, used. The gap between the first two is a risk; the gap between the last two is money spent on nobody. Security. Disk encryption is a technology which protects information by converting it into code that cannot be deciphered easily: an encrypted laptop that is lost gives up nothing. Mobile device management is the administration of mobile devices, such as smartphones, tablet computers, and laptops, remotely, locking and wiping included. These are the points an auditor looks at: see the guide to the security audit.

02

Six moments in the life of a machine

The figure gives, for six moments, what is done and what is noted.

Figure 3 · Six moments, from purchase to end of life. Each has an action and a line in the register: it is the second column that is often missing, and it is what lets you answer “how many machines, and who has what”.

The second column. Many companies do the actions in the first column: they buy, assign, repair. What is missing is the line written each time. Without it, nobody knows whether the laptop of the salesperson who left in March was returned, or which machine is still under warranty. The breakdown. It is noted with its downtime: after a year, you see which models and which machines cost whole days, and replacement is decided on facts.

End of life. A machine does not leave the company with its data: the disk is wiped, the licences are taken back, and the register line is closed with the date and the destination, donation, resale or recycling. The data. What was on the machine must already be somewhere else; that is the rule in the guide to backups.

03

The age of the fleet: 12 machines out of 40 are over five years old

The figure sorts the forty machines by age, then shows what replacing eight machines a year gives.

Figure 4 · On the left, the age of the forty machines: twelve are over five years old. On the right, the number of machines over five years old at the start of each year, if the eight oldest are replaced every year: the backlog is absorbed in five years, with no black year. Invented ages; no hardware price is given.

The sum. Number of machines divided by the length of the cycle: forty machines, five years, eight machines a year. In the example, twelve machines are already over five years old. Replacing the eight oldest every year, twelve remain at the start of 2028, eleven in 2029, nine in 2030, five in 2031, and none in 2032. After that, eight machines reach five years every year, and eight are replaced.

Why five years. It is not a rule: it is a choice, to be made according to use. Two reference points help to set it. The system: Windows 11 requires features such as Trusted Platform Module (TPM) version 2.0, and its official support is limited to recent processors; a machine that is too old therefore stays on a system that is no longer supported. Breakdowns: the register tells you from what age they multiply in your company. The budget. By fifths, the spend is the same every year. This guide gives no price: multiply eight by the price of the machine you buy.

04

An employee arrives and leaves, in six steps

The first step is accented: the notice, five days before.

Figure 5 · The accented step is the first: the notice, five days before, without which the new employee waits three days for a machine. The next three prepare the arrival; the last two close the departure, on the day itself.

The arrival. The manager gives notice five days before, stating the job. The machine is prepared with the standard build, labelled, and the accounts are created: email, applications, rights on the folders. On the first morning, the employee signs the handover and works. Without notice, they wait, and someone lends them their login “for now”: that is how shared accounts are born.

The departure. The register gives the list of what the person holds: machine, phone, badge, accounts, licences. On the day itself, the equipment is returned, the accounts are closed or transferred, the mailbox is redirected according to the rule described in the guide to professional email, and the licences go back into stock. A former employee’s account left open is a door; a licence left assigned is an expense.

«A former employee’s account left open is a door; a licence left assigned is an expense.»
05

Six weeks to take back control, in 2027

Six weeks in the example, for forty machines.

  • What the manager receives: the register, with for each machine its user, its age and its condition; the list of gaps sorted by urgency; the number of licences paid, installed and used; the renewal plan over five years.
  • What the company no longer does: look for a machine on the morning of an arrival, discover an expired licence through a red banner, leave a departed employee’s account open, replace twenty machines in the same year.
  • What is measured: machines out of support, machines late on updates, unencrypted laptops, licences paid and not used, average age of the fleet, hours between an arrival and a machine being ready.
  • What Symloop does: the inventory and labelling, the register and its agent, the standard build, the monthly updates, the licence count, the arrival and departure procedure, and the renewal plan.
Figure 6 · Six weeks in the example, for forty machines. The accented period is the first: one week to inventory and label, after which you know where to start. Urgent items are handled from the second week; the rest becomes monthly upkeep. Indicative durations from a constructed example.

Week 1, the inventory. The agent is installed, the labels are stuck on, the first register comes out with the list of gaps. Week 2, the urgent items: systems out of support, unencrypted laptops, former employees’ accounts. Weeks 2 and 3, the standard build, tried on three machines.

Weeks 3 to 5, updates and licences. Weeks 5 and 6, arrivals, departures and the renewal plan. After that, it is upkeep: an hour a month to read the register, and one decision a year on the eight machines to replace. These durations hold for forty machines; allow more beyond a hundred, or over several sites.

How do you manage a fleet of company computers?
With five things, in order: a register kept up to date automatically, a standard build per job, monthly updates, licences counted, and a renewal by fifths. Everything starts from the register: you cannot manage what you have not counted.
How do you take an inventory of the computers?
By installing on each machine a small program that reads the model, the system, the software and the last update, and by sticking on the machine a label carrying the same number as in the register. A spreadsheet filled in by hand is only right on the day it is written.
What software do you need to manage a fleet?
Three functions are enough: an inventory fed by an agent, a tool that pushes updates and the standard build, and, for phones and laptops, remote administration. The choice depends on the size of the fleet; what matters is that the register updates itself.
How often should a company replace its computers?
There is no rule: it is a choice according to use. In our example, the cycle is five years, that is a fifth of the fleet a year. Two reference points: the system must still be supported by its publisher, and the register tells you at what age breakdowns multiply in your company.
What should we do with computers still on Windows 10?
Support for Windows 10 ended on October 14, 2025. Three routes: move to Windows 11 if the machine allows it, enrol in the paid extended security updates programme, which is limited in time, or replace the machine. In the meantime, these machines are dealt with first.
How do we know how many licences we really use?
By counting three numbers per program: the licences paid, the installations read by the agent, and the accounts actually used over the last three months. The gap between paid and installed is a risk; the gap between installed and used is a needless expense.
What should be done when an employee leaves the company?
Take from the register the list of what they hold, then, on the day itself: equipment returned, accounts closed or transferred, mailbox redirected, licences taken back. Without a register, something is always forgotten, generally an account.
What should be done if a laptop is lost or stolen?
If it is encrypted, the data cannot be read. You wipe it remotely if it is managed, change its user’s passwords, and note the loss in the register. If it was not encrypted, you have to assume that what it held has been read.
Do forty machines need a full-time IT person?
Not necessarily. Once the register and the standard build are in place, routine upkeep takes a few hours a month, given to someone in-house or to a provider. What matters is that someone is explicitly in charge of it.
How long does it take to put a fleet of forty machines in order?
Six weeks in our example: one to inventory and label, one for the urgent items, two for the standard build, three for updates and licences, two for the procedures and the renewal plan, partly in parallel.
Tell us how many machines you think you have, and over how many sites: we do the first inventory, and within a week you will know what you really have, and where to start

Nobody knows who has what, licences discovered through a red banner, former employees’ accounts still open, or a founder in France who wants a company that runs without them: we keep the register and everything that follows from it

Inventory, register, standard build, updates, licences, arrivals and departures, renewal plan. We work from Algiers and Sétif, in French, Arabic and English.