I have a situation with the SCCM 2012 R2 client as part of a captured WIM image that is causing an issue. My company is mid-way through our upgrade from SCCM 2012 SP1 to SCCM 2012 R2. Our lab site where I create my WIM images is R2, but our production site is not R2, and will not be for a couple more months. I created a new WIM image in the lab site which has the R2 SCCM client baked into it. When attempting to deploy this image in the prod non-R2 site it is failing when trying to install the SCCM client during the task sequence. The ccmsetup.log shows that it is detecting the newer R2 version of the client being present in WMI. When the client install gets to the point of validating the CU2 patch I'm installing as part of the client setup action it's telling me that kb2882125 is not applicable to the currently installed version of the client and then it fails the task sequence.
Is there a way I can prevent this detection of the R2 client that is in the WIM and somehow force it to install the SP1 client during task sequence deployment? I've tried running a simple ccmsetup /uninstall in the task sequence prior to the CCM client install action but that fails. Regards, Eric Giroux Senior Infrastructure Engineer Unum End User Computing E-mail: [email protected]<mailto:[email protected]> | Office: (207) 575-2482 Mobile: (207) 239-5190 | Fax: (207) 575-2158
