My point is that there is a difference between 1606TP and what will eventually be released as 1606 to production - that's why it's important to denote it as TP1606 or 1606TP.
? "there will also be a full production 1606 release" ... (you must know more than us) ... This has been well publicized by the product group so not just me. ? Is v1606 ready, really, for CB release. No. That's why there's a 1606TP. After additional testing including at TAPs, they will determine what (if anything) needs to be fixed/changed or if any new features maybe need to be yanked. These updates will then be incorporated to make the full 1606 production release. ? Cos WS 2106 & SC 2016 are not ready. 1606 has nothing to with Windows Server 2016 or System Center 2016 - no one said it did. The blog simply says that there will be *a* release. Given the every 4 month cycle they've been on (and have publically said they will be maintaining) for releasing ConfigMgr CB production builds, that equates to - the following is speculation and simple math on my part - 1610 being released sometime in the November timeframe which is after Ignite (which is in late September) which is where I speculate they will at least announce the release of Windows Server 2016 and System Center 2016. J From: [email protected] [mailto:[email protected]] On Behalf Of Shane Alexander Sent: Thursday, July 7, 2016 8:53 AM To: [email protected] 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/ 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: [email protected]<mailto:[email protected]> To: [email protected]<mailto:[email protected]> 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: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Juelich, Adam Sent: Tuesday, July 5, 2016 7:54 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] SCCM Current Branch CB is 1602, and the TP release is 1606 I believe. ----------------------------------------------- Adam Juelich Pulaski Community School District<http://www.pulaskischools.org> Client Management Specialist 920-822-6075[X] On Tue, Jul 5, 2016 at 7:12 AM, David Jones <[email protected]<mailto:[email protected]>> 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.
