Let’s check the latest ConfigMgr Deprecated Features | Removed Features Of SCCM | Unsupported features. The post is all about the updated list of SCCM Unsupported features/SCCM Deprecated Features. Also, you will be able to check out the unsupported versions of SCCM client operating systems (Windows, Linux, Unix, etc..).
Updated on 4th July 2021 – The biggest announcement is HTTP-only client communication is going out of support.
I’m not planning to cover the unsupported operating systems for SCCM site system/site server/SQL roles in this post.
Updated List of SCCM Unsupported Features/SCCM Deprecated Features
| SCCM Unsupported Features | End of Support Date |
| The SCCM cloud-attach scenario uses Azure AD Graph API and Azure AD Authentication Library (ADAL) will no longer be supported. | 30th June 2022 |
| Legacy MBAM-based service (recovery service) is going way with more integrated features with SCCM MP. | First release after May 2022 |
| Windows diagnostic data processor configuration support is going away with Desktop Analytics data for Windows 7, Windows 8, and earlier versions of Windows 10 that don’t support. | 31st Jan 2022 |
| The older style of console extensions that haven’t been approved in the Console Extension node, will no longer be supported. | TBD |
| SCCM will no longer support the following workloads Certificate profiles, VPN profiles, Wi-Fi profiles, Windows Hello for Business settings, and email profiles. | The first release after 1st March 2022 |
| HTTP-only client communication. Enable a more secure communication method for the site either by enabling HTTPS or Enhanced HTTP. | The first release after Oct 31, 2022 |
| Microsoft Edge legacy browser profiles | April 2021 |
| Desktop Analytics tile and page for Security Updates | March 2021 |
| The collection evaluation viewer, which is integrated in version 2010. | The first release after March 1, 2021 |
| Log Analytics connector for Azure Monitor. | The first release after July 1, 2021 |
| The geographical view in the Site Hierarchy node of the Monitoring workspace in the SCCM console. | TBD |
| You won’t be able to create a traditional cloud distribution point in the future. | TBD |
| Classic service deployment to Azure for CMG and cloud DP | TBD |
| DHA for conditional access compliance policies | Version 1910 |
| The Configuration Manager Company Portal app | Version 1910 |
| SCCM CMG Classic Service Deployment | SCCM 1910 |
| Windows Analytics and Upgrade Readiness integration | January 31, 2020 |
| SCEP (Defender) for Mac and Linux Clients | 31st Dec 2018 |
| SCCM On-premises Conditional Access | 1st Sep 2019 |
| SCCM Hybrid MDM (Intune) | 1st Sep 2019 |
| SCCM Windows Hello for Business settings | 1st SCCM Release of 2020 |
| SCCM Application Catalog Support | SCCM 1810 |
| Old SCCM Software Center Support | SCCM 1802 |
| SCCM VHD Support | SCCM 1710 |
| SCCM Linux and Unix Clients Support | SCCM 1902 |
| SCCM Windows 8 Client Support | SCCM 1802 |
| SCCM Windows XP Client Support | SCCM 1511 |
| Convert Disk to Dynamic – SCCM Task Sequence Action | SCCM 1710 |
| Install Deployment Tools – SCCM Task Sequence Action | SCCM 1710 |
| OSDPreserveDriveLetter – Task Sequence Action | SCCM 1606 |
| SCCM NAP Support | SCCM 1511 |
| SCCM Out of Band Management | SCCM 1511 |
What is SCCM Deprecated Features? (
SCCM Removed Features )
The following is the official statement from Microsoft on SCCM deprecated features (SCCM Unsupported features/SCCM Deprecated Features). A feature, a product, or an operating system will be first listed as deprecated. The support for using it with SCCM is scheduled to be removed in a future version of SCCM.
- Can’t use anymore?
- Can use without support?
I would recommend not to use any deprecated feature of SCCM (Removed Unsupported SCCM Features). But, that doesn’t mean that unsupported SCCM client operating systems won’t work at all. You can take the risk of using some depreciated features and unsupported operating systems for SCCM clients.
NOTE! – Some of the deprecated features will be removed from GUI and there will be a hard block. Hence you won’t be able to use.
Microsoft doesn’t give any guarantee for these unsupported or depreciated features of SCCM. You might be able to make it work, but you won’t get any support from Microsoft, and they stopped developing that section of code in the product. But, (I assume) still most of the code will be there in the product itself.
There are some other deprecated features which can’t be used at all after the end of support date. For example, SCCM CMG creation via classic service deployment, this feature can’t be used by any of the SCCM admins. Why? The options for this feature will be removed from GUI itself.
NOTE! – So make sure, you start planning to move away SCCM deprecated features (SCCM Unsupported features/SCCM Deprecated Features) as soon as possible.
Deprecated or Unsupported Features via SCCM Management Insights
Most of these SCCM deprecated features (SCCM Unsupported features) will be highlighted via SCCM management insights within the SCCM console. This notification is helpful for SCCM admins to fine tune the SCCM environment.
SCCM Unsupported features with Management Insights
Management Insights to Understand Unsupported Features
Following is some of the management insight rules about SCCM deprecated features (SCCM Unsupported features):
- Unsupported antimalware client versions
- SCEP for Mac and Linux end of support
- Old (non-CB) SCCM Client Versions
- Direct your user to software center instead of the application catalog
- Use the new version of Software Center
Resources
- Microsoft documentation on SCCM Depreciated Features
- More Insights of SCCM depreciated features with Management insights
Good one Sir. So what should we do for application catalog. We removed the role. Alternative Sir?
Most of the features are available in the Software center itself. Are you missing some features of the application catalog that are not available in Software Center yet.