“Two terabytes of DDR5” describes capacity. It does not tell a buyer how many modules are available, which part numbers they carry or whether they have the same condition. For an upgrade, it also leaves the installed layout unresolved.
A useful inventory starts with individual module records and then produces a summary. That approach preserves the details needed to investigate discrepancies instead of hiding them inside a fleet-wide total.
Start with the system’s reported information
On Windows, Microsoft’s Win32_PhysicalMemory documentation identifies fields including manufacturer, part number, serial number, device locator and capacity. Capacity is expressed in bytes, and several properties are populated from SMBIOS information. These fields provide a starting point for an inventory, rather than an independent inspection of each module.
On Linux systems where it is available, dmidecode can display the firmware’s hardware descriptions. Its manual warns that it reads DMI table information rather than scanning the actual hardware, so reported data can be unreliable. Read the dmidecode manual.
Keep the original export alongside your working spreadsheet. Add the collection date, system asset identifier and collection method. If a field is missing, label it unknown instead of copying a value from another module that looks similar.
Three groups of information
Manufacturer, complete part number and serial number where available.
Source server, reported slot and collection date.
Inventory source, label verification, condition and documented test history.
Reconcile software records with physical evidence
Before a sale or hardware change, resolve incomplete or conflicting entries. During approved maintenance or decommissioning, compare the recorded part numbers with module labels and retain clear photographs where useful. Follow the server’s handling procedure when accessing installed memory.
Keep the full part-number suffix. Record module type and rated specification from manufacturer documentation, rather than inferring them from capacity alone. Where a label and a software export disagree, retain both observations and investigate the difference before treating either as a confirmed specification.
Use separate fields for the module’s rated speed and the speed reported by the system. Include the units and source. That prevents an operating configuration from silently replacing the product specification in the inventory.
Likewise, separate installed inventory from the quantity available for sale. Modules reserved as spares, still in service or awaiting a condition check should have an explicit status. A technically accurate export can still overstate what is ready to ship.
Build a summary without losing the detail
For a surplus quotation, group verified modules by complete part number and condition, then provide the quantity in each group. Retain serial-level records internally where available so discrepancies can be traced after packing or inspection.
For an upgrade, retain the server and slot mapping and compare the proposed configuration with the platform’s population rules. Knowing what is installed supports that check; it does not itself certify compatibility with additional memory.
Record testing separately from identification. A software inventory entry shows what the system reports, not that a module passed a diagnostic procedure. Use descriptions such as tested, untested or removed during troubleshooting only when they accurately reflect the evidence, and attach the relevant date and method.
Before handing off the file, reconcile row counts, grouped quantities and capacity totals. Have a second reviewer check exceptions rather than simply confirming the grand total. Keep internal asset references in your master record and share only the details needed for the external quotation.
A useful inventory lets someone trace a summary back to the modules behind it.
Prepared October 16, 2026 using Microsoft’s Win32_PhysicalMemory reference and the dmidecode manual linked above. The record structure and handoff recommendations are Ocitech’s editorial guidance. No inventory command has been run against customer servers, and no testing results are implied.