Lifecycle Windows Server 2022
Carla Wykes
On January 9th, 2024, Microsoft will end the extended security updates for Windows Server 2008 and Windows Server 2008 R2. This final year of ESU was only available in Azure. If you still have any devices running the 2008 or 2008 R2 version, please make sure to update to the most current version of Windows Server.
Lansweeper data gathered from 1.3 million instances of Windows Server across more than 35,000 organizations shows that an overwhelming majority of users is in fact running a supported version. Only 6.72% of Windows Server installations are unsupported. However, the data also shows that 20.94% of installations are of Server 2012. With the upcoming end-of-life of Server 2012 in October, these will all need to be upgraded soon.
While not receiving any new functionalities is a minor inconvenience, the lack of security updates for legacy products can punch dangerous holes in your network security. The longer you keep a product around after its EOL date, the more security issues will pop up and go unpatched. Eventually, any unsupported product in your network becomes an open door for security breaches.
Windows Server 2008 and Windows Server 2008 R2 originally went end of life on the 14th of January, 2020. Microsoft offered an additional 4 years of Extended Security Updates (ESU). The third (and for non-Azure users last) of these security updates went end of life on the 10th of January, 2023. The final 4th year of ESU (in Azure only) will be going end of life on the 9th of January 2024. From then on Windows Server 2008 and Windows Server 2008 R2 will be fully out of support.
In order to keep your environment up to date and secure, Microsoft recommends that you upgrade any machines still running Windows Server 2008 or 2008 R2 to the latest version. You can find detailed instructions in their Windows Server Upgrades overview.
Our team has put together a Windows Server Audit report that will give you a full overview of when the Windows Server versions in your IT environment will be going end of life. It shows you when the EOL date is and how many days are remaining so you can plan your migrations in advance.
Windows Server 2012 and Windows Server 2012 R2 will be going end of life on the 10th of October, 2023. In order to keep receiving regular updates and keep your environment secure, make sure to upgrade any machines still running Windows Server 2012 or Windows Server 2012 R2 to the latest version. You can find detailed instructions in the Windows Server Upgrades overview.
If needed, it is possible to purchase an additional 3 years of extended security updates for Windows Server 2012 and Windows Server 2012 R2. Please note that the ESU program is considered a last resort for customers who really need to run certain legacy Microsoft products past the end of support. It only includes critical and important security updates. There will be no new features added nor customer-requested non-security updates or design changes.
August 9, 2022, marks the end of support of the last of the modern lifecycle policy Windows Server version. These versions offered a much shorter support period since they are more closely aligned with the Windows 10 versioning.
Microsoft is ending support for the last Semi-annual release of Windows Server. These server versions were an attempt to mirror the Windows 10 versioning, with a new release twice per year. These versions received support for 18 months following their release. With the end of life of Version 20H2, there are no more supported versions of these releases.
Overview
OpenJDK Life Cycle and Support Policy
OpenJDK Update Release Dates
OpenJDK Lifecycle Dates and RHEL versions
OpenJDK Lifecycle Dates and Windows versions
OpenJDK Entitlements
OpenJDK (Open Java Development Kit) is an open source implementation of the Java Platform, Standard Edition (Java SE). The upstream community project OpenJDK is currently sponsored and led by Oracle and is released under the GNU General Public License (GNU GPL 2 and 2+) with a linking exception.
OpenJDK is the Java Development Kit (JDK) and Java Runtime Environment (JRE) in Red Hat Enterprise Linux. Packages for OpenJDK are made available in Red Hat Enterprise Linux in the same manner as the rest of the content set. OpenJDK packages for Microsoft Windows are also distributed via the JBoss downloads section of the support portal. OpenJDK is also shipped as the JDK and JRE in many containers in the Red Hat Container Catalog
Oracle leads development of the Java Platform SE and contributes heavily to the OpenJDK project. Red Hat is one of the top non-Oracle contributors to the project. See Overview and Development model of Java Platform SE for more details.
A major version of OpenJDK is supported for at minimum a period of six years from the time it is first introduced by Red Hat. OpenJDK versions can fall out of support on versions of RHEL if the retirement date of the underlying RHEL platform precedes the retirement date of the OpenJDK version. There are currently three active major versions available in RHEL, but customers are advised to migrate to the newest version of OpenJDK as soon as practical to continue to receive updates and support.
Entitlements for Java workloads on OpenJDK are included in a Red Hat Enterprise Linux subscription. Red Hat Middleware subscriptions include OpenJDK entitlements for Windows when used with Red Hat Middleware. For other Java workloads on Windows (non-Red Hat Middleware), an additional subscription for OpenJDK on Windows is required.
Eclipse Temurin is an OpenJDK distribution produced by Eclipse Adoptium. OpenJDK (Open Java Development Kit) is an open source implementation of the Java Platform, Standard Edition (Java SE). The upstream community project OpenJDK is currently sponsored and led by Oracle and is released under the GNU General Public License (GNU GPL 2 and 2+) with a linking exception.
Eclipse Temurin is distributed by Adoptium through their website, API, and marketplace for a variety of platforms as binaries and installers, as well as distributed on DockerHub as official Docker images.
A major version of Eclipse Temurin is supported for at least a period of six years from the time it is first introduced. Red Hat provides enterprise support for select Eclipse Temurin binaries, Linux x86_64, Linux aarch64, Windows 32-bit, and Windows 64-bit as well as developer support for macOS x64 & aarch64. These are respectively supported on specific Linux, Windows, and Mac platforms outlined below.
OpenJDK versions can fall out of support on platforms if the retirement date of the underlying platform precedes the retirement date of the OpenJDK version. There are currently three active major versions available, but customers are advised to migrate to the newest version of OpenJDK as soon as practical to continue to receive updates and support.
Entitlements for Eclipse Temurin are the same as the Red Hat build of OpenJDK: Entitlements for Java workloads on OpenJDK are included in a Red Hat Enterprise Linux subscription. Red Hat Middleware subscriptions include OpenJDK entitlements for Windows when used with Red Hat Middleware. For other Java workloads on Windows (non-Red Hat Middleware), an additional subscription for OpenJDK on Windows is required. For workloads on non-RHEL or Mac, an additional subscription for OpenJDK is required.
Yes. Red Hat has the ability to provide updates to OpenJDK software shipped in Red Hat Enterprise Linux and Windows distributions subject to the lifecycle guidance provided in this article and subject to the availability of fixes in the upstream distributions. Red Hat can also backport fixes from newer OpenJDK versions to older supported versions when a fix is not provided in the older upstream version.
Yes, it is possible to have multiple versions of OpenJDK on the same Red Hat Enterprise Linux server as long as they are available on the media (DVD) or Red Hat Network channels. These packages are separate packages with the version number clearly identified in the name of the RPM. It is also possible for a third-party Java JDK/JRE to be installed concurrently with OpenJDK. For customer convenience, Red Hat also bundles the IBM JDK via the Supplementary channels. Note that the IBM JDK is not integral to the RHEL content set and follows IBM's guidance on updates and life cycle. We recommend you use the alternatives tool[1] to configure OpenJDK or a third-party Java.
RHEL has a proven track record of maintaining binary compatibility of key components for the life of the (major) release. OpenJDK is no exception to this rule. Users are free to stay at a particular release (e.g. "1.41.1.10.4.el6"). However, we strongly recommend that you update to the most recent release that is available. This ensures that you receive fixes to the most recent critical bugs and security fixes.
While Red Hat will make a commercially reasonable effort to support the earlier release, it may become necessary to update to the most recent release to help reproduce and identify a problem. Red Hat will treat any binary incompatibility between releases as a bug and will attempt to provide a fix as per the SLA. The exceptions to this include and are not limited to our need to patch security vulnerabilities in the package with no option to avoid binary compatibility breakage. These cases are very rare and are clearly documented in the errata.
Yes, we run the TCK test suite, which is a set of tests that we received from Oracle. Anytime there is a code change, we run the TCK to ensure that OpenJDK is in compliance with the Java specification.
Our intent is to support Long Term Support Releases so Red Hat skipped Java SE 9 and 10, and shipped an OpenJDK distribution based on Java SE 11. See the Red Hat OpenJDK 11 Advice article for additional information.
d3342ee215