Replace SCCM 2012 agent to another SCCM 2203

Question

Hi,

Our domain have 2 SCCM servers: SCCM CB 2203 server and SCCM 2012 server.

As the SCCM 2012 will be retired, the clients (Win 7) and servers managed by this SCCM server will be changed to manage by the SCCM 2203. Can we push the 2203 agent to these clients to replace the old 2012 agent directly? Or I need to remove the old agent and install the new agent one by one directly?

Thanks

Best Regards
Chong

Answer 1

Hi,

Yes, after the sccm upgrade to 2203, we could push the 2203 agent to clients, SCCM 2203 client version is 5.00.9078.1006, we could use the Automatic Client Upgrade feature to upgrade it.

-->1.Open the SCCM Console.
-->2.Go to Administration > Site Configuration > Sites.
-->3.Click the Hierarchy Settings in the top ribbon and select the Client Upgrade tab.
-->4.The Upgrade client automatically when the new client update is available to the checkbox is enabled.
-->5.Set the required number of days for automatic client upgrade.

With automatic client upgrade enabled, any computers running an older version of ConfigMgr client will now upgrade to version 5.00.9078.1006.

Agree with Garth, the Configuration Manager 2203 client agent is compatible with Windows 10 and Windows 11 operating systems, so win7 is not support, the upgrade will fail, please upgrade it.

Please note: the sccm 2012 version is older, please do not upgrade to the 2203 immediately, we could upgrade to for example 2103, and then 2203 to avoid any issue.

---

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 "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.

Answer 2

You can push directly to them for the older cm12 clients. Keep in mind that win 7 isn't support and there is no guarantee that everything will work. 100%.

Answer 3

Hi，

According to your description, these clients managed by sccm 2012 could not discovered by sccm 2203, is it right? If so, yes, it means these new machines will be SCCM client. We should configure a new boundary and then push the client.

Here are these articles about installing configuration manager clients by using client push and boundaries:
https://www.prajwaldesai.com/install-configuration-manager-clients-using-client-push/
https://www.prajwaldesai.com/configuring-discovery-boundaries-sccm/
Note: These links are not from Microsoft, just for your reference.

---

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 "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.