Solutions
Server Refresh & Migration
A refresh is a sequencing problem — end-of-support dates, license transfers, rack space, disposal. We quote the replacement fleet, stage and image it, and take the old kit back out under your disposition policy.
- Driven by
- End-of-support dates, not purchase age
- Staging
- Configured, imaged, racked and labeled
- Removal
- Coordinated under your disposition policy
- Boundary
- We supply and stage; you decide what gets destroyed
Refresh programs fail on the calendar, not on the specification
Choosing replacement hardware is the easy half. The hard half is sequencing: which systems fall off vendor support first, which licenses transfer to new hardware and which have to be repurchased, whether the rack has space for old and new at the same time or whether every swap is a like-for-like removal, and what happens to the equipment coming out. Uniqcli quotes the replacement fleet against the end-of-support dates that actually drive the program, stages and images it so installation is a lift rather than a build, and coordinates removal of the old estate under the disposition policy your organization already has.
The order that keeps a refresh on schedule
Every one of these is a date or a decision, and each one has stalled a program somewhere.
- End-of-support dates per platform, oldest first — that is the real backlog
- License transfer checked before the hardware is ordered, not after
- Rack space confirmed: parallel install, or strict like-for-like swap
- Long-lead components identified and quoted with a real date
- Staging: configured, imaged, firmware-levelled, racked and labeled
- Removal booked against your disposition policy, with the property record updated
Replacement fleet and the parts that populate it
Verified priced lines on this hub catalog. Naming a manufacturer describes the market, not a Uniqcli partnership or endorsement.
Server platforms
Lenovo anchors the hub server line by a wide margin, with Supermicro where a build-to-spec platform is the better answer. Quoted per role rather than as a single standard, because a virtualization host and a file server are not the same purchase.
Memory and storage
Micron and Kingston memory, and Western Digital storage, quoted as explicit per-host lines. Refresh programs that carry over a base configuration are the ones that discover a memory shortfall after the hosts are racked.
Lifecycle checking
Use the end-of-life checker to confirm which platforms are genuinely past or approaching vendor support before you build the replacement list, so the sequence is driven by dates rather than by asset age.
Two server lines live on their own storefronts
Not every server brand is carried on this catalog. HPE and Dell are sold through dedicated Uniqcli storefronts with their own inventory and pricing, so if your standard is written around either of those platforms the honest route is straight there rather than through a hub quote that would have to be re-sourced.
For everything else — the platforms above, the memory and storage that populate them, and the racking and power around them — the hub is the right place, and it can all go on one document. Where a refresh spans both, we will say which lines belong where instead of quietly quoting around the gap.
- HPE and Dell platforms: quoted through their dedicated Uniqcli storefronts on the same document
- Hub catalog: Lenovo, Supermicro, memory, storage, racking and power
- Country of origin recorded per line; NDAA §889 screening before the quote
Server refresh questions
How do we decide what to refresh first?
By vendor support date rather than by asset age. A four-year-old platform still under support is a lower risk than a three-year-old one that fell off it last quarter. Our end-of-life checker will confirm the dates for the platforms it covers, and anything it does not cover we will check on request.
Do our licenses move to the new hardware?
Sometimes, and it depends entirely on the license type and the agreement. It is worth confirming before the hardware is ordered, because a license that does not transfer turns a hardware line into a hardware-plus-licensing line. We will quote both once you know which case applies.
What happens to the old servers?
We coordinate removal alongside delivery. What happens next — wipe standard, resale, destruction, property-book removal — is a decision your organization makes and documents. We work to the policy you give us and do not substitute our own.
Can the new servers arrive ready to rack?
Yes. Configured to your build sheet, firmware-levelled, imaged, racked and labeled to your elevation. That turns install day into a lift-and-connect rather than an afternoon of setup in a cold aisle.
The solutions atlas
Every solution, one accountable partner.
UniQ platforms
By technology
By customer
- TAA & NDAA-889 Compliance Screening
- CMMC & CUI Solutions
- Federal & DoD
- State, Local & Education
- Healthcare
- Enterprise
- Rapid Procurement & GPC Buys
- Multi-Vendor Integration Projects
- eProcurement & Custom Catalogs
- FISMA Modernization
- CJIS-Compliant Justice Cloud & Local AI
- Federal Storage Modernization
- Government ERP & Business Systems Infrastructure
- Managed Procurement
- Secure AV & Conferencing
- Fiber Network Infrastructure
- Satellite & Resilient Connectivity
- Wavelength & Optical Transport
- Decentralized Data Centers
- Data Center Design & Build
Send the estate and the support dates
We return a sequenced replacement plan with lead times, staging scope and removal coordinated against your disposition policy.