SCCM Client Version Backward Compatibility

Question

Good day.

I am interested to know that if SCCM client agent (higher version eg Current Branch 2107) is compatible with lower version of Configuration Manager eg 1802?

OR both agent and conf manager have to be in the same version in order to work.

Thanks.

Answer 1

Hi,

You could try to remove the parameter /mp.

The Configuration Manager client installer, ccmsetup, can get installation content from a local source or via a management point. Its initial behavior depends upon the command-line parameters you use to install the client:

• If you don't use either /mp or /source parameters, ccmsetup tries to get a list of management points from Active Directory or DNS.
• If you only specify /source, it forces the installation from the specified path. It doesn't discover management points. If it can't find ccmsetup.cab at the specified path, ccmsetup fails.
• If you specify both /mp and /source, it checks the specified management points, and any it discovers. If it can't locate a valid management point, it falls back to the specified source path.

/mp 
Specifies a management point for clients to use to find the nearest distribution point for the client installation files.
/source
Specifies the file download location. 

https://learn.microsoft.com/en-us/mem/configmgr/core/clients/deploy/about-client-installation-properties

Answer 2

Hi,

SCCM clients are designed to be backward compatible with older versions of the Configuration Manager. This means that a higher version client (e.g., Current Branch 2107) can work with a lower version of Configuration Manager (e.g., 1802). However, this compatibility might not cover all features and functionalities, and some advanced features available in the newer client version may not be supported by the older server version.

It's generally recommended to keep the client and server versions in sync to ensure full functionality and support.

Answer 3

Hi Xin Guo,

Thanks for quick response and also highlighting the new features that I could be missed.

I have a specific condition to setup with this kind of scenario in my environment. My issue is when I try to try install SCCM Client 2107 via command line: "ccmsetup /source:path to the 2107 installer /mp:mysccmserver /logon /SMSSITECODE=xx FSP=mysccmserver", it refuse to install 2107. Instead, it connect to my Configuration Manager and install with version 1802 which is my current configuration manager. It can tell from the ccmsetup log says "Checking the URL "http://mysccmserver/CCM_Client/ccmsetup.cab"

What was possibly goes wrong here? Any idea to get it works in this case?

Best Regards,

Answer 4

Hi Xin Guo,

Thanks for the helps and this works for removing the /mp from the command line.

Thanks again!