There are many methods to install SCCM client Installation 2012 but I had great success rate with following 3. SCCM Client Push SCCM Client Deployment by Group Policy SCCM software Update Deployment Method Before we dive into explaining the above 3 methods. There are several scenarios where you would need to manually install or uninstall the SCCM agent/client, and here’s a quick guide how to do it! Manual Installation. The SCCM 2012 client is stored on your SCCM server (or additional Management Points) in the Client-folder under SMSSITECODE (SCCMSERVERSMSSITECODEClient). When you try to install the Microsoft System Center 2012 Configuration Manager client, the installation fails, and the following text is logged in the CCMSetup.log file: This operating system does not contain the correct version of BITS. BITS 2.5 or later is required. Sending Fallback Status Point message, STATEID='321'.

1. Sccm 2012 Beta
2. What Is Sccm

Sccm 2012 Beta

Hi Vgneshwaran4264,

Thanks for you respond. I am aware that we have to use '/skipprereq:windowsupdateagent30-x64.exe' as part of install command. That has been applied for any future SCCM Client push to new systems.

What's going on here is that before the above fix for windows 10 SCCM Client install are applied. We have all these systems that user upgrade to or manually install windows 10. Then when those systems were added to domain, it receive SCCM Client to install from GPO (without the correct command line in place). Now I have 300+ systems reporting to SCCM as 'Check Fail' status. I have install SCCM Client with correct command line for 3 systems with issue and not they are checking in with SCCM Server now.

What Is Sccm

My intention is to see if there is a way I can create a query in SCCM to check for those 300+ systems for wrong SCCM Client parameters for windows 10. This way I can populate to a collection then do a mandatory push to install correct SCCM Client with '/skipprereq:windowsupdateagent30-x64.exe' command line.