Windows Server 2016 reaches end of support on 12 January 2027 — five months out, and part of the same lift as the database.
Treated as a separate infrastructure ticket, it lands after the ERP upgrade has already been scoped against the wrong OS.
Who it binds
- Any Sage X3 estate on Windows Server 2016. Extended Security Updates are available via Azure Arc.
- Windows Server 2019 runs to January 2029, so it is a viable intermediate step only if the X3 target version supports it.
What it actually demands
- Sage X3 through 2022 R3 (12.0.32) requires Windows Server 2019.
- 2023 R1 (12.0.33) through 2024 R2 (12.0.36) requires Windows Server 2022.
- 2025 R1 (12.0.37) and above requires Windows Server 2025.
- Linux estates: RHEL or Oracle Linux 7, 8 or 9 depending on X3 version.
The OS floor moves with the X3 version, in the same way the SQL floor does. Choosing a target X3 release without checking the OS it demands produces a migration plan that has to be rebuilt once someone reads the prerequisites page properly.
What it means for the estate
Three moving floors — X3 patch level, SQL Server, Windows Server — with dependencies in both directions. There is exactly one combination that is current and supported end to end, and finding it is a two-hour job that is worth doing before anything is costed.
Java and Elasticsearch are cost and risk drags rather than hard breaks: X3 runs latest Java 8 through 2024 R1 and latest Java 11 from 2024 R2, and supports Elasticsearch 6.4, 6.8, 7.16 or latest 8, of which only the ES 8 path is vendor-supported.
Primary sources
Run the exposure check — three minutes, free, and it will tell you which of the other 11 dates catch you as well and in what order they have to be done. Sequencing is most of the cost on these programmes.