Yes, by not supported means that MS may not support any issues arising in your ConfigMgr infra if you are not running a supported configuration. While things may work, it is not recommended to run unsupported configuration as issues may arise. Having said that, I have personally not faced issues in a situation like yours, but this should not be generalised in anyway.
Supported Windows 11 clients in MECM/SCCM Config Mgr?
Hi All - Right now we are on ConfigMgr version 2203. We already have a few Win 11 22H2 PCs with the SCCM client. We haven't noticed any issues functionality wise or problems with this (apparently) "unsupported" OS in Config Mgr. We have a mix of domain systems imaged by SCCM and then AutoPilot AAD systems with the Config Mgr client running co-management. Our server team said there are roadblocks to upgrading to at least 2207 branch version as several Win server OSs running the sites need to be upgraded before 2207/2211 branch can be installed. While it says 'unsupported' below, does that just mean if we had to open a case or run into issues with 2203 and Win 11 22H2, MS would say they can't help? Or the Win 11 22H2 systems in Config Mgr 2203 can/do operate fine, but may not in the future? Have you noticed any issues with your PCs if you are in this bind?
1 additional answer
Sort by: Most helpful
-
AllenLiu-MSFT 41,136 Reputation points Microsoft Vendor
2023-03-17T02:11:33.08+00:00 Hi, @Courtney Regan
Thank you for posting in Microsoft Q&A forum.
Like you said, the Win 11 22H2 systems in ConfigMgr 2203 can/do operate fine now, but may not in the future.
So, it's recommended to upgrade SCCM to the latest version ASAP after your server team upgrade the server.
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.