Yes,  thanks Mike for taking time and writing with detailed

On Thu, Jul 13, 2017 at 10:47 AM, Ed Aldrich <ed.aldr...@1e.com> wrote:

> Nice, concise explanation
>
>
>
> *[image: Ed]*
>
> *Ed Aldrich* *| Technology Enablement Lead*
>
> www.1e.com/mms
>
> Mobile: (401) 924-2293
>
> ed.aldr...@1e.com | www.1e.com
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Marable, Mike
> *Sent:* Thursday, July 13, 2017 10:12 AM
> *To:* mssms <mssms@lists.myitforum.com>
> *Subject:* RE: [mssms] Windows 10 Servicing
>
>
>
> No, you didn’t miss anything at all.
>
>
>
> Each Windows 10 build is first released as Current Branch.  That is when
> it is make publicly available.  That is the first listing for that version
> in the table.  It just shows that it was first released on August 2, 2016.
>
>
>
> Next, after about 4 months Microsoft will declare it ready for business
> and it will then be considered Current Branch for Business (CBB).  That is
> the second listing in the table.  It shows that 1607 reached the CBB
> milestone on November 29, 2016.
>
>
>
> Now, 1607 was a special build.  Build 1607 (the Anniversary Update) also
> included a new Long-Term Servicing Branch (LTSB) release.  That is the
> third and final entry in the table.  That LTSB version was released on
> August 2, 2016.
>
>
>
> LTSB is a special version of Windows 10 for use in very specific
> scenarios.  You really are only concerned with the CB and CBB entries in
> the table.
>
>
>
> So the latest version of Windows 10 is build 1703.  You can see in the
> table that it was release on April 11th.  It has not reached the
> milestone where Microsoft decides that it is ready for widespread
> deployment in corporate environments (the CBB milestone), so that is why
> there is only the one entry for 1703.  Pretty soon though build 1703 will
> reach that milestone and the table will be updated with that info.
>
>
>
> I hope that helps to clear things up.
>
>
>
> Mike
>
>
>
>
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com <listsad...@lists.myitforum.com>] *On Behalf Of *Kevin Ray
> *Sent:* Thursday, July 13, 2017 9:51 AM
> *To:* mssms <mssms@lists.myitforum.com>
> *Subject:* Re: [mssms] Windows 10 Servicing
>
>
>
> Thanks Mike,
>
> also when saw below for all CB,CBB,CTSB also showing same Windows
> 10.0.14393. Did i missing anything
>
>
>
>
>
> [image: Inline image 1]
>
>
>
> do we have any step by step upgrade task sequence blog please!!
>
>
>
> On Thu, Jul 13, 2017 at 7:52 AM, Marable, Mike <mmara...@med.umich.edu>
> wrote:
>
> Here is the Windows 10 build number info from TechNet for future use.
>
>
>
> https://technet.microsoft.com/en-us/windows/release-info.aspx
>
>
>
> 14393 is build 1607
>
>
>
> 1)      The latest build (1703) is version 15063
>
> 2)      Yes, you would get the latest builds from Microsoft
>
> 3)      Yes, in fact you are going to be doing that going forward since
> Windows 10 needs to be kept on a current build
>
> 4)      Personally, I would use an upgrade task sequence as opposed to
> the automated servicing to upgrade your clients to new builds.  The task
> sequence just offers you so much more control over the process.
>
>
>
> Mike
>
>
>
>
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Kevin Ray
> *Sent:* Thursday, July 13, 2017 7:40 AM
> *To:* mssms <mssms@lists.myitforum.com>
> *Subject:* [mssms] Windows 10 Servicing
>
>
>
> Hi All,
>
>
>
> I'm new to Windows 10 Servicing plans.
>
>
>
> I prepared the Windows 10 Image and deployed  on some machine.Now realized
> the  Windows 10 Servicing.When i check in SCCM Service Plan Dashboard most
> of the machines 98% machines showing as expires soon.Most of them are ready
> for release .(CB)
>
>
>
> when i checked the windows 10 version is  *"Windows 10.0.14393". *
>
>
>
> So my questions
>
>
>
> 1) what is the latest build
>
> 2) do i get the latest build from Microsoft .So that i can directly deploy
> that image(im assuming )
>
> 3) can i upgraded to latest build which i have already deployed
>
> 4) any other things i need to consider for this
>
>
>
> i'm with 1703 SCCM version
>
>
>
> **********************************************************
> Electronic Mail is not secure, may not be read every day, and should not
> be used for urgent or sensitive issues
>
>
>
>
>
>
>
> **********************************************************
> Electronic Mail is not secure, may not be read every day, and should not
> be used for urgent or sensitive issues
>
>
>
> ------------------------------
>
>
> Legal Notice: This email is intended only for the person(s) to whom it is
> addressed. If you are not an intended recipient and have received this
> message in error, please notify the sender immediately by replying to this
> email or calling +44(0) 2083269015 <+44%2020%208326%209015> (UK) or +1
> 866 592 4214 <(866)%20592-4214> (USA). This email and any attachments may
> be privileged and/or confidential. The unauthorized use, disclosure,
> copying or printing of any information it contains is strictly prohibited.
> The opinions expressed in this email are those of the author and do not
> necessarily represent the views of 1E Ltd. Nothing in this email will
> operate to bind 1E to any order or other contract.
>
>



Reply via email to