Have you tried simply excluding CU3 (the KB you cited is CU3, not CU2) from installing during the client install and deferring it to post-image installation? Obviously if there’s a direct need for the CU that’s not an option, but if it’s not and that’s the only thing preventing your image deployment and you’re just looking for a stop-gap for the next few months until the R2 rollout is completed, that would seem to be the simplest solution.
-Phil _________________________________________________________________ Phil Schwan | Technical Architect, Enterprise Windows Services Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI 48075 Lync: 312.756.1626 Mobile: 419.262.5133 www.projectleadership.net<http://www.projectleadership.net/> [Description: Description: Description: Arrow email]Lead with Strategy. Leverage Technology. Deliver Results. [linkedin_logo-19x20]<http://www.linkedin.com/in/philschwan>[Twitter-Logo1-20x20]<https://twitter.com/philschwan> [wordpress-logo3] <http://myitforum.com/myitforumwp/author/philschwan> From: [email protected] [mailto:[email protected]] On Behalf Of Giroux, Eric J Sent: Thursday, August 14, 2014 10:08 AM To: [email protected] Subject: RE: [mssms] OSD with R2 image in non-R2 site The problem is that the ccmsetup /uninstall is not working during the task sequence after the image is layed down. Re-creating and re-capturing the image is not really an option at this point. Need to get this one working. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Niall Brady Sent: Thursday, August 14, 2014 9:13 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] OSD with R2 image in non-R2 site well I havnt tested Eric's scenario yet, i think we should wait and see what he says :) On Thu, Aug 14, 2014 at 3:01 PM, Daniel Ratliff <[email protected]<mailto:[email protected]>> wrote: Ah, uninstallers that work. :D Nice find Niall. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Niall Brady Sent: Thursday, August 14, 2014 8:56 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] OSD with R2 image in non-R2 site good point however, i've just done a quick test on a client that had the r2 client installed, i started wbemtest and connected to root\ccm (wmi basically) it listed all the usual stuff you'd expect to see there, then i closed wbemtest and uninstalled the client using ccmsetup.exe /uninstall during uninstallation you see references to wmi provider removal after verifying it had uninstalled i checked wbemtest again, this time i could not connect to root\ccm as it reported an invalid namespace see screenshot On Thu, Aug 14, 2014 at 2:37 PM, Daniel Ratliff <[email protected]<mailto:[email protected]>> wrote: You may need to do more than just a ccmsetup.exe /uninstall. If its detecting it in WMI, you may need to blow away the CCM repository or maybe a few more to remove all remnants of the R2 client. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Niall Brady Sent: Thursday, August 14, 2014 7:48 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] OSD with R2 image in non-R2 site have you tried recapturing the wim without the client installed, you can build it as normal in a vm, but instead of capturing it, remove the client (ccmsetup /uninstall) and then do the capture using capture media http://www.windows-noob.com/forums/index.php?/topic/5070-how-can-i-capture-an-image-using-capture-media-in-configmgr-2012/ On Thu, Aug 14, 2014 at 1:19 PM, Giroux, Eric J <[email protected]<mailto:[email protected]>> wrote: 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 The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. ________________________________ PRIVILEGED AND CONFIDENTIAL. This email and any files transmitted with it are privileged and confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. If you are not the named addressee you should not disseminate, distribute or copy this e-mail or any of its attachments.
