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]> wrote: > Ah, uninstallers that work. :D Nice find Niall. > > > > *Daniel Ratliff* > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Niall Brady > *Sent:* Thursday, August 14, 2014 8:56 AM > > *To:* [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]> > 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]] *On Behalf Of *Niall Brady > *Sent:* Thursday, August 14, 2014 7:48 AM > *To:* [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]> 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] | 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. > >
