Skip to content

Latest commit

 

History

History
36 lines (28 loc) · 1.65 KB

decommissioning.md

File metadata and controls

36 lines (28 loc) · 1.65 KB

Checklist for decommissioning library machines:

For any server, first:

  • Disconnect server from network for 30 days.

Note: This allows time for the unexpected - if someone really was using the server, they can tell us and we can bring it back.

If the 30 days go by and nobody complains, then decommission the server:

For Physical Servers:

  1. Remove from rack, Store in Firestone rack for 6 months.
  2. After 6 months, low-level format the disk or pull out all disk drives and send to Surplus for shredding.
  3. Record and send hardware to Surplus.

For Virtual Servers:

  1. Copy VM files to archival disk.
  2. Delete from VM environment.

Once the server is decommissioned, remove all traces of it:

  1. Remove Host database entry.
  1. Remove from any monitoring services (IE: Nagios, Datadog, etc).
  2. Revoke any TLS certificates (if applicable*)
  3. Remove all references from load balancers, inventory, and variables (if applicable).
  4. Remove from firewall rules (if applicable).
  • Send a note to lsupport@
  • Subject: Hardware Firewall Change - oldvm.princeton.edu
  • Body: Please delete all rules for
  1. Remove from BigFix.
  2. Remove from inventory spreadsheet.
  3. Remove from backup solutions (Cohesity, Veeam).
  4. Remove computer account from domain (if joined).

*The "if applicable" note means that these steps should only be taken if the application is being permenantly retired/deleted, not if we are inserting a new/different VM in its place.