At least as of 1602 I don’t think you can deploy the Win10 upgrade via traditional software updates. Your options are task sequence (for greater control but with more manual work) or servicing plan (less manual work but not as flexible yet).
Go watch the MVA that Wally and I did a while back: https://mva.microsoft.com/en-US/training-courses/deploying-windows-10-using-system-center-configuration-manager-16311 I expanded on this during MMS session (with Dune & Niall), which unfortunately wasn’t recorded or the slides published (unless you attended MMS and then look up my session, “Windows 10 Servicing with Configuration Manager”), but here’s the key slide from the MVA: [cid:[email protected]] And the important thing to note is that like a lot of what we’re doing with SCCM current branch, it’s very much iterative. So instead of just not using a new feature, please try it out in a lab or pilot, and then give us feedback so that we can improve it. As you can see from the slide above, we already have a number of things in the works (and are working closely with the Windows, WU and WSUS teams on this topic as well). From: [email protected] [mailto:[email protected]] On Behalf Of Brian Illner Sent: Wednesday, 6 July, 2016 09:07 To: [email protected] Subject: RE: [mssms] SCCM Current Branch The MS recommendation was within the Config Mgr program in Microsoft Connect. I cannot find the specific feedback/bug post at the moment. BRIAN ILLNER | Canal Insurance Company 864.250.9227 864.679.2537 Fax Visit canalinsurance.com<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fcanalinsurance.com&data=01%7c01%7caaron.czechowski%40microsoft.com%7c5adadd9b301e4fc5127608d3a59f4ac6%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=%2fCjoAWj%2bD26VlFlLJfo03%2f1uLj%2fP0nXDVRIyg1QFpe8%3d> for news and information. [cid:[email protected]] [cid:[email protected]]<https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww.linkedin.com%2fcompany%2fcanal-insurance-company&data=01%7c01%7caaron.czechowski%40microsoft.com%7c5adadd9b301e4fc5127608d3a59f4ac6%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=dqIHGPeGlfqXvCr7F7ZeGr%2b5lF2NimV4Na1M%2f2lCD6c%3d> 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]> [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Tuesday, July 5, 2016 11:30 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] SCCM Current Branch +1 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Tuesday, July 5, 2016 9:39 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] SCCM Current Branch It’s never truly been broken. There are just a lot of caveats due to how the upgrades are/were published in WSUS along with things that the in-place upgrade scenario from a Windows perspective simply doesn’t handle gracefully (or at all). If you any actual control over the process, then an upgrade task sequence that enables you to do additional things is the way to go; examples include (but are not limited to) removing built-in store apps, dealing with third-party disk encryption or AV, injecting drivers, adding languages. Thus, it is completely possible to use the built-in servicing successfully but in most corporate environments, due to the variety and complexity involved, the simplistic fire and forget upgrade is just not sufficient to handle all of these caveats. I don’t think Microsoft has any explicit recommendation here at all. They’ve provided multiple technically viable paths and it’s up to you to choose which is best for your organization. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Brian Illner Sent: Tuesday, July 5, 2016 8:26 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] SCCM Current Branch Is the Windows 10 Servicing feature still broken within SCCM? Last instruction I had read from MS was to deploy the Win10 upgrades via the standard Software Updates, and not attempt the Servicing Plans yet. BRIAN ILLNER | Canal Insurance Company 864.250.9227 864.679.2537 Fax Visit canalinsurance.com<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fcanalinsurance.com&data=01%7c01%7caaron.czechowski%40microsoft.com%7c5adadd9b301e4fc5127608d3a59f4ac6%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=%2fCjoAWj%2bD26VlFlLJfo03%2f1uLj%2fP0nXDVRIyg1QFpe8%3d> for news and information. [cid:[email protected]] [cid:[email protected]]<https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww.linkedin.com%2fcompany%2fcanal-insurance-company&data=01%7c01%7caaron.czechowski%40microsoft.com%7c5adadd9b301e4fc5127608d3a59f4ac6%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=dqIHGPeGlfqXvCr7F7ZeGr%2b5lF2NimV4Na1M%2f2lCD6c%3d> 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]> [mailto:[email protected]] On Behalf Of Juelich, Adam Sent: Tuesday, July 5, 2016 8: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<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fwww.pulaskischools.org&data=01%7c01%7caaron.czechowski%40microsoft.com%7c5adadd9b301e4fc5127608d3a59f4ac6%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=63LuO4nJDIrlw28OK%2fKqJkoKBhTKx59QKTSFF%2f99Mds%3d> Client Management Specialist 920-822-6075 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. ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
