Microsoft released MECM Version 2203 on April 9, 2022. The MECM 2203 version of the Configuration Manager is now generally available as an opt-in version.
MECM 2203 update is now available, and you can apply this update on sites that run version 2010 or later.
When installing a new site, MECM 2203 will be available as a baseline version.
You cannot upgrade to MECM version 2203 if you are running an older version of ConfigMgr SCCM 2012 or SCCM 2012 R2. If you are running MECM version 2107 you can directly upgrade to MECM 2203. You can skip the MECM 2111.
MECM 2203 features include:-
Prefer cloud-based software update points - Clients now prefer to scan against a cloud management gateway (CMG) software update point (SUP) over an on-premises SUP when the boundary group uses the Prefer cloud based source over on-premises source option.
Improvements to Power BI Report Server Integration - You can now use Microsoft Power BI Desktop that was released after January 2021. MECM 2203 now handles correctly Power BI reports saved by Power BI Desktop in May 2021 or later.
Exclude data warehouse reporting tables from synchronization - Starting in this release, you can exclude one or more of these required tables from synchronization.
Improvements to management insights - A new management insights group was added to Management Insights. A new rule for detecting Windows Server 2012 and 2012 R2 was added to the Proactive Maintenance group.
Deployment Status client notification actions - perform client notification actions, including Run Scripts, from the Deployment Status view.
Delete collection references - When you delete a collection, you can review and delete its dependent collections at the same time
LEDBAT support for software update points
Pre-download content for available software updates
Customize maximum run time for other software update types
ADR scheduling improvements for deployments
Folder support for nodes in the Software Library
Alerts for orchestration groups
Escrow BitLocker recovery password to the site during a task sequence
Custom icon support for task sequences and packages
Improvements to implicit uninstall
Delete a contribution you made to the Community hub
Dark theme for SCCM console
Console and user experience improvements
Servicing Updates for Configuration Manager Updates.
Microsoft releases updates for Configuration Manager current branch version 3 times a year.
Each update is supported for 18 months. Initial, 4 months security and critical updates and next 14 months only security updates.
Supported ADK Version
MECM 2203 Upgrade Prerequisites and Upgrade
Configmgr 2203 current branch is available as an in-console update.
To apply this update on your sites, ensure you have installed MECM version 2010 or later.
Apply the version 2203 updates starting at the top-level site in the hierarchy. Perform upgrade the CAS upgrade, later you can begin the upgrade of each child site.
Ensure that you are running a supported Operating System and SQL Server version.
If there is any pending restart, restart the server and begin the update installation.
The Configuration Manager should have an Online Service Connection Point.
Early Update Ring - Download Opt-In Script
As Configuration Manager version 2203 has been released recently only, it is available for early update ring. We have to download the version 2203 opt-in Script
Once download (EnableEarlyUpdateRing2203.exe), extract .exe.
It will extract as EnableEarlyUpdateRing2203.ps1
Open PowerShell as administrator and execute the below command.
Command:- .\enableearlyupdatering2203.ps1 -siteServer <SiteServername>
Refer the MECM Console, MECM 2203 will be visible under Update and Servicing.
Step to Upgrade MECM 2203.
Login to the MECM console, navigate to Administration\Overview\Updates and Servicing.
The download will start automatically, if not download manually
Once the update is downloaded, we can see Ready to Install.
Run Prerequisite Check, select MECM 2203, right-click, and select "Run Prerequisite Check".
Once the status changes from "Checking prerequisites" to "Prerequisites checked passed with warnings".
Initiate Install Update Pack MECM 2203.
Open MECM Console, click on the administration tab, Overview/Updates and Servicing, right click on MECM 2203, and select "Install Update Pack"
Will launch Configuration Manager Update Wizard window, under General Page, check the box Ignore any prerequisite check warnings and install this update regardless of missing requirements and click Next.
Under Features Included in update Pack page, select the option you want to enable or leave it default.
For Client update options, select the desired option for your client update. This option allows only client members of a specific collection.
Accept the license and click Next.
In Cloud attach window, you can sign in to Microsoft endpoint Manager with your Microsoft organizational account, if you want to skip the cloud attach, uncheck all the checkboxes and click Next.
On the summary tab, review your setting. Click Next.
Close the wizard on the completion Tab
MECM 2203 update installation begins now,
You Can Monitor the MECM 2203 upgrade process.
In the MECM Console, Monitoring workspace.
Click Overview /updates and servicing status.
Right-click Configmgr 2203 and show status.
Once installation is done, you can open the MECM Console will ask you to update your console with the version.
Click on OK
Once completed you can verify the site version. Click on the top left of the SCCM ribbon and select the option "About Configuration Manager".
Client Upgrade
You can upgrade clients by using the Automatic Client Upgrade feature.
Open the MECM 2203 Console.
Goto Administration -> Site Configuration ->Sites.
Click on Hierarchy Setting ->Client Upgrade.
Upgrade client Automatically when the new client update is available to the checkbox is enabled.
Set the required number of days for Automatic Client Upgrade
Update Boot Image, it is recommended to update the client version in the boot image as well.
Open the MECM console software library\Overview\Operatins System\Boot Images, select the boot image and click Update Distribution Point.
Logs:-
Dmpdownloader.log
cmupdate.log
Configmgrprereq.log
ConfigMgrAdminUISetup.log
ConfigMgrAdminUISetupVerbose