Top 7 SCCM 2211 New Features, Improvements, and Fixes

Prajwal Desai
Posted by Prajwal Desai
SCCM 2211 New Features Improvements and Fixes

In this article, we will look at the top 7 SCCM 2211 new features that can be used right away after upgrading to version 2211. The ConfigMgr 2211 release includes many new features and improvements over the previous release.

The ConfigMgr version 2211 update will be available only on sites running SCCM 2107 or later. Or, to put it another way, you can only upgrade to ConfigMgr 2211 if you are using version 2107 or higher.

You can upgrade to version 2211 of Configuration Manager current branch using the SCCM 2211 upgrade guide. The upgrade guide includes all the information required for upgrading the Configuration Manager to version 2211.

To take full advantage of SCCM 2211 new features, after you finish the Configuration Manager 2211 upgrade, you must update clients to the latest version 5.00.9096.1000. While new functionality appears in the Configuration Manager console when you update the site and console, the complete scenario isn’t functional until the client version is also the latest.

Top 7 SCCM 2211 New Features, Enhancements, and Fixes

There are many new features and improvements added to the SCCM 2211 release. The new features in the Configuration Manager 2211 update include:

  • Improvements to Cloud Sync (Collections to Azure Active Directory Group Synchronization) feature
  • Network Access Account (NAA) account usage alert
  • Distribution point content migration
  • Featured Apps in Software Center
  • Enhancements in console search experience
  • Dark theme is now extended to more dashboards
  • Resolved duplicate entries for co-managed device in Intune portal

#1 Improvements to Cloud Sync (Collections to Azure Active Directory Group Synchronization) feature

Starting with Configuration Manager 2211, the scalability of the Cloud Sync feature has been improved with better throttles and error handling. Additionally, we see new dedicated dashboards for user collections and device collections in the Monitoring workspace to show Cloud Sync status. The dashboard displays the following:

  • Cloud Sync status per collection with the mapped Azure AD group
  • Total member count
  • Synced member count
  • Status (success, failed, in progress) and last sync details.

#2 Get Account Alert Usage for Network Access Account (NAA)

When you configure network access account in ConfigMgr for your site, you’ll see this new prerequisite warning added. To improve the security of distribution points configured with NAA account, review the existing accounts and their relevant permissions. If it has more than minimal required permission, then remove and add a minimal permission account. Do not configure any administrator level permission accounts on the NAA. If the SCCM site server is configured with HTTPS / EHTTP, it recommended removing NAA account, which is unused. This feature was first added in ConfigMgr Technical Preview 2211 and now this is a part of SCCM 2211 new features current branch release.

#3 New Distribution Point Content Migration Feature

Distribution Point content migration support is now available for migrating content from one DP to another DP using PowerShell cmdlets. You can also monitor the DP migration status using these PowerShell cmdlets. Take a look at how to install and configure SCCM DP.

#4 Software Center Featured Apps

Starting in Configuration Manager 2211, you will find a new Featured tab in Software Center where you can find the featured apps. Using this, IT admin can mark apps as “featured” and encourage end users to use the app. Currently, this feature is available only for “User Available” apps. Furthermore, admins can make the Featured tab of Software Center as default tab from Client Settings.

Software Center Featured Apps - SCCM 2211 New Features
Software Center Featured Apps – SCCM 2211 New Features

#5 SCCM 2211 Console New Search Enhancements

When performing a search on any node in the console, the hint text in the search bar will now indicate the scope of the search. Furthermore, search experience related issues have been resolved.

  • By default, all subfolders are searched when you perform a search in any node that contains subfolders. You can narrow down the search by selecting the “Current Node” option from the search toolbar.
  • If you want to expand the search to include all nodes, then select the “All Objects” button in the ribbon.

#6 Console Dark Theme Extended to more dashboards

Configuration Manager version 2203 introduced a new feature called dark theme support for console. Configuration Manager Console offers dark mode, and you can switch the console theme to dark theme or light theme.

In SCCM 2211, Microsoft has extended the dark theme to additional components such as buttons, context menus, and hyperlinks. You must first enable this pre-release feature to experience the dark theme. The dark theme is extended to more dashboards, which previously didn’t display the dark theme correctly. For example, the O365 Updates Dashboard, PCM Dashboard, and Health Attestation dashboard will now display according to the dark theme when it’s enabled. Pop-ups in the Health attestation dashboard will now adhere to the dark theme.

Console Dark Theme Extended to more dashboards - SCCM 2211 New Features
Console Dark Theme Extended to more dashboards – SCCM 2211 New Features

#7 Resolved duplicate entries for co-managed device in Intune portal

The co-managed devices entities previously showed up on the Intune interface as two independent entries. After registration, two entries – one for Intune and the other for ConfigMgr appeared. In certain instances, the entries were irreversible. Many scenarios, including policy targeting and device entity counts, were impacted. Because Intune is unaware of the AAD ID of devices arriving from ConfigMgr, the entries were duplicated. Only when the daily discovery cycle has completed and sent to Intune via CMGS does Intune become aware. By propagating the right AAD device ID from ConfigMgr during Intune enrollment, the problem is resolved. This quickly results in combined entities for co-managed devices (30-40 mins). The need to wait for the discovery cycle to complete has passed.

Share This Article
Prajwal Desai
Posted by Prajwal Desai
Prajwal Desai is a Microsoft MVP in Intune and SCCM. He writes articles on SCCM, Intune, Windows 365, Windows Server, Windows 11, WordPress and other topics, with the goal of providing people with useful information.
Leave a comment