Site Version Is Past The End Of Support 2203

[Nakia Schaf]

OurSCCM server gives us the error that the site is past the end of support however we are on the latest version (2207)

Is there a way to resolve this problem? Perhaps somewhere in the registry?

It seems the others have also encountered this problem, some people fixed it by upgrade the SCCM, but you already have the latest version.

It's recommended to open a support case with Microsoft Customer Support Services (CSS) as they can work with you to solve this problem.

Here is the link of CSS support:

-us/hub/4343728/support-for-business

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Under the tab for "Licensing", what date is there for Software Assurance expiration date? If that date is in the past, read the "learn More"... determine what is the right thing to do for your company and licensing agreements. You may need to update that date to match your existing Software Assurance expiration date for your company.

Version 2211 of Microsoft Configuration Manager (formerly Microsoft Endpoint Configuration Manager, System Center Configuration Manager, or SCCM) will go end of life on June 5, 2024. In order to avoid running outdated and unsupported versions, we made an overview of everything that you need to know regarding the versions of SCCM that go end of life. Keep your network safe and update your Configuration Manager environment.

Microsoft releases a new updated version of Configuration Manager a couple of times per year. Each version remains in support for 18 months. Any version that is still in support will receive technical support. The latest current branch also received both security and critical updates. When a new current branch is released, Microsoft only supports security updates for older versions for the remainder of their lifecycle. There is no option for additional paid extended support when a version of SCCM goes end of life.

Microsoft Endpoint Configuration Manager version 2211 will reach its end of support date on June 5, 2024. You are advised to update any installation you have to version 2303 or higher in order to continue receiving support and updates. Aside from still being supported, version 2303 also includes a list of new features, including but not limited to:

Our experts created an SCCM End of life Audit Report that checks if the assets running Microsoft Configuration Manager software in your network are on the latest versions. This will give you an easy and quick overview of which assets are already on the latest version of Microsoft Endpoint Configuration Manager, and which ones still need to be patched. As always, all admins are advised to install these security updates as soon as possible to protect your installations from security risks.

Microsoft Endpoint Configuration Manager version 2207 will reach its end of support date on the 12th of February, 2024. You are advised to update any installation you have to version 2211 or higher in order to continue receiving support and updates. Aside from still being supported, version 2211 also includes a list of new features, including but not limited to:

Microsoft Endpoint Configuration Manager version 2111 will go end of life on the 1st of June, 2023. Make sure to update your installation to version 2203 or higher in order to stay fully supported. Aside from still being supported, version 2203 also gives you access to a list of new features, including but not limited to:

Microsoft Endpoint Configuration Manager version 2107 will be going end of life on the 2nd of February, 2023. To ensure your SCCM version is fully supported you are advised to update to version 2111 or higher. Aside from being supported, version 2111 also adds a list of new features that you can make use of, including but not limited to:

SCCM version 2103 will go end of life on October 5, 2022. To ensure your SCCM version is fully supported it is advised to update to version 2107 or higher. Aside from being supported, version 2107 also adds a list of new features to the SCCM feature set that you can make use of, including but not limited to:

Multiple products part of Microsoft System Center 2012 and Microsoft System Center 2012 R2 are going end-of-life on July 12, 2022. While these products will continue to function, Microsoft will no longer be providing technical support, security updates and fixes, or definition, engine, and platform updates.

SCCM version 2010 will be end of life on May 30, 2022. To ensure your SCCM version is fully supported it is advised to update to version 2103 or higher. Aside from being supported, version 2103 also adds a list of new features to the SCCM feature set that you can make use of, including but not limited to:

SCCM version 2006 will be end of life on February 11, 2022. To ensure your SCCM version is fully supported it is advised to update to version 2010 or higher. Aside from being supported, version 2010 also adds a list of new features to the SCCM feature set that you can make use of, including but not limited to:

