I don't *know* anything. But my understanding is you would upgrade to 1511, and then go to 1606. When we went to 1602 (from 2012 r2); we did 1511 on a Friday, 1602 on Saturday. We COULD have just kept going Friday and been done by midnight. It really was that easy (even considering how big our databases are). But well... it was Friday. and we had planned for it to take all weekend "just in case". So we left it to sit and simmer overnight mostly because it was wine o'clock, and we could. Other than the site servers (which went to 1511, then 1602 as a client); no other clients went to 1511 first, then 1602. Clients for version went from 2012 r2 client to 1602.
You may want to do that (I'm guessing) similarly; if only because the bits need to download to go from 1511 to the next one. On Tue, Jul 26, 2016 at 10:08 AM, Brian Illner <[email protected]> wrote: > We’re going to be upgrading our SCCM environment before too long. > > > > Does anyone know if MS plans to make a new downloadable ISO for this build? > > > > Or will we still have to upgrade to 1511 and then apply the updated builds? > > > > *BRIAN* *ILLNER |* Canal Insurance Company > 864.250.9227 > 864.679.2537 Fax > > Visit canalinsurance.com for news and information. > > *WARNING*: *As the information in this transmittal (including > attachments, if any) may contain confidential, proprietary, or business > trade secret information, it should only be reviewed by those who are the > intended recipients. Unless you are an intended recipient, any review, > use, disclosure, distribution or copying of this transmittal (or any > attachments) is strictly prohibited. If you have received this > transmittal in error, please notify me immediately by reply email and > destroy all copies of the transmittal. While Canal believes this > transmittal to be free of virus or other defect, it is the responsibility > of the recipient to ensure that it is virus free and no responsibility is > accepted by Canal (or its subsidiaries and affiliates) for any loss or > damage arising therefrom.* > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Linkey, Mike > *Sent:* Tuesday, July 26, 2016 8:18 AM > > *To:* [email protected] > *Subject:* RE: [External] [mssms] ConfigMgr 1606 current branch available > now > > > > I let it sit for a few hours then tried it all again and then it worked. > Must have been having a moment…Thanks for the input. > > > > Mike L. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Jason Sandys > *Sent:* Monday, July 25, 2016 1:52 PM > *To:* [email protected] > *Subject:* RE: [External] [mssms] ConfigMgr 1606 current branch available > now > > > > Are you sure it’s not installed already? > > > > Re-running the script btw won’t change anything – all that the script does > is flip a value in the site control file. > > > > J > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Linkey, Mike > *Sent:* Monday, July 25, 2016 11:31 AM > *To:* [email protected] > *Subject:* RE: [External] [mssms] ConfigMgr 1606 current branch available > now > > > > Yep several times in fact. It was there Friday, but gone today. I see > this in the hman.log file > > > > Configuration Manager Update > (PackageGuid=705820EF-6982-4417-8E54-307454C9A17A) is not applicable and > should be filtered. > > > > Don’t get why it says it is not applicable especially since I have ran > that script at least 6 times again today. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Jason Sandys > *Sent:* Monday, July 25, 2016 9:48 AM > *To:* [email protected] > *Subject:* RE: [External] [mssms] ConfigMgr 1606 current branch available > now > > > > No. Did you run the PowerShell script to opt in to the fast ring? > > > > J > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Linkey, Mike > *Sent:* Monday, July 25, 2016 8:04 AM > *To:* [email protected] > *Subject:* RE: [External] [mssms] ConfigMgr 1606 current branch available > now > > > > I saw this was available on Friday before I left. Today, it is no longer > an option for Updating. Did it get pulled? > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Brian Illner > *Sent:* Friday, July 22, 2016 11:40 AM > *To:* [email protected] > *Subject:* [External] [mssms] ConfigMgr 1606 current branch available now > > > > > > *david james (@djammmer <https://twitter.com/djammmer?refsrc=email&s=11>)* > > 7/22/16, 12:01 PM > <https://twitter.com/djammmer/status/756519487457734656?refsrc=email&s=11> > > #ConfigMgr <https://twitter.com/search?q=%23ConfigMgr&src=hash> 1606 > current branch available now, for everyone. Opt into fast ring to get it > immediately. blogs.technet.microsoft.com/enterprisemobi… > <https://t.co/7UMaFuZVva> > > > > > > CONFIDENTIALITY NOTICE: The e-mail transmission (and/or the documents > accompanying such) may contain confidential information. Such information > is intended only for the use of the individual or entity named above. If > you are not the named or intended recipient, you are hereby notified that > any disclosure, copying, distribution, or the taking of any action in > reliance on the contents of such information is strictly prohibited. If you > have received this email in error, please notify the sender and then delete > the email. Thank you for your cooperation. > > > > > > CONFIDENTIALITY NOTICE: The e-mail transmission (and/or the documents > accompanying such) may contain confidential information. Such information > is intended only for the use of the individual or entity named above. If > you are not the named or intended recipient, you are hereby notified that > any disclosure, copying, distribution, or the taking of any action in > reliance on the contents of such information is strictly prohibited. If you > have received this email in error, please notify the sender and then delete > the email. Thank you for your cooperation. > > > > > > CONFIDENTIALITY NOTICE: The e-mail transmission (and/or the documents > accompanying such) may contain confidential information. Such information > is intended only for the use of the individual or entity named above. If > you are not the named or intended recipient, you are hereby notified that > any disclosure, copying, distribution, or the taking of any action in > reliance on the contents of such information is strictly prohibited. If you > have received this email in error, please notify the sender and then delete > the email. Thank you for your cooperation. > > > > -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, http://www.smguru.org
