A campus refresh moves hundreds of machines in a few weeks, usually during a break, usually with a small team. The data on them ranges from student records to unpublished research, and the machines themselves often have years of useful life left.
Data Sanitization Pro fits that shape. PXE boot starts erasure across a whole lab from one console, with no agent to deploy and no need to touch each machine individually. Hardware diagnostics run in the same pass, so you know which machines are worth redeploying and which are genuinely finished.
Every drive produces a certificate. When a department asks what happened to the machine a research group used, there is an answer.
Identify, Erase, Verify, Report, Then Decide
A lab of a hundred machines runs the same five steps as one. PXE is what makes the count stop mattering.
- 01
Identify
Machines pick up the erasure environment at boot and report what media they hold. Nothing is installed on them.
- 02
Erase
Started for the whole room from one console, running overnight while the building is empty.
- 03
Verify
Every machine reads its own medium back and records the result before it reports finished.
- 04
Report
One certificate per machine, collected centrally, so the morning after is a list rather than a walk round the room.
- 05
Redeploy, Donate or Recycle
The diagnostic grade says which machines are worth keeping. The certificate is what lets them leave.
A Whole Lab from One Console
PXE boot sends the erasure environment over the network to every machine in the room at once. Nobody walks between desks with a USB stick, and the job runs overnight while the building is empty.

Keep What Still Works
The diagnostic pass reports drive health, memory, battery and thermal behaviour. Machines that pass go back into service or to a donation programme; only the ones that genuinely fail get recycled.

- 0 agentsTo Install on Any Machine
PXE hands the erasure environment to each machine at boot. Nothing is installed on the computers being erased, so nothing has to be removed afterwards.
- 25 methodsErasure Standards Built In
NIST SP 800-88 Clear and Purge, IEEE 2883, DoD 5220.22-M, BSI, DPDP and twenty more. The software issues what the medium actually supports.
- 12 checksIn the Hardware Report
SMART attributes, reallocated sectors, power-on hours, read and write throughput, memory, battery and thermals, graded against thresholds you set.
- 100%Of Erased Machines Report Back
A lab wiped overnight is only worth anything if you can prove it in the morning. Every machine finishes with its own certificate.
Frequently Asked Questions
Can this run overnight without staff present?
Yes. PXE-booted erasure runs unattended across the machines you target and reports results when it finishes. Most institutions run it during a break or overnight.
Does it work on Chromebooks and mixed fleets?
It boots independently of the installed operating system, so mixed Windows, Linux and Chrome fleets are handled the same way. Media type determines the method, not the OS.
What about machines being donated?
Erase and certify first, then redeploy. The certificate is what protects the institution if a donated machine is later found to hold data — and the diagnostic grade tells you whether it is worth donating at all.
Is there pricing for education?
Licences are per device erased, which suits a refresh cycle better than per-seat licensing. Talk to us about volumes and we will size it against your refresh plan.
Plan Your Next Refresh
Tell us how many machines and what window you have, and we will size the job.

