Do not question the ways of Microsoft. You will find only madness.
Daniel Wolf From: [email protected] [mailto:[email protected]] On Behalf Of Bradley, Matt Sent: Wednesday, January 28, 2015 10:19 AM To: [email protected] Subject: RE: [External] RE: [mssms] RE: Right-Click Client Install If it’s the only way to get right-click install to work, how could MS NOT support it? From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Wednesday, January 28, 2015 9:19 AM To: [email protected] <mailto:[email protected]> Subject: [External] 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]> [mailto:[email protected]] On Behalf Of Sean Pomeroy Sent: Wednesday, January 28, 2015 9:09 AM To: [email protected] <mailto:[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] <mailto:[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.
smime.p7s
Description: S/MIME cryptographic signature
