Français
English
Español
Deutsch
NorskPractical guide
Build an IT estate maintenance plan
Turn an equipment list into priorities, scheduled work and evidence of completion.
Practical guide
A case to prepare your project
An office has mixed-age computers, a file server and a shared printer. Server failure affects everyone, while the spare workstation has never been tested. Priorities should reflect those dependencies.
Illustrative scenario, to adapt to your organisation.Prepare and perform the checks
Qualify every asset
Record owner, purpose, version, support lifecycle, backup and dependencies. Do not store passwords in the inventory.
Build the schedule
Assign frequency by risk, an owner and a change window. Include a pilot, communication and rollback.
Close the loop
Verify the service with its user, update inventory and record exceptions. Review recurring issues at service meetings.
A reusable acceptance checklist
Agree thresholds, owners and test data before testing. Retain dated results, exceptions and the acceptance decision.
| Check | Expected result | Evidence to retain |
|---|---|---|
| Reliable inventory | Critical assets have an owner, version and identified dependencies. | Verified, dated asset record. |
| Controlled patching | The pilot works and rollback is documented before broad rollout. | Change ticket and user test. |
| Usable backup | A file or service can be restored into a verification environment. | Restore report, not only a copy log. |
| Traceable support | An incident has an owner, priority and verified closure. | Ticket and confirmation of recovery. |
Decide using evidence
Prioritise risks to multiple users or irreplaceable data. Patch rates and ticket counts need a defined period, covered estate and exceptions. Every indicator should support a decision.
Standards and reading
References checked on .
Relevant ISO standards
- ISO/IEC 20000-1:2018 (+ Amd 1:2024)
Organise service management and improvement.
- ISO/IEC 27002:2022
Select asset protection measures.
These standards help define scope and expected evidence. Citing them does not certify Salott-IT or establish your project’s conformity. A dedicated assessment is required. Include applicable amendments when scoping the engagement.
Technical documentation
Reference books
- The Practice of System and Network Administration · Volume 1, 3rd edition
Thomas A. Limoncelli, Christina J. Hogan & Strata R. Chalup · Addison-Wesley · 2016
Original synthesis based on official summaries, open documentation and publishers’ public descriptions or contents. Books are selected references, not a universal ranking. Copyrighted book and standards text is not reproduced.
Start with your actual situation.
Scope, responsibilities, timing and acceptance criteria will be defined in the proposal.