+1 From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: Tuesday, July 5, 2016 9:39 AM To: mssms@lists.myitforum.com 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: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Brian Illner Sent: Tuesday, July 5, 2016 8:26 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> 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<http://canalinsurance.com> for news and information. [cid:image001.jpg@01D1D6B0.8B228AE0] [cid:image002.jpg@01D1D6B0.8B228AE0]<https://www.linkedin.com/company/canal-insurance-company> 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: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Juelich, Adam Sent: Tuesday, July 5, 2016 8:54 AM To: mssms@lists.myitforum.com<mailto: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<http://www.pulaskischools.org> Client Management Specialist 920-822-6075 On Tue, Jul 5, 2016 at 7:12 AM, David Jones <dkjones9...@gmail.com<mailto: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. ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
