sap-dormant-clientslisted

# Dormant Client Assessment & Retirement Every client you keep must be secured, patched, user-maintained and audited — including the ones nobody uses. Removing an unused client **reduces maintenance effort and increases security**, because unused clients are where forgotten standard users (`SAP*`, `DDIC`, `EARLYWATCH`) keep their well-known passwords. [G, RM] > **Guardrail — client deletion is irreversible in practice.** > - **Never delete on a hunch.** Dormancy is a *conclusion from evidence* (§2). "Nobody mentions it" is not > evidence. Present the evidence table and get explicit sign-off before §4. > - **Client 001 is productive in some products.** SAP Solution Manager and BW commonly run production in > **001**. Confirm what the system *is* before assuming 001 is a leftover. [G, RM] > - **Always run SCC5 in test mode first**, and always in **background** for a large client. [G, RM] > - **PRD systems: typed confirmation naming the SID and client number**, and a current backup you have > verified is restorable — see [sap-backup-recovery](../sap-backup-recovery/SKILL.md). Recovery of a > wrongly deleted client is a restore, not an undo (SAP Note 31496). [G, REC] > - **Deleting rows does not free disk.** Space returns only after a reorganization — §6. > - Never re-create client **066** after removing it. [G, RM] Verification legend: **[V]** verified during authoring · **[G]** cited to an SAP Note or guide. --- ## 1. The three install-time clients | Client | What