A used workstation needs a purpose before it needs an upgrade
Published October 5, 2026 ยท Independent editorial guide
Before buying RAM for a donated workstation, write down the one job you need it to do. A machine destined for a static exhibit has different requirements from one that must run a particular legacy program. For the latter, identify the program, processor architecture and operating system first. Reaching a boot prompt answers only the first of several questions.
The IBM RS/6000 Model 240 page is an example of the site's historical equipment information. Its specifications and the site's old sales material are not a current offer, warranty or indication that software remains supported.
Write down the intended workload
Identify the program, operating system, processor architecture, memory requirement and required peripherals. An application built for a different architecture will not become compatible merely because the new machine has more memory. Check the relevant vendor documentation and licensing conditions for the exact configuration rather than relying on a model family's reputation.
For research use, define a small representative workload and a way to repeat it. The EEG benchmark documentation guide explains the value of recording the environment alongside the analysis. It does not imply that a particular legacy workstation can run modern EEG software.
Inspect the whole system
Check the storage, connectors, power requirements, cooling and physical condition before planning a workload. Ask what is missing and which replacement parts are realistically available. Use qualified assistance for electrical faults or uncertain safety conditions. Keep a record of the inspected configuration, because a model number alone does not describe every installed component.
Handle existing data deliberately
Confirm ownership and permission before accessing a previous owner's files. The NIST media-sanitization guidance treats sanitization as making access to target data infeasible for a specified level of effort. Choose a suitable, verifiable method for the particular media and requirements; deleting a folder is not a reliable substitute. Preserve any data you are authorized and required to retain before beginning an irreversible operation.
Choose a supportable role
An unsupported system should not casually become a public-facing service or a device holding sensitive credentials. Document the limits of the proposed environment and have the responsible maintainer assess its isolation and access arrangements. The small-group accounts and backup checklist helps connect equipment decisions to information ownership and recovery.
Finish with a decision sheet: intended purpose, tested configuration, unresolved problems, support status and recovery plan. Reuse is most defensible when the machine has a bounded job and the remaining limitations are understood by the people relying on it.
Keep the identifier with the equipment
A photographed label and a complete model identifier are more useful than a guess based on appearance. The hydration-pack archive offers archived design details for another kind of reused equipment. Record the condition and source of a specification before deciding whether reuse is practical.
Reference: CISA Secure Our World. .


