Managing and deploying updates via Configuration Manager
The prerequisite check fails because it detects at least one site server or site system server running an unsupported OS version (for example, Windows Server 2012/2012 R2), not because Windows Server 2025 is unsupported.
For Configuration Manager 2603:
- All site servers in the hierarchy must run a supported version of Configuration Manager before starting the update, and all site system roles (except specific DP cases) must run on supported OS versions.
- The prerequisite check explicitly fails when it finds a site server or site system on Windows Server 2012/2012 R2. This is a blocking error for the update.
- Starting in version 2403, site upgrades are blocked if any site systems are detected with operating systems that are past the end of support date.
To resolve the failure:
- In the Configuration Manager console, review all site system roles:
- Go to Administration → Site Configuration → Servers and Site System Roles.
- Identify any site servers or site system servers still running Windows Server 2012/2012 R2 or any other OS that is no longer supported.
- Move or remove those roles, or upgrade the OS on those servers to a supported version.
- Pay special attention to:
- Primary and secondary site servers.
- Management point, software update point, reporting services point, and other roles listed under the prerequisite checks.
- If any remote site systems were recently upgraded in-place to a newer Windows Server version, restart the affected computer or the SMS_Executive service so that the prerequisite checker correctly detects the new OS version.
- Rerun the prerequisite check after all unsupported OS instances are removed or upgraded.
If the only site server is on Windows Server 2025 and all other site systems are on supported OS versions, the prerequisite check should pass and allow installation of update 2603.
References: