Project context
When an IT administrator leaves or changes role, the main risk is often that device access, credentials, configuration, backups and business dependencies exist only in personal knowledge. The project therefore focused first on making the environment identifiable, accessible, backed up and explainable before deciding what to remediate. Directory services, virtualisation, firewalls, switches/APs, NAS, backup, cloud platforms, domains/certificates and privileged accounts were included in the handover boundary.
Objectives
- Create a verifiable inventory of IT assets, administrative entry points, owners and critical dependencies.
- Close leaver-owned personal access first; change service accounts, scripts and scheduled-task credentials only after dependency checks.
- Rebuild topology, IP/VLAN records, configuration backups and restore evidence so the environment can be handed over.
Scope baseline
Directory/DNS, virtualisation, physical servers, NAS and file-service inventory.
Firewall, switching, AP, remote-access, cloud, domain and certificate administration review.
Privileged accounts, responsible owners, bound phone/email, MFA and recovery path verification.
Configuration backups, business dependencies, restore tests, risk register and managed support baseline.
Implementation and control
- 01
Freeze non-essential changes and capture the current state of networks, accounts, servers, virtualisation and backups.
- 02
Confirm each asset and admin entry point, moving critical accounts from personal ownership to an enterprise-controlled owner.
- 03
Disable or constrain leaver personal accounts first; service accounts, scripts, scheduled tasks and production credentials are changed only after dependency review.
- 04
Back up key firewall, switch and virtualisation configurations, document logical topology and application dependencies, and record external mappings and remote-access paths.
- 05
Use ordinary files, test instances or other low-risk objects for restore validation, then build a prioritised remediation and ongoing review plan.
Risk and change control
Changing every administrator password immediately can break service accounts, scheduled tasks or scripts; dependencies come first.
“Can log in” is not enough—ownership, MFA, recovery email/phone and emergency recovery path must also be known.
A green backup console is not enough for a reliable handover; restore access and a tested recovery method are required.
Acceptance and handover
- Core administrative entry points, owners and recovery methods are under enterprise control.
- Leaver personal access is closed and service-account dependencies are documented.
- Topology, IP/VLAN, key configurations and backup locations can be reviewed by another engineer.
- A risk register, remediation priority and managed support baseline are in place for future changes.

