Configuration Manager update 2303 is the recently released update of Microsoft Endpoint Configuration Manager version. 2303 update is available as in-console update and is also available soon as baseline version

Microsoft Endpoint Configuration Manager name is changing to Microsoft Configuration Manager with this release.

Following is the benefit of in-console update:

  • In-console updates provides greater flexibility of upgrading the SCCM Current Branch by getting updates of SCCM within SCCM console only.
  • You just need to make sure that “Service connection point site system role” should be installed on SCCM to make sure synchronization schedule pull latest updates for SCCM.
  • Once you install in-console update on CAS site, updates will be automatically applied to Primary sites. For secondary sites, you need to initiate it manually.

Configuration Manager Supported Versions:

Configuration Manager 2203, 2207 and 2211 are the supported versions when publishing this post. If you are doing fresh setup of SCCM, you can download and use this Baseline version  as baseline media for installation through Volume Licensing Service.

VersionAvailability dateSupport end dateBaselineIn-console update
2207 (5.00.9088)12-Aug-2212-Feb-24NoYes
2203 (5.00.9078)8-Apr-228-Oct-23YesYes
2111 (5.00.9068)1-Dec-211-Jun-23NoYes

Servicing Support for Configuration Manager

Microsoft usually releases update for Configuration Manager current branch version 3 times a year. But this cadence is changing from three updates to two updates a year. The current version released is 2303 and next one will be version 2309 which combines version xx07 and xx11. Check the link for more details on change in cadence for Configuration Manager

Each update is supported for a period of 18 months. For 18 months of lifecycle, initial 4 months are for Security & Critical Updates while next 14 months are for Security Updates only. Above mentioned table can be used to see the servicing life cycle for Configuration Manager updates (supported versions of Configuration Manager including both Baseline and In-console update)

Following link can be used as a reference for supported versions

Supported ADK version

Make sure to have supported Windows ADK version, following is the table showing support for existing ConfigMgr versions:

Windows ADK versionConfigMgr 2111  ConfigMgr 2203  ConfigMgr 2207  ConfigMgr 2211  ConfigMgr 2303
Windows 11
No  Yes  Yes  Yes  Yes
Windows 11
Yes  Yes  Yes  Yes  Yes
Windows Server 2022
Yes    Yes    Yes    Yes    Yes
Windows 10, version 2004
Yes    Yes    Yes    Yes    Yes

What’s new in SCCM 2303
For detailed list on what’s new in version 2303 of Configuration, you can follow this What’s new in version 2303

Following are the improvements and new features, important things to be noted down is:

  • Microsoft Configuration Manager product branding – Previously Microsoft Endpoint Configuration Manager was used.
  • Improvements to Cloud Sync.
  • Endpoint Security reports in Intune admin center for Tenant Attached devices.
  • SQL Server 2022 version support added for Configuration Manager.
  • Unified update platform (UUP) GA release.
  • Maintenance window schedules.
  • Dark theme extended to delete secondary site wizard

Following is the Checklist for installing update 2303 for Configuration Manager

Early update ring – Download opt-in script

As Configuration Manager version 2303 has released recently only, it is available for early update ring. We need to opt in for installation, ie we have to download the Version 2303 opt-in script

Once downloaded (EnableEarlyUpdateRing2303.exe), execute it to extract EnableEarlyUpdateRing2303.ps1

Open PowerShell as Administrator, and run following command:

.\enableearlyupdatering2303.ps1 -siteServer <SiteServername>

(Replace <SiteServerName> with your SCCM server)


Configuration Manager 2303 will be made available immediately under Updates and Servicing.

Install Configuration Manager 2303 update

Login to SCCM server, open Configuration manager console and navigate to \Administration\Overview\Updates and Servicing, we can see new version available “Configuration Manager 2303” version 5.00.9106.1000.

Configuration Manager 2303 available to download

Downloading should start automatically, if not should Right click “Configuration Manager 2303” and click on download.

Configuration Manager 2303 Downloading

