The version numbers are based on dates, so you can quickly see what order they are in.
1602 = February 2016 1511 = November 2015 If the version comes with "TP" that means it is a preview and not production. When Microsoft talks to us about version 8811, it'll be November, 2088. Though I don't think Microsoft thought this through. What do we do after 9912? Is this SCCM's Y2K? #FutureAaronProblems On Fri, Jul 8, 2016 at 8:10 AM Aaron Czechowski < aaron.czechow...@microsoft.com> wrote: > https://technet.microsoft.com/en-US/library/mt607046.aspx > > > > The following versions of Configuration Manager are available as a > baseline, an update, or both: > > *Version* > > *Availability date* > > *Baseline* > > *in-console update* > > 1511 > > 5.00.8325.1000 > > 12/8/2015 > > Yes > > No > > 1602 > > 5.00.8355.1000 > > 3/11/2016 > > No > > Yes > > > > > > *From:* listsad...@lists.myitforum.com [mailto: > listsad...@lists.myitforum.com] *On Behalf Of *Hun boy > *Sent:* Friday, 8 July, 2016 06:52 > > > *To:* mssms@lists.myitforum.com > *Subject:* Re: [mssms] SCCM Current Branch > > > > Sorry, > > > > if i hijack this thread. > > > > If MS keep changing the numbers like 1606, 1511.... is there any ms link > that tells what is current version and previous versions ? > > > > Thanks & Regards, > > Hunboy > 564-1888 > > > ------------------------------ > > *From:* listsad...@lists.myitforum.com <listsad...@lists.myitforum.com> > on behalf of Lindenfeld, Ivan <ivan.lindenf...@fnf.com> > *Sent:* Thursday, July 7, 2016 7:53 PM > *To:* mssms@lists.myitforum.com > *Subject:* RE: [mssms] SCCM Current Branch > > > > I interpret the public data as: > > > > CM 1606 = Windows 10 Anniversary Edition release > > CM later this year = Server 2016 release > > > > So we get two more Current Branches this year, for three total. > > > > No inside info, not an MVP. YMMV. Objects in this mirror are closer than > they appear. > > > > Ivan Lindenfeld > > > > *From:* listsad...@lists.myitforum.com [ > mailto:listsad...@lists.myitforum.com <listsad...@lists.myitforum.com>] *On > Behalf Of *Shane Alexander > *Sent:* Thursday, July 7, 2016 9:53 AM > *To:* mssms@lists.myitforum.com > *Subject:* RE: [mssms] SCCM Current Branch > > > > "there will also be a full production 1606 release" ... (you must know > more than us) ... > > ... I personally think that 1606 will be too old, still buggy and not > complete, to be CB, however MS do need to lock down code. > Reviewing some random timelines published ... > > *FAQ: System Center Configuration Manager (Current Branch)* > > Learn about the Microsoft Configuration Manager current branch model and > how it works with the Windows 10 servicing model > > > https://blogs.technet.microsoft.com/enterprisemobility/2016/06/24/faq-system-center-configuration-manager-current-branch/ > <https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fblogs.technet.microsoft.com%2fenterprisemobility%2f2016%2f06%2f24%2ffaq-system-center-configuration-manager-current-branch%2f&data=01%7c01%7caaron.czechowski%40microsoft.com%7cf59df493e9704941e30d08d3a71ebb45%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=4gh06U9ZWQFBc0d4RgNM5F8OuRBG4x80ANBGrghAMRc%3d> > > > <https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fblogs.technet.microsoft.com%2fenterprisemobility%2f2016%2f06%2f24%2ffaq-system-center-configuration-manager-current-branch%2f&data=01%7c01%7caaron.czechowski%40microsoft.com%7cf59df493e9704941e30d08d3a71ebb45%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=4gh06U9ZWQFBc0d4RgNM5F8OuRBG4x80ANBGrghAMRc%3d> > > FAQ: System Center Configuration Manager (Current Branch ... > <https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fblogs.technet.microsoft.com%2fenterprisemobility%2f2016%2f06%2f24%2ffaq-system-center-configuration-manager-current-branch%2f&data=01%7c01%7caaron.czechowski%40microsoft.com%7cf59df493e9704941e30d08d3a71ebb45%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=4gh06U9ZWQFBc0d4RgNM5F8OuRBG4x80ANBGrghAMRc%3d> > > blogs.technet.microsoft.com > > In December 2015, we made some major changes to System Center > Configuration Manager (ConfigMgr) when we introduced our current branch > model. This new model ... > > > > > *Will Microsoft release a ConfigMgr product update in alignment with > System Center 2016?* > > Yes, there will be a release of ConfigMgr that *aligns with the release > of Windows Server 2016 and System Center 2016*. We’ll share more details > on this release in the near future. > > > Is v1606 ready, *really*, for CB release. Cos WS 2106 & SC 2016 are not > ready. > > At least we know when W10 next release will be available ... August 2. > That's when I think we'll know about other important matters like new > GPO's/ADMX's for W10 and also the ConfigMgr branch to support all of this. > MS teams not always in lock-step. > > My 2.1 cents :-) > > > > Shane > > ------------------------------ > > From: ja...@sandys.us > To: mssms@lists.myitforum.com > Subject: RE: [mssms] SCCM Current Branch > Date: Tue, 5 Jul 2016 13:11:06 +0000 > > Adam is correct. It’s important to denote the TP releases as such because > there will also be a full production 1606 release (just like there was a TP > and a full production 1602 release also). So the TP should be TP1606 > otherwise we’ll all go completely bonkers trying to keep the two separated. > > > > J > > > > *From:* listsad...@lists.myitforum.com [ > mailto:listsad...@lists.myitforum.com <listsad...@lists.myitforum.com>] *On > Behalf Of *Juelich, Adam > *Sent:* Tuesday, July 5, 2016 7:54 AM > *To:* mssms@lists.myitforum.com > *Subject:* Re: [mssms] SCCM Current Branch > > > > CB is 1602, and the TP release is 1606 I believe. > > *-----------------------------------------------* > *Adam Juelich* > Pulaski Community School District > <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fwww.pulaskischools.org&data=01%7c01%7caaron.czechowski%40microsoft.com%7cf59df493e9704941e30d08d3a71ebb45%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=KPH13pKREKuhy52UcrwkwVukHBosyRfvMkewMKMuHD0%3d> > > > Client Management Specialist > 920-822-6075 > > > > On Tue, Jul 5, 2016 at 7:12 AM, David Jones <dkjones9...@gmail.com> wrote: > > Right now, what is the Current Branch and what is the latest 'in between > for the bleeding edge folks' release? > > > > > > > > > > > ------------------------------ > > *The Pulaski Community School District does not discriminate on the basis > of any characteristic protected under State or Federal law.* > > > > NOTICE: The information contained in this message is proprietary and/or > confidential and may be privileged. If you are not the intended recipient > of this communication, you are hereby notified to: (i) delete the message > and all copies; (ii) do not disclose, distribute or use the message in any > manner; and (iii) notify the sender immediately. >
