Not a big deal is it? mine works just fine. If it does not work for you, don't do it.
"In this context, "not supported" means that if you reported problems with the use of the ClientPatch folder directly - or problems as a result of its use - we would not change the product code to resolve those. " Ok, so they will not change the code. But if your clients do not work you still get support. The doom and gloom over "Supported" is way over hyped. I doubt many people even know what it really means. It CERTAINLY does not mean they will no longer help you resolve issues. PSS is a profit center after all. Honestly, I have found at least 5 bugs int he content distribution systems and several more in the application model. One of them lets users bypass software approval requirements. THAT is 100% fully supported, and yet... NO CODE CHANGES. So even when they "Support" it, they do not really support it. Completely meaningless term, "Supported" On Wed, Jan 28, 2015 at 11:10 AM, Daniel Ratliff <dratl...@humana.com> wrote: > The one known one is outlined in the article Jason linked to. > > > > > http://blogs.technet.com/b/configmgrteam/archive/2009/04/08/automatically-applying-hotfixes-to-the-configuration-manager-2007-client-during-installation.aspx > > > > *The specific issue uncovered so far is that if certain command line > properties <http://technet.microsoft.com/en-us/library/bb680980.aspx> were > specified (such as FSP or SMSSLP) they may not be honored when the patch is > applied. There could be other issues that we are not aware of yet, but > that one is apparent quickly if you are in that state.* > > > > *Daniel Ratliff* > > > > *From:* listsad...@lists.myitforum.com [mailto: > listsad...@lists.myitforum.com] *On Behalf Of *Todd Hemsell > *Sent:* Wednesday, January 28, 2015 12:05 PM > *To:* mssms@lists.myitforum.com > *Subject:* Re: [mssms] RE: Right-Click Client Install > > > > 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 <dratl...@humana.com> > 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:* listsad...@lists.myitforum.com [mailto: > listsad...@lists.myitforum.com] *On Behalf Of *Ewing, Scott L > *Sent:* Wednesday, January 28, 2015 11:24 AM > *To:* mssms@lists.myitforum.com > *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:* listsad...@lists.myitforum.com [ > mailto:listsad...@lists.myitforum.com <listsad...@lists.myitforum.com>] *On > Behalf Of *Jason Sandys > *Sent:* Wednesday, January 28, 2015 10:19 AM > *To:* mssms@lists.myitforum.com > *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:* listsad...@lists.myitforum.com [ > mailto:listsad...@lists.myitforum.com <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. > > > > > > > > > > > > > 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. > >