The status of the update will soon change from available to downloading. It will download the update in cab format ( which can be monitored through dmpdownloader.log and the location of update will be:

EasySetupPayload Cab file

D:\Program Files\Microsoft Configuration Manager\EasySetupPayload

Following info you can see in the dmpdownloader.log:

EasySetupMaintenance – Redownload package: 2b85942d-2f3a-4b8c-afa7-20c37e3bb266
The payload to be processed is at D:\Program Files\Microsoft Configuration Manager\EasySetupPayload\
Download content for payload 2b85942d-2f3a-4b8c-afa7-20c37e3bb266
Redirected to URL

dmpdownload.log SCCM 2303

File D:\Program Files\Microsoft Configuration Manager\EasySetupPayload\ has been extracted with 0

Once downloaded, cab file will be extracted with in same folder and original cab will be deleted, you will be able to see following folder:

D:\Program Files\Microsoft Configuration Manager\EasySetupPayload\2b85942d-2f3a-4b8c-afa7-20c37e3bb266

SCCM2303 06

Once update is download, you will see the status as “Ready to Install” for “Configuration Manager 2303

Run Prerequisite Check
Select “Configuration Manager 2303”, right click and select “Run Prerequisite Check”, the status will change to “Checking prerequisites”. Verify CMUpdate.log for process initiation and verify c:\ConfigMgrPrereq.log for success or failure.

SCCM 2303 Run prerequisite check
SCCM 2303 Checking prerequisites

CMUpdate will show you multiple stages of Prerequisite check which can be seen as SubStageID such as 0xe0005.

Wait for last stage to get it completed.

You will see following in CMUpdate.log:

Content replication succeeded. Start extracting the package to run prereq check...
Successfully reported ConfigMgr update status (SiteCode=MAN, SubStageID=0xd0005, IsComplete=1, Progress=1, Applicable=1)
Successfully reported ConfigMgr update status (SiteCode=MAN, SubStageID=0xd0005, IsComplete=1, Progress=25, Applicable=1)
Successfully reported ConfigMgr update status (SiteCode=MAN, SubStageID=0xd0005, IsComplete=2, Progress=100, Applicable=1)
Running prereq checking against Server [SCCM01.MANBAN.COM] ...

ConfigMgrprereq.log will show:
******* Prerequisite checking is completed. *******

SCCM Prerequisite checking is completed

In-console updates provides greater flexibility of upgrading the SCCM Current Branch by getting updates of SCCM within SCCM console only.

Initiate Install Update Pack
Open SCCM Console, click on Administration Tab, go to Overview > Updates and Servicing. On right Pane you will be able to see now “Configuration Manager 2303”, from the top ribbon select “Install Update Pack”.

SCCM Install Update Pack

This will launch Configuration Manager Update Wizard, under General page check the box Ignore any prerequisite check warnings and install this update regardless of missing requirements. Once again, don’t do it in the production environment. Click Next.

Configuration Manager 2303 Updates Wizard

Under Features included in update pack page, select the options you want to enable or leave it as default. You can enable this at later stage as well. Click Next

Configuration Manager 2303 Features included in update pack

Under Client Update Settings page, select Validate in pre-production collection and select the collection used for this so that you can test new client agent on few systems before rolling out in production. Click Next.

SCCM 2303 Validate in pre-production collection

Under License Terms page, check the box “I accept these License Terms and Privacy Statement”. Click Next.

SCCM 2303 License terms

You will get completion status, click on Close to exit.

Under SCCM Console, you will see the installation status showing as Installing.

SCCM 2303 update summary

You can monitor the installation through Monitoring \ Overview \ Updates and Servicing Status and through CMUpdate.log.

Navigate to \Monitoring\Overview\Updates and Servicing Status, select Configuration Manager 2303, right click and select Show Status.

Update Pack Installation Status will show the installation progress.

SCCM 2303 Extract Update package

After waiting for some time, Update Pack installation status will show success in cmupdate.log with message:

Content replication succeeded. Start extracting the package to run prereq check…

Update pack install status will show the upgrade has been completed.

Successfully reported ConfigMgr update status (SiteCode=MAN, SubStageID=0xe0005, IsComplete=2, Progress=100, Applicable=1)
Successfully reported ConfigMgr update status (SiteCode=MAN, SubStageID=0xe0006, IsComplete=1, Progress=1, Applicable=1)
MonitorDrsReplication waiting for server to be in replication active state for maximum 1800 second .
check current replication details
successfully detected the site server is in ReplicationInactive state.
Successfully reported ConfigMgr update status (SiteCode=MAN, SubStageID=0xe0006, IsComplete=2, Progress=100, Applicable=1)

Once installation is done, and you try to open the SCCM console, this will ask you to update your console with version 5.2303.1089.1000. Click on Ok to initiate download and install.

SCCM 2303 console update

Download of Adminconsole.msi will happen at following location:

C:\Program Files (x86)\ConfigMgr10\AdminconsoleSetup\469A3000-14DA-425E-B288-4B0E16DB87C4

Configuration Manager Adminconsole Setup location

Adminconsole.msi will be visible which will be executed automatically.

Downloading & installation of console can be verified through log file:


Once completed you can verify the site version and control version (by clicking on top left of the SCCM ribbon and selection option “About Configuration Manager”.

Version 2303
Console Version: 5.2303.1089.1000
Site Version: 5.0.9106.1000

Configuration Manager 2303 version info

Navigate to \Administration\Overview\Updates and Servicing, we can see Configuration Manager 2303 showing status as “Installed”

Configuration Manager 2303 installed

Client Update

We can see the Production client version is 5.00.9096.1000 and Pre-production client version is 5.00.9106.1000 under \Administration\Overview\Site Configuration\Sites.

Configuration Manager 2303 Production client version

Updated client version (5.00.9106.1000) is currently Pre-production client version which is targeted on collection “Pilot Client” as we selected during installation Phase. Under Hierarchy Settings Properties, we must make sure to check the box “Upgrade all clients in the hierarchy using production client”

Source of this client version is created in StagingClient under Microsoft Configuration Manager Folder:

Configuration Manager 2303 Staging Client location

Promote Pre-production Client

If you want to promote the Pre-production client in production environment, then navigate to \Monitoring\Overview\Client Status. Right click Pre-production Client Deployment and select Promote Pre-production Client.

SCCM 2303 Pre-production Client Deployment

Promote Pre-production Client window will appear, click on Promote to replicate the changes in the environment using new SCCM client package.

SCCM 2303 Promote Pre-production Client

Update Boot image

For better support with your boot images, it is recommended to update the client version in boot image as well, though old one will also work fine. Benefit of having latest client version in boot image is better support and compatibility.

SCCM 2303 Boot Image update

Navigate to \Software Library\Overview\Operating Systems\Boot Images, select the boot image and click Update Distribution Points. You will be represented with current Windows ADK version and current client version and showing the old client version as well.

SCCM 2303 Update boot image

You don’t require to select “Reload this boog image with the current Windows PE version from the Windows ADK”, this option is only required when you have updated the ADK.

SCCM2303 28

The consequences of reloading the boot image is, you are going to loose all kind of customization done (if any) within the boot image such as injecting MsDart binaries, increasing smsts.log file size using smsts.ini etc, everything will be lost. For more info on find the link on Customize boot image

SCCM2303 29

We can see now Boot image is updated with latest client version ie. 5.00.9106.1000

SCCM2303 30

Important Links

What’s new in version 2303 – Configuration Manager | Microsoft Learn

Checklist for 2303 – Configuration Manager | Microsoft Learn