Windows Server 2016 End of Support: Migrate the OS and Refresh the Hardware Together
Windows Server 2016 reaches end of extended support on January 12, 2027 — after that there are no more security updates without paid Extended Security Updates (ESU). The cleanest path is to migrate to Windows Server 2022 or 2025 on a current HPE ProLiant Gen12 server rather than re-licensing aging Gen9/Gen10 hardware. Uniqcli, an authorized HPE partner, plans the OS migration, hardware refresh, right-sizing, and licensing as one project on TAA-compliant, federally buyable terms.
Signs it’s time to refresh
- Windows Server 2016 reaches end of extended support on January 12, 2027 — no further security patches without paid ESU
- Your workloads still run on ProLiant Gen9 or early Gen10, which are past or nearing hardware end-of-support and out of standard warranty
- You are paying for a third year of Windows Server 2016 ESU (or about to start one) and the per-core cost now rivals new hardware
- Newer Windows Server features, TPM 2.0 / Secured-core, and current SQL Server versions are gated behind a supported OS and platform
- Federal STIG and FedRAMP requirements flag the unsupported OS as a finding you can no longer remediate with patches
- Per-core Windows Server licensing on old, high-core-count CPUs is overspending versus right-sized modern cores
Your refresh planning checklist
Work these in order, or send us where you are and we’ll build the plan with you.
- 1
Inventory every Windows Server 2016 instance and its host hardware
List each VM and physical host, the ProLiant generation underneath, roles (AD, file, SQL, Hyper-V, app), and which are domain controllers. You cannot plan a migration you have not counted.
- 2
Classify each workload: migrate, consolidate, retire, or re-platform
Separate keep-as-VM workloads from candidates for consolidation onto fewer Gen12 hosts or a move to GreenLake/Azure. Retiring dead servers cuts both hardware and license cost.
- 3
Choose the target OS — Windows Server 2022 or 2025 — per workload
Confirm application and SQL Server vendor support matrices. Server 2025 buys the longest runway; 2022 is the conservative, broadly certified choice for legacy apps.
- 4
Right-size cores and memory before you buy or license
Old servers were often grossly over-provisioned. Size Gen12 SKUs to actual utilization so you do not over-buy per-core Windows Server and SQL licensing on cores you will never use.
- 5
Map the licensing path: new licenses, Software Assurance, or CSP
Decide whether to bring existing licenses with Software Assurance, buy new per-core licenses, or move to subscription. Datacenter vs Standard hinges on VM density per host.
- 6
Sequence the migration to protect Active Directory and dependencies
Stand up new domain controllers and transfer FSMO roles before decommissioning old ones; migrate file/print and app servers in dependency order to avoid outages.
- 7
Plan cutover, validation, and decommissioning with a rollback window
Schedule maintenance windows, validate each workload on the new platform, keep the old host recoverable until sign-off, then wipe and retire per your data-disposal policy.
A typical refresh timeline
Assessment (weeks 1-3)
Inventory all Server 2016 instances and host hardware, classify workloads, confirm OS and app support matrices, and capture utilization for right-sizing.
Design and quote (weeks 3-6)
Size ProLiant Gen12 configs, finalize Windows Server 2022/2025 and SQL licensing, and issue a TAA-compliant quote via GPC, SAP, FAR, or GPC.
Procure and stage (weeks 6-12)
Order hardware, factory-integrate where possible, rack and image new Gen12 hosts, and build the target OS and AD environment in parallel with production.
Migrate and validate (weeks 12-18)
Move workloads in dependency order, transfer AD roles, validate each application, and run both environments side by side through a defined cutover window.
Decommission (weeks 18-20)
Confirm sign-off, retire and securely wipe legacy Gen9/Gen10 hardware, and close out warranty and license records.
Why run the refresh with Uniqcli
OS and hardware refresh planned as one project
We scope the Windows Server 2016 migration alongside the ProLiant Gen12 refresh and licensing so you are not solving the OS deadline and the hardware deadline separately.
Right-sizing that cuts license overspend
Per-core Windows Server and SQL licensing makes core count expensive. We size modern hosts to real utilization so you stop paying for cores you inherited from 2016-era servers.
Authorized HPE partner, TAA-compliant
Genuine HPE ProLiant Gen12 on TAA-compliant terms, buyable through GSA, SAP/FAR channels, and GPC — built for federal, DoD, SLED, and healthcare procurement.
Licensing guidance, not guesswork
We walk through Standard vs Datacenter, Software Assurance, ESU bridges, and CSP so the licensing model matches your VM density and budget cycle.
Refresh planning — FAQs
When does Windows Server 2016 reach end of support?
Extended support for Windows Server 2016 ends on January 12, 2027. After that date, Microsoft no longer ships free security updates. You can buy Extended Security Updates (ESU) for up to three additional years, but ESU is a paid bridge, not a long-term fix.
Do I have to replace the hardware to migrate the OS?
Not strictly, but it usually makes sense to. Most Server 2016 workloads run on ProLiant Gen9 or early Gen10 that is already past or near hardware end-of-support. Migrating the OS onto current Gen12 hardware solves both deadlines at once and avoids re-investing in platforms you will replace soon anyway.
Should I move to Windows Server 2022 or Windows Server 2025?
It depends on the workload. Windows Server 2025 gives the longest support runway and newest features, while 2022 is the conservative choice that is broadly certified for legacy applications. We confirm each application and SQL Server version against vendor support matrices before recommending a target.
How does right-sizing reduce my licensing cost?
Windows Server and SQL Server are licensed per physical core, so over-provisioned old servers carry license cost you do not need. By sizing Gen12 hosts to actual utilization, you license fewer cores and often consolidate onto fewer, denser hosts — which can also shift the math between Standard and Datacenter editions.
Can I buy this through federal contract vehicles?
Yes. Uniqcli is an authorized HPE partner and quotes TAA-compliant ProLiant Gen12 hardware and licensing through GSA, SAP/FAR channels, and the Government Purchase Card. This supports federal, DoD, SLED, and healthcare procurement requirements.
What happens to Active Directory during the migration?
Active Directory is migrated carefully: we stand up new domain controllers, transfer FSMO roles, and validate replication before decommissioning the old controllers. Migrating in the right dependency order prevents authentication and DNS outages during cutover.
Build your HPE bill of materials.
Send us the requirement, the project, or an existing quote to beat. We come back with a validated, TAA-compliant HPE configuration and a real price, often below list.
connect [at] getuniqcli.com · Chicago, IL