" known side-effects " more information pls.
On Wed, Jan 28, 2015 at 9:19 AM, Jason Sandys <ja...@sandys.us> wrote: > Yep, just to reinforce, this is explicitly unsupported and there are > known side-effects from doing this. Many folks do it successfully, but > given that it’s explicitly unsupported, I would highly recommend you not do > it this way. > > > > J > > > > *From:* listsad...@lists.myitforum.com [mailto: > listsad...@lists.myitforum.com] *On Behalf Of *Sean Pomeroy > *Sent:* Wednesday, January 28, 2015 9:09 AM > *To:* mssms@lists.myitforum.com > *Subject:* Re: [mssms] RE: Right-Click Client Install > > > > Just be aware that patching that way is unsupported by MS. Its a holdover > from SMS2003 days. > > On Wed Jan 28 2015 at 10:02:31 AM Bradley, Matt <mbrad...@quiktrip.com> > wrote: > > Ok, I got this figured out and working. Like I said, updating our SCCM > server falls under one of our admins duties. But as I got to digging, > there appeared to be a CU msp path in the folder structure of my client > install files. Inside the folder with ccmsetup.exe, there is the i386 and > x64 folders. In each of those is a folder labeled ClientPatch, and within > that, the msp update for the CU. For whatever reason, we had the current > ccmsetup.exe version, but that ClientPatch folder had CU2. I replaced it > with CU3 (configmgr2012ac-r2-kb2994331-x64.msp), redistributed the package, > and now my right-click properly installs the current CU3 version. > > > > > > > >
