Top 10 ConfigMgr 2403 New Features

In this article, I will list some of the best ConfigMgr 2403 new features that can be used right away after upgrading to version 2403. It is worthwhile to upgrade to SCCM 2403 since it has many new features and enhancements over the previous release.

Microsoft has released ConfigMgr update 2403, and this update can be applied to sites running version 2211 or later. I recommend using the SCCM 2403 upgrade guide, which includes all the information required for upgrading your Configuration Manager to version 2403.

From my understanding, most of the new features in SCCM 2403 were first added in technical preview 2401 and the remaining were from other technical preview releases. If you have been following this blog, you will agree that I cover the new features added to every technical preview release in detail.

It is important to know that the new features in SCCM 2403 can be used only when you update the client agents to the latest version (5.00.9128.1005 or later). Ensure you upgrade the clients to the latest version in your hierarchy before testing out the new features.

List of ConfigMgr 2403 New Features

Before I cover each of the new features in detail, here is the list of new features that have been added to the SCCM 2403 release.

• Microsoft Azure Active Directory rebranded to Microsoft Entra ID
• Automated diagnostic Dashboard for Software Update Issues
• The console now has a centralized search box
• Added Folder support for Scripts node in Software Library
• HTTPS or Enhanced HTTP, should be enabled for client communication from this version of Configuration Manager
• Resource access profiles and deployments will block Configuration manager upgrade
• The Save-CMSoftwareUpdate cmdlet now has a new parameter called SoftwareUpdateO365Language.
• Support for ARM 64 Operating System Deployment
• Enhancement in Deploying Software Packages with Dynamic Variables
• Upgrade to CM 2403 is blocked if CMG V1 is running as a cloud service (classic)

Here is an official guide by Microsoft on what’s new in version 2403 of Configuration Manager.

1. Microsoft Azure Active Directory rebranded to Microsoft Entra ID

Starting Configuration Manager version 2403, Microsoft Azure Active Directory is renamed to Microsoft Entra ID within Configuration Manager.

Microsoft renamed Azure Active Directory (Azure AD) to Microsoft Entra ID to communicate the multi-cloud, multiplatform functionality of the products. The same rebranding now reflects in Configuration Manager too.

After you upgrade to 2403, in the Configuration Manager console, you’ll see the Azure AD Tenants under Cloud Services have been renamed to Microsoft Entra ID tenants.

2. Software updates health dashboard

A new dashboard has been added to the console under the monitoring workspace section of ConfigMgr 2403; it displays a diagnosis of the software update issues in your environment.

After you deploy software updates using SCCM, the updates may fail to install or cause errors. This dashboard makes it easier to identify any software update-related issues in your SCCM estate. Microsoft says the software update problems can be resolved by using troubleshooting documentation.

To access the Software Update Health dashboard in the console, navigate to Monitoring\Troubleshooting Dashboard\Software Update Health. You can choose the update group to identify issues with the software update installation.

3. New Centralized Search Box in Console

In ConfigMgr 2403 and newer versions, you will find a new centralized search box to find objects within the console, which, we believe, is one of the best new features.

This global search bar improves the overall usability, productivity, and effectiveness of SCCM, as users no longer need to navigate through multiple nodes, sections or folders to find the information they require, saving valuable time and effort.

The centralized search box appears at the top of the Configuration Manager console. You can type the name of the object that you want to search for and press enter. By default, search results will include items from that workspace as well as from all node folders and subfolders.

4. Folder support for Scripts node in Software Library

In version 2403 of ConfigMgr, you can organize scripts by using folders. The Scripts section of the Software Library now supports folders. Admins can use this feature to create, remove, rename, move, and set security scopes for folders.

This change allows for better categorization and management of scripts. Full Administrator and Operations Administrator roles can manage the folders.

5. Support for ARM64 Operating System Deployment

After a long wait, SCCM version 2403 adds support for ARM64 OS deployment. Windows 11 ARM64 devices can be deployed with Configuration Manager. Currently importing and customizing Arm 64 boot images, Wipe and load TS, Media creation TS, WDS PXE for Arm 64 and CMPivot are supported.

In the console, navigate to Software Library > Operating Systems > Boot Images. Here you’ll find a new boot image (arm64); this is exclusively for ARM64 OS deployment.

6. New parameter SoftwareUpdateO365Language is added to Save-CMSoftwareUpdate cmdlet

A new parameter SoftwareUpdateO365Language is now added to the PowerShell Save-CMSoftwareUpdate cmdlet. Customers now don’t have to check a specific language in the SUP Properties (causing a metadata download for that language for all updates).

The below command shows how to use the Save-CMSoftwareUpdate

Save-CMSoftwareUpdate – SoftwareUpdateO365Language <language name> (<region name>)

7. Enhancement in Deploying Software Packages with Dynamic Variables

ConfigMgr Administrators, while deploying the “Install Software Package” via dynamic variable with “Continue on error” unchecked to clients, will not be notified of task sequence failures even if package versions on the distribution point are updated.

8. Upgrade to CM 2403 is blocked if CMG V1 is running as a cloud service (classic)

The option to upgrade Configuration Manager 2403 is blocked if you’re running cloud management gateway V1 (CMG) as a cloud service (classic). All CMG deployments should mandatorily use a virtual machine scale set.

9. Windows Server 2012/2012 R2 is not supported for SCCM Roles

Starting Configuration Manager 2403, Windows Server 2012/2012 R2 operating system site system roles aren’t supported in any CB releases. You cannot upgrade to version 2403 if your primary site server is running Windows 2012/2012 R2.

Microsoft says clients with extended support (ESU) will continue to receive support. When you launch the console, you will see a notification that the Configuration Manager upgrade will be blocked on hierarchy servers running Windows Server 2012/2012 R2.

If your organization contains Windows Server 2012/2012 R2 servers with any of the site system roles such as distribution point, FSP, or MP, you must upgrade the servers to the next supported version. I have listed all the supported Windows server operating systems for SCCM.

10. Resource access profiles and deployments will block Configuration manager upgrade

To be honest, this is not a new feature, but it is important. If you have resource access profiles and deployments that were previously created, the upgrade to version 2403 will fail.

You get the following error: “Delete all Resource Access profiles and associated deployments and move the co-management workload for Resource Access (if co-managed) to Intune.” I have published a dedicated guide to resolve Co-Mgmt slider is not pointed to Intune.

11. HTTPS or Enhanced HTTP should be enabled for client communication

Starting ConfigMgr 2403, HTTP-only communication is deprecated, and support is removed from this version of Configuration Manager. Please enable HTTPS, or Enhanced HTTP for client communication.

Deprecated Features in Configuration Manager 2403

As per Microsoft docs, System Center Update Publisher (SCUP) and integration with ConfigMgr are planned to end support in January 2024. For more information about this, refer to the resource access depreciation FAQ.