Founder of System Center Dudes. Based in Montreal, Canada, Senior Microsoft SCCM Consultant, 8 times Enterprise Mobility MVP. Working in the industry since 1999. His specialization is designing, deploying and configuring SCCM, mass deployment of Windows operating systems, Office 365 and Intune deployments.

Microsoft has released the first SCCM version for 2022. SCCM 2203 has been released on April 8th, 2022. This post is a complete step-by-step SCCM 2203 upgrade guide, meaning that if you want to upgrade your existing SCCM/MEMCM installation to the latest SCCM/MEMCM updates, this post is for you.

SCCM 2203 includes an incredible amount of new features and enhancements in the site infrastructure, content management, client management, co-management, application management, operating system deployment, software updates, reporting, and configuration manager console. This release is packed with interesting features to try.

Before installing, make sure that you are running a supported Operating System and SQL version. Older SCCM version was giving a warning during the Prerequisite check but 2107 is giving an error that prevents the installation from continuing.

Version 1906 client requires SHA-2 code signing support.

Due to weaknesses in the SHA-1 algorithm and to align to industry standards, Microsoft now only signs Configuration Manager binaries using the more secure SHA-2 algorithm. The following Windows OS versions require an update for SHA-2 code signing support:

Windows 7 SP1

Windows Server 2008 R2 SP1

Windows Server 2008 SP2

You can use this SCCM 2203 upgrade guide to upgrade your Configuration Manager running in production to version 2203. After you install SCCM version 2203, you must also install the latest hotfixes available for 2203 to ensure all the bugs and known issues are resolved.

In this guide, will look at the steps to upgrade Configuration Manager running in production to version 2203. You can begin the upgrade to ConfigMgr 2203 from the Updates and Servicing node of Configuration Manager console.

The SCCM 2203 update is now available for everyone, and you can apply this update on production sites that run version 2010 or later. In other words, the SCCM upgrade path to 2203 begins with version 2010 and above.

Important: You cannot upgrade to SCCM version 2203 if you are running older versions of ConfigMgr such as SCCM 2012 or SCCM 2012 R2. If you are still running an older version of Configuration Manager, you must upgrade to current branch soon.

SCCM current branch release 2203 is the first current branch release of the year 2022. The next versions of SCCM will be SCCM 2207 and SCCM 2211. Remember that every new ConfigMgr current branch update version remains in support for 18 months from its general availability release date.

Before you upgrade to SCCM version 2203, please read the SCCM upgrade checklist and prerequisites. Here are some of the prerequisites checklist that you need to look into before installing Configuration Manager 2203 update.

SCCM 2203 supports the latest versions of Windows 10 ADK and Windows 11 ADK. For Windows 10, you can install Windows ADK for Windows 10 version 2004. With SCCM 2203, you can deploy and manage Windows 11, it means you can also install Windows 11 ADK for Windows 11 operating systems.

If you have installed an older version of ADK and would be upgrading your Windows 10 to newer versions like Windows 10 20H2 or Windows 10 21H2, you must upgrade your ADK. Use the following guide to update ADK on SCCM server.

The Fast ring (early Update Ring) is an opt-in ring only available for SCCM environments (using PowerShell Script). The Slow Ring (also known as Generally Available) is available for all ConfigMgr environments.

Wait while the ConfigMgr update 2203 downloads and extracts all the files required for upgrade. The update state immediately changes from Downloading to Ready to Install.

The second method that you can use is to verify the prerequisite check results is directly from the Configuration Manager console. In the Updates and Servicing node, the State column shows the prerequisite check state.

In this example, we see the state as prerequisite check passed for update 2203. This means there were no errors or warnings found during Configuration Manager 2203 prerequisite checks and update 2203 can be installed.

The Cloud Attach tab includes cloud attach settings. You can sign in to Microsoft Endpoint Manager with your Microsoft organizational account. If you want to skip the cloud attach settings, uncheck all the checkboxes and click Next.

3a8082e126