DriveErase Enterprise and Audit support compatible Windows Server environments. Standard and Pro do not provide licensed operation on Windows Server.
Sanitizing storage on a server requires additional preparation because the computer may be running services, hosting virtual machines, providing shared storage, or participating in a cluster. The DriveErase workflow requires a restart into the Privileged Execution Environment, so any workloads depending on the server must be considered before the operation begins.
Preparing the server
Schedule an appropriate maintenance window and confirm that the selected storage devices are no longer needed by active workloads.
For example, a server being retired might contain several drives that belong to a RAID array. Before sanitization, ensure that the relevant data has been backed up or migrated and that the server is no longer required for production services.
If the server participates in clustering, replication, or failover, review how taking it offline will affect other systems. Coordinate with the responsible administrators before changing the storage configuration.
Remote access also deserves attention. Ordinary Windows Remote Desktop sessions will not necessarily remain available after the system restarts into the Privileged Execution Environment. Make sure a supported local console or out-of-band management interface is available to observe the operation and completion screen.
Storage controllers and RAID arrays
Servers commonly use RAID controllers, SAS HBAs, hot-swap enclosures, and specialized storage interfaces. These components can change how individual devices appear in DriveErase.
A RAID controller might expose one logical volume representing several physical disks. Overwriting that logical volume does not automatically establish that every individual member disk, spare drive, controller cache, or previously removed member has been sanitized.
When individual physical drives are being retired, identify and expose them separately through an appropriate supported controller configuration whenever possible.
Record the drive’s serial number and physical bay location, particularly when several identical drives are installed.
System disks and shared storage
The disk containing the active Windows Server installation cannot be selected for erasure from that running installation. To sanitize it, connect the device as a non-system target to another compatible DriveErase computer.
Be especially careful with shared storage. A device presented through a storage area network or multipath configuration may be accessible from more than one server. Its identity and ownership must be confirmed before any destructive operation.
Completing the operation
Review the individual results after execution. Enterprise and Audit can produce certified data sanitization reports, which are useful for documenting server retirement or storage replacement.
Where physical devices were removed from an enclosure, retain the serial-number and bay mapping alongside the reports. This helps establish which disk corresponds to each result.
A completed server maintenance task does not necessarily mean every storage device was successfully sanitized. Examine the actual erasure, verification, and compliance information before releasing any equipment.
