![update windows 10 build 10240 to 1511 update windows 10 build 10240 to 1511](https://slideplayer.com/slide/14127614/86/images/4/Momentum+for+Windows+10+since+release.jpg)
- #Update windows 10 build 10240 to 1511 how to#
- #Update windows 10 build 10240 to 1511 install#
- #Update windows 10 build 10240 to 1511 update#
" Microsoft designed Windows 10 servicing lifetime policies so that CBBs will receive servicing updates for approximately twice as many months as CBs.
#Update windows 10 build 10240 to 1511 install#
You must install new feature upgrades on machines running these branches in order to continue receiving monthly security updates." (v=vs.85).aspx " Unlike previous versions of Windows, the servicing lifetime of Current Branch or Current Branch for Business is finite. This is the answer I got from support "We do offer patching for windows 10 for security updates we do not offer nor will offer feature packs that are not classified as security updates."Īm I not reading the microsoft documentation correct that if we don't stay within 2 versions of the latest CBB (which Symantec support is telling me we can't support through patch), that we will no longer be eligible for security updates? Doesn't that really make these feature updates security related? Timeframe and exact solution is TBD but this is something we are working on. We are working on a supported way for this. See the link from Microsoft which provides more details on how to accomplish thisĢ. Yes.
#Update windows 10 build 10240 to 1511 update#
iso for the feature update and pulling out the files and delivering them via software management. They have shared with me a workaround which involves you pulling down the. We are working ways to make this part of the Patch Manaement tool directly. The Patch Management System currently doesn't handle these, since they are not an OS or Application Security update. Windows 10 is the first version of Windows that has exhibited this behavior. My team has told me that the Feature Release updates that are referred to here are really like updates to the OS itself as opposed to security updates. I circled back with our team for some guidance, and they were able to share the following with me. The vague statement about voiding MS support agreements is not helpful either. This is an entirely different task from maintaining Windows 10 build releases.
#Update windows 10 build 10240 to 1511 how to#
At first glance, the above referenced article (INFO3298) appears to do this but actually refers admins to a How To article (HOWTO124389) which explains how to do an in-place upgrade from a previous OS (Windows 8) using the files from a Win 10 DVD. Until Symantec gets these build updates working within the patch management solution (where they belong), they should publish an official recommendation for how they can be done in the existing versions of their product. Read more about maintaining Windows 10 here: (v=vs.85).aspx Microsoft states that build updates on the Current Branch for Business (CBB) track can be done by Windows Update, WSUS, SCCM, or 3rd Party configuration management tools so it doesn't appear they are intending to prevent tools like Altiris (ITMS) from deploying these updates.
![update windows 10 build 10240 to 1511 update windows 10 build 10240 to 1511](https://slideplayer.com/14127614/86/images/slide_1.jpg)
We should be able to stage and deploy these updates just like any other Windows update in patch management solution.
![update windows 10 build 10240 to 1511 update windows 10 build 10240 to 1511](https://i.ytimg.com/vi/lWmWsbxLEeM/maxresdefault.jpg)
The Windows 10 support model requires you keep up to date with the Windows build releases and those releases will be coming frequently enough to warrant some serious automation that doesn't require custom package creation. I sure hope Symantec is working hard on finding a solution to this universal IT dilemma.