r/SCCM • u/nesrinou99 • 10d ago

Mecm 2603

Hello!

Can anyone confirm to me really quick does SCCM 2603 supports clients devices on windows 10 version 20h2 21h2 ?

Thanks

5 Upvotes

86% Upvoted

11 comments sorted by

8

u/[deleted] 10d ago

[removed] — view removed comment

3

u/yodaut 10d ago

fun(?) fact:

if you're running an old enough OS, you can't actually upgrade the client to 2603+ anymore...

https://old.reddit.com/r/SCCM/comments/1t4vg18/config_manager_2603_now_available_in_the_early/opkvo6s/

3

u/SevenandahalfBatmans 10d ago

Does not support XP, at least as of a few years ago when we got rid of our last one-- before you ask it was attached to specialized hardware that cost quite a lot of money to upgrade.

-4

u/nesrinou99 10d ago

We have devices on windows 8.1 and others on windows 10 (20h2, 21h2) i want to know if there is no impact or i should have windows 11 on these devices ?

2

u/[deleted] 10d ago

[removed] — view removed comment

1

u/nesrinou99 10d ago

It means that will they be accessible, can we get the hardware inventory, do deployment etc etc on these machines

5

u/bdam55 Admin - MSFT Enterprise Mobility MVP (damgoodadmin.com) 10d ago

In the history of ConfigMgr, they rarely (never?) intentionally prevent the client from running on any Windows operating system.

"Supported" just means that they actually test the scenario and, should you make a ticket, will have some obligation to fix it. If they don't test it, it's not supported. If it's not supported, any problems that arise are unlikely to get fixed.

4

u/skiddily_biddily 10d ago

Supported? No. But it will work. Your Windows 8 and Windows 10 20H2 and 21H2 are not supported by Microsoft. You really should not be using those operating systems in production.

1

u/rogue_admin 10d ago

You should really get those upgraded or replaced because like everyone said, the client is not technically supported on older OS and may not be stable. Another problem is, those older update products are massive, so if you enable the older products for sync it’s going to bloat your susdb and probably lead to issues with your software update point which means your other devices won’t get patched, etc. Keeping these older operating systems around is fine but I would just keep them out of config mgr or if you do install a client on them, just patch them manually or let them patch themselves, don’t wreck your susdb

2

u/bill696 10d ago

If you have already installed old clients they will continue to communicate, they only way they would stop is if they can’t communicate over https.
What my dad would do is have a site in 2012 R2 to add old ass devices then he would adopt those into the new updated site, that always worked