so it was supported, had a bug, and they withdrew support. Lovely. They did the same thing to AAW. Said it was "Fully Supported" then we had an issue and they said "Fully supported" means we support the "installation" of it, but not the product if it stops working or has bugs
"Supported by Microsoft" is meaningless these days. 100% without value. They can change it at any time it suits them. So if you commit to doing something X way or use X product, it could be different the next time you call in and the do not feel like fixing it. On Mon, Jul 22, 2013 at 5:01 PM, Rod Trent <[email protected]> wrote: > And, apparently, Microsoft wasn’t aware that it wasn’t supported, either… > J**** > > ** ** > > > http://myitforum.com/cs2/blogs/rtrent/archive/2008/09/25/good-info-how-to-automatically-apply-a-client-hotfix-as-part-of-a-client-push-or-client-installation.aspx > **** > > ** ** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Todd Hemsell > *Sent:* Monday, July 22, 2013 5:39 PM > *To:* [email protected] > *Subject:* Re: [mssms] ConfigMgr CU2 silent install**** > > ** ** > > does not sound like wrong side of the street to me.**** > > **** > > As it turns out, this little known feature was little known for a reason - > it was *not fully tested* for use with Configuration Manager 2007. *As a > result, it is not supported.* **** > > 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. **** > > In the event you have already deployed your clients and patched them in > this manner but have no known issues,* chances are there's nothing to > worry about. ***** > > On Mon, Jul 22, 2013 at 2:40 PM, Jason Sandys <[email protected]> wrote:**** > > > http://blogs.technet.com/b/configmgrteam/archive/2009/04/08/automatically-applying-hotfixes-to-the-configuration-manager-2007-client-during-installation.aspx > **** > > **** > > That’s for 2007, nothing has changed in 2012 – trust me, I’ve asked.**** > > **** > > Also remember, not everything is documented – in fact, very few things > compared to the number of possibilities is actually documented.**** > > **** > > J**** > > **** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *James Massardo > *Sent:* Monday, July 22, 2013 2:29 PM > *To:* [email protected] > *Subject:* Re: [mssms] ConfigMgr CU2 silent install**** > > **** > > Is that listed in the Technet documentation or are there any MS blog posts > about it?**** > > **** > > Thanks,**** > > James Massardo**** > > **** > > *From: *Jason Sandys <[email protected]> > *Reply-To: *"[email protected]" <[email protected]> > *Date: *Monday, July 22, 2013 2:22 PM > *To: *"[email protected]" <[email protected]> > *Subject: *RE: [mssms] ConfigMgr CU2 silent install**** > > **** > > Exactly what I said before: CSS. They have explicitly stated it’s not > supported because there are known issues and it’s abandoned code.**** > > **** > > J**** > > **** > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Todd Hemsell > *Sent:* Monday, July 22, 2013 2:14 PM > *To:* [email protected] > *Subject:* Re: [mssms] ConfigMgr CU2 silent install**** > > **** > > who said it has risks other than you?**** > > what are the risks?**** > > On Mon, Jul 22, 2013 at 1:57 PM, Jason Sandys <[email protected]> wrote:**** > > Actually it has – he’s doing something he’s been explicitly told has risks > and should not do.**** > > **** > > J**** > > **** > > *From:*[email protected] [mailto: > [email protected]] *On Behalf Of *Todd Hemsell > *Sent:* Monday, July 22, 2013 1:50 PM > *To:* [email protected] > *Subject:* Re: [mssms] ConfigMgr CU2 silent install**** > > **** > > it has not been established he is going the wrong way.**** > > On Mon, Jul 22, 2013 at 12:54 PM, Jason Sandys <[email protected]> wrote:*** > * > > So, when you hit the car head-on because you’re going down the freeway the > wrong way is when you’ll decide to stop doing something?**** > > **** > > J**** > > **** > > *From:*[email protected] [mailto: > [email protected]] *On Behalf Of *Ewing, Scott L > *Sent:* Monday, July 22, 2013 12:43 PM > *To:* [email protected] > *Subject:* RE: [mssms] ConfigMgr CU2 silent install**** > > **** > > When it stops working we’ll stop using it. J**** > > **** > > *Scott Ewing***** > > **** > > *From:*[email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Tuomo Leppänen > *Sent:* Monday, July 22, 2013 1:04 PM > *To:* [email protected] > *Subject:* Re: [mssms] ConfigMgr CU2 silent install**** > > **** > > Using the same method here, works fine, haven't got any issues with it. > With 2007 there were some issues that the ccmsetup parameters weren't > applied when using this method, with 2012 I've noticed that the client > actually installs the normal SP1 client first (with the setted parameters) > and applies the msp afterwards. > > I haven't heard that anyone has had any issues with CM12. > > -T > > > On 22.7.2013 19:32, Jason Sandys wrote:**** > > This is totally and explicitly unsupported because it is known to have > issues – it is essentially left over code from SMS 2003. I would recommend > not using it all.**** > > **** > > J**** > > **** > > *From:*[email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Ewing, Scott L > *Sent:* Monday, July 22, 2013 11:16 AM > *To:* [email protected] > *Subject:* RE: [mssms] ConfigMgr CU2 silent install**** > > **** > > I realize this is not an answer to your question but here it is anyway. We > place the *configmgr2012ac-sp1-kb2854009-i386.msp* in primary site server > folder *\Program Files\Microsoft Configuration > Manager\Client\i386\ClientPatch*. CU2 then installs during a client > install without any CCMSETUP command line switches.**** > > **** > > *Scott Ewing***** > > **** > > *From:*[email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Trond Karstensen > *Sent:* Tuesday, July 16, 2013 4:43 PM > *To:* [email protected] > *Subject:* RE: [mssms] ConfigMgr CU2 silent install**** > > **** > > I am talking about the initial install on the site server.**** > > **** > > I have a scripted install of CM12 and want to add the installation of CU2. > **** > > **** > > Regards**** > > Trond**** > > **** > > *From:*[email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Trevor Sullivan > *Sent:* 16. juli 2013 22:25 > *To:* [email protected] > *Subject:* RE: [mssms] ConfigMgr CU2 silent install**** > > **** > > Are you talking about the ConfigMgr 2012 SP1 Cumulative Update 2 for the > client?**** > > **** > > Cheers,**** > > *Trevor Sullivan***** > > [image: WordPress Logo 32px] <http://trevorsullivan.net/> [image: > Twitter Logo 32px] <http://twitter.com/pcgeek86> [image: Facebook Logo > 32px] <http://facebook.com/trevor.sullivan> [image: Google+ Icon > 32px]<https://plus.google.com/106658223083457664096> > **** > > **** > > *From:*[email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Trond Karstensen > *Sent:* Tuesday, July 16, 2013 2:53 PM > *To:* [email protected] > *Subject:* [mssms] ConfigMgr CU2 silent install**** > > **** > > Hi.**** > > **** > > Is it possible to script the installation of ConfigMgr 2012 SP1 CU2 by > using install switches ?**** > > **** > > Regards**** > > Trond**** > > **** > > **** > > **** > > **** > > **** > > **** > > **** > > **** > > **** > > **** > > **** > > **** > > **** > > NOTICE: This electronic mail message and any files transmitted with it are > intended > exclusively for the individual or entity to which it is addressed. The > message, > together with any attachment, may contain confidential and/or privileged > information. > Any unauthorized review, use, printing, saving, copying, disclosure or > distribution > is strictly prohibited. If you have received this message in error, please > immediately advise the sender by reply email and delete all copies.**** > > **** > > ** ** > > ** ** > >
<<image001.gif>>
<<image002.gif>>
<<image003.gif>>
<<image004.gif>>
