How to upgrade the sccm verison from 2403 to 2509

Kaushal Mourya 0 Reputation points
2026-07-31T07:07:57.0866667+00:00

How to upgrade the SCCM version from 2403 to 2509 and what is the perpetuities to perform this task

Microsoft System Center | Other
0 comments No comments

1 answer

Sort by: Most helpful
  1. AI answer

    2026-07-31T07:08:23.1533333+00:00

    To upgrade Configuration Manager from 2403 to 2509, use the in-console update for version 2509. Version 2509 can be applied only on sites that run version 2403 or later.

    Recommended upgrade path:

    1. Verify the hierarchy version
      • Every site server in the hierarchy must run the same Configuration Manager version before starting the update.
      • To update to 2509, the hierarchy must already be on 2403 or later.
    2. Confirm the update can be downloaded
      • A service connection point is required at the top-level site of the hierarchy.
      • The service connection point can be online or offline.
      • If it is offline, use the service connection tool to download the update.
    3. Find the update in the console
      • In the Configuration Manager console, go to Administration > Updates and Servicing.
      • When version 2509 shows as Available, it is ready to install.
      • If it stays at Downloading, review hman.log and dmpdownloader.log.
      • If dmpdownloader.log shows it is waiting for the next interval, restart the SMS_Executive service on the site server to restart the download of redistribution files.
      • Also verify that proxy settings are not blocking downloads from the required internet endpoints.
    4. Start the installation from the top-level site
      • Install 2509 from the CAS or the stand-alone primary site.
      • After the top-level site is updated:
        • Child primary sites install the update automatically after the CAS finishes.
        • Secondary sites must be updated manually from the Configuration Manager console after the parent primary site finishes.

    Prerequisites before upgrading:

    1. Supported source version
      • The environment must be on 2403 or later.
    2. Licensing status
      • An active Software Assurance (SA) agreement or equivalent subscription rights is required to install the update.
    3. .NET requirement
      • Configuration Manager requires Microsoft .NET Framework 4.8 for site servers, specific site systems, and the console.
      • Update .NET first, then restart the system before running setup.
      • A pending reboot can cause component status errors and random .NET application failures until restart.
    4. Windows ADK
      • The installed Windows ADK version should be supported for Configuration Manager 2509.
      • If the ADK must be updated, do that before upgrading Configuration Manager so the default boot images are updated automatically.
      • Any custom boot images must be updated manually after the site update.
    5. Site system prerequisites
      • Before installing the update, make sure each site system server meets the current prerequisites for the new version.

    Important behavior during the upgrade:

    • Until all child primary sites finish updating:
      • Client upgrades do not start.
      • New features enabled by the update are not available.
      • Replication links can show Completed with warning or Link is being configured.

    Post-upgrade tasks:

    1. Update the Configuration Manager console
      • The first time the console is opened after the site update, it prompts for a console update.
      • Update all remote consoles to the same version as soon as possible.
    2. Update clients
      • New functionality is not fully available until the client version is also updated to the latest version.
    3. Verify site and role versions
      • In Administration, add the Version column in Sites and Distribution Points to confirm they are on 2509.
    4. Check replication health
      • In Monitoring > Site Hierarchy and Monitoring > Database Replication, confirm replication is active.
    5. Review environment reconfiguration items if applicable
      • Reconfigure database replicas for management points if they were removed before the update.
      • Reset availability groups to automatic failover if used.
      • Re-enable any maintenance tasks that were disabled before the update.

    If the environment already runs 2403, the upgrade to 2509 is supported directly through Updates and Servicing.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.