Correct. NOBODY can say what the "known side-effects" actually are. I have used that method for years and years and never had a single issue as a result.
MS hardly supports the stuff they do support anyway. Not a whole lot of loss there IMHO. On Wed, Jan 28, 2015 at 10:57 AM, Daniel Ratliff <[email protected]> wrote: > Tons of details so Jason doesn’t have to re-explain in the post I sent > before. > > > > > https://social.technet.microsoft.com/Forums/en-US/9e2d45c4-dd36-47d9-853e-4f94fc12ccd0/best-practise-for-installing-patches-for-sccm-client-2012-both-x86-and-x64-osd-and-client-push > > > > *Daniel Ratliff* > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Ewing, Scott L > *Sent:* Wednesday, January 28, 2015 11:24 AM > *To:* [email protected] > *Subject:* RE: [mssms] RE: Right-Click Client Install > > > > What are the known side-effects Jason? > > > > P.S. We use the CCMSETUP.EXE PATCH parameter to install the CU3 > configmgr2012ac-r2-kb2994331-x64.msp. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Jason Sandys > *Sent:* Wednesday, January 28, 2015 10:19 AM > *To:* [email protected] > *Subject:* RE: [mssms] RE: Right-Click Client Install > > > > 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:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Sean Pomeroy > *Sent:* Wednesday, January 28, 2015 9:09 AM > *To:* [email protected] > *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 <[email protected]> > 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. > > > > > > > > > > > > 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. > >
