Prepare
Stage a consistent collection package and destination structure before the device reaches the technician.
GraphPilot collection workflow
HashPilot
A repeatable way to collect Windows Autopilot hardware-hash data, preserve device context, and return cleaner intake files from the bench or the field.
HashPilot is included inside GraphPilot. It focuses on the first handoff in the Autopilot workflow: getting a trustworthy device record back from the technician before merge, review, or upload begins.
Why it exists
The collection step is where clean data starts.
Hardware-hash projects often become inconsistent before an administrator ever sees the CSV. Different technicians use different commands, filenames, folders, and handoff notes. HashPilot turns those choices into a prepared workflow.
Collect
Capture the hardware identity and useful device context through a repeatable Windows-side process.
Return
Hand the administrator a predictable output that is easier to identify, merge, validate, and audit.
Operational fit
Designed for real handoffs.
MSP staging work
Prepare collection media once, use a recognizable workflow across customer devices, and reduce the cleanup needed after files return.
Distributed technicians
Give remote or field staff a narrower process so the endpoint administrator does not have to reconstruct what happened later.
Bench intake
Keep serial number, source file, and collected device context together while multiple systems are being processed.
GraphPilot handoff
Move collected records into merge, normalization, review, and upload-preparation steps without starting over in a spreadsheet.
Boundaries
What HashPilot does—and what it does not do.
| HashPilot helps with | You still control |
|---|---|
| Preparing the collection workflow and expected output | Which devices are authorized for collection |
| Reducing inconsistent filenames and technician handoffs | Customer consent, chain of custody, and local handling policy |
| Keeping device data ready for GraphPilot review | Tenant credentials, Intune permissions, and the final upload action |
| Working locally on Windows | Storage, transport, retention, and secure deletion of collected files |
Local-first: HashPilot does not require an x=mas2 cloud data service. The operator remains responsible for the files and for any Microsoft authentication or upload action.
Common questions
HashPilot FAQ
Is HashPilot sold separately?
No. HashPilot is a named collection workflow included inside GraphPilot.
Does it replace Microsoft’s hardware-hash requirements?
No. It helps operators collect and hand off the data more consistently. The resulting records still need to meet Microsoft’s current Autopilot import requirements.
Does it automatically upload devices to a tenant?
No. Collection and upload are separate decisions. GraphPilot can prepare the workflow, while the administrator controls authentication, permissions, tenant selection, and the upload action.
Where should I start if I already have CSV files?
Start with the Autopilot CSV validation guide, then use GraphPilot’s merge and review workflow if the records came from multiple sources.