Five decisions to make before your next HP refresh
A refresh goes wrong at the beginning, not the end. The five decisions below are the ones we see teams make halfway through a rollout — usually under pressure, usually at a cost. Make them before the purchase order and the rest is logistics.
1. Support term and options
Decide how long you will actually keep each device class, then buy that much coverage — not the default. A device on a three-year cycle gets 3-year onsite HP Support Services; a class you expect to stretch gets 4-year up front, because a post-warranty extension later is a different, more limited product.1 Add Defective Media Retention anywhere a drive can hold personal or case data — which, for a human-services, healthcare or K-12 fleet, is everywhere. And decide now whether downtime has a per-hour cost that justifies HP's Premium or Premium+ support tiers, with predictive detection and priority parts.2
Do it now because: HP Support Services coverage starts on the hardware purchase date. Attaching at quote is cheap; retrofitting is not.
2. Who gets Wolf Protect & Trace
HP Wolf Protect & Trace lets you find, lock and erase a notebook even when it is powered off or will not boot.2 It is not a fleet-wide default — it is for the devices that leave the building: caseworkers, inspectors, field engineers, anyone whose laptop lives in a car. Two practical constraints shape the decision: it is available on select HP commercial G10 and later laptops and mobile workstations, and each device must be registered in HP Workforce Central.2 Pick the models with it in mind, and have the registration done at staging so protection is live before the device is handed over — not on a to-do list after.
Do it now because: eligibility is decided when you choose the model, and registration is trivial at the bench and painful in the field.
3. Image strategy
Three options, and a large program usually needs two of them. A golden image built and applied at a staging bench is the right answer for sites without IT staff — the device arrives ready at the desk. A customer-validated build (a .WIM your own team signs off) applied at the distributor's imaging facility suits sites that have standards but not capacity. Windows Autopilot suits organisations that have already moved to cloud-native management and want devices to self-provision on first sign-in. Decide per site type, and validate the image on real hardware before the first wave — an image that loops on one model will stall an entire county. If you license HP Workforce Experience Platform, build the HP Insights Agent into the image so every device reports from first boot.5
Do it now because: imaging path determines who ships what to where, and that is the whole delivery plan.
4. Delivery model
Sites with their own technicians can take delivery to the door — multi-pack shipments, their staff deploys. Sites without need delivery to the desk — device set up, old device recovered, in one visit. Most statewide or multi-campus programs are a mix, and the largest sites are usually worth an onsite assist day regardless: delivering 300 devices and recovering 300 in the same trip is faster and cleaner than any return kit.3 Decide the model per site before ordering, because it changes the packaging, the carrier arrangement and the receipt process.
Do it now because: "how do we get the old ones back" is the question that stalls rollouts in month three.
5. The end-of-life plan
The refresh is not finished when the new device is on the desk; it is finished when the old device is sanitized and the certificate is filed. Decide up front: return kit type (multi-pack versus one-for-one), the carrier account, the chain-of-custody documentation, the sanitization standard — NIST SP 800-88, with destruction evidence retained by you4 — and whether retired devices are bought out, remarketed or recycled. If you chose DMR in decision 1, the failed drives from the last three years are part of this batch too.
Do it now because: retired devices holding data are a liability until the certificate exists, and the residual value of a device drops every month it sits in a closet.
And one more: where the record lives
Every decision above produces something that needs to be tracked per device: an HP Support Services expiration, a Protect & Trace enrollment, an image version, a delivery receipt, a sanitization certificate. If those live in five spreadsheets, the next refresh starts from zero. Every device Milestone ships gets a single record in VAR360 — order, serial, coverage, delivery, return — which is the same record the next refresh is planned from. Decide where your record lives before the first wave, and the sixth decision makes the other five stick.
Key takeaways
- Buy coverage for how long you will keep the device — 3- or 4-year onsite with DMR — and attach it at purchase.
- Protect & Trace goes on the devices that leave the building; choose eligible models and register at staging.
- Pick the image path and delivery model per site type before ordering; validate the image on real hardware.
- Plan end of life — return kits, custody chain, NIST 800-88, buyout or remarketing — before the first wave ships.
Sources
- Milestone HP Support Services quotations for a state agency notebook fleet, June 2026 — HP 3-year and 4-year Onsite DMR Notebook Support; HP 1-year Post Warranty Onsite DMR Notebook Support (NASPO ValuePoint contract vehicle).
- HP, Workforce Experience Platform — Solution Brief, 4AA8-4877ENW, July 2025 — sections on HP PC and Print Support Services (Essential, Premium, Premium+) and HP Protect and Trace with Wolf Connect.
- Milestone rollout workbook and status decks, August–September 2026.
- NIST Special Publication 800-88 Rev. 1, Guidelines for Media Sanitization.
- HP, HP Workforce Experience Platform — Datasheet, 4AA8-4726ENW, November 2025 — plans, Smart PC Refresh, warranty status, HP Insights Agent and system requirements.